@hopla/claude-setup 1.2.6 → 1.2.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/files/CLAUDE.md +2 -0
- package/files/commands/hopla-execute.md +23 -5
- package/package.json +1 -1
package/files/CLAUDE.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Global Rules — Agentic Coding System
|
|
2
2
|
|
|
3
|
+
> 🌐 **CRITICAL — Language:** Always respond in the same language the user is writing in, regardless of the language of any command or instruction. If the user writes in Spanish, respond in Spanish. If in English, respond in English. This rule overrides everything else.
|
|
4
|
+
|
|
3
5
|
## 1. Communication
|
|
4
6
|
|
|
5
7
|
- **Always respond in the same language the user writes in** — if the user writes in Spanish, respond in Spanish; if in English, respond in English
|
|
@@ -15,17 +15,35 @@ Read in this order:
|
|
|
15
15
|
|
|
16
16
|
Do not start implementing until you have read everything above.
|
|
17
17
|
|
|
18
|
-
## Step 2:
|
|
18
|
+
## Step 2: Verify Git Branch
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
git branch --show-current
|
|
22
|
+
git status
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
Check that the current branch follows Git Flow:
|
|
26
|
+
- **Never execute on `main` or `master`** — stop and warn the user
|
|
27
|
+
- **If on `develop`/`dev`** — ask: "You're on `develop`. Should I create a feature branch first? (recommended: `feature/[plan-name]`)"
|
|
28
|
+
- **If on a `feature/`, `fix/`, or `hotfix/` branch** — proceed
|
|
29
|
+
|
|
30
|
+
If a new branch is needed, propose the name and wait for confirmation before creating it:
|
|
31
|
+
```bash
|
|
32
|
+
git checkout -b feature/[kebab-case-plan-name]
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
## Step 3: Confirm Understanding
|
|
19
36
|
|
|
20
37
|
Before executing, summarize:
|
|
21
38
|
- What you are about to build
|
|
39
|
+
- The branch where changes will be made
|
|
22
40
|
- How many tasks are in the plan
|
|
23
41
|
- Any constraints or gotchas flagged in the plan
|
|
24
42
|
- Anything unclear that needs clarification before proceeding
|
|
25
43
|
|
|
26
44
|
If anything in the plan is ambiguous or contradictory, **stop and ask** before writing code.
|
|
27
45
|
|
|
28
|
-
## Step
|
|
46
|
+
## Step 4: Execute Tasks in Order
|
|
29
47
|
|
|
30
48
|
Work through each task in the plan sequentially. For each task:
|
|
31
49
|
|
|
@@ -44,7 +62,7 @@ Work through each task in the plan sequentially. For each task:
|
|
|
44
62
|
|
|
45
63
|
Do not improvise silently. When in doubt, stop and ask.
|
|
46
64
|
|
|
47
|
-
## Step
|
|
65
|
+
## Step 5: Run Full Validation Pyramid
|
|
48
66
|
|
|
49
67
|
After all tasks are complete, run the full validation sequence in order.
|
|
50
68
|
**Do not skip levels. Do not proceed if a level fails.**
|
|
@@ -76,7 +94,7 @@ List what the user should manually verify:
|
|
|
76
94
|
- Edge cases to check
|
|
77
95
|
- Any decisions made during implementation that the user should review
|
|
78
96
|
|
|
79
|
-
## Step
|
|
97
|
+
## Step 6: Completion Report
|
|
80
98
|
|
|
81
99
|
Provide a summary of what was done:
|
|
82
100
|
|
|
@@ -105,7 +123,7 @@ Provide a summary of what was done:
|
|
|
105
123
|
- [anything that differed from the plan and why]
|
|
106
124
|
```
|
|
107
125
|
|
|
108
|
-
## Step
|
|
126
|
+
## Step 7: Suggest Next Steps
|
|
109
127
|
|
|
110
128
|
After the summary, suggest:
|
|
111
129
|
1. Run `/hopla-execution-report` to document this implementation for system review
|