procedure-cli 1.0.4 → 1.2.0
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/package.json +1 -1
- package/templates/AGENTS.md.hbs +12 -0
- package/templates/CLAUDE.md.hbs +12 -0
package/package.json
CHANGED
package/templates/AGENTS.md.hbs
CHANGED
|
@@ -16,6 +16,11 @@ This file provides tool-agnostic instructions for AI coding agents working on th
|
|
|
16
16
|
|
|
17
17
|
Run typecheck before build. Run all checks before submitting a PR.
|
|
18
18
|
|
|
19
|
+
## Documentation Lookup
|
|
20
|
+
|
|
21
|
+
- Always use Context7 MCP to fetch concise, up-to-date documentation for all libraries before implementation
|
|
22
|
+
- Do not rely on training data for API usage — verify with Context7 first
|
|
23
|
+
|
|
19
24
|
## Code Style
|
|
20
25
|
|
|
21
26
|
- Language: {{language}}
|
|
@@ -55,6 +60,13 @@ When a user reports a bug:
|
|
|
55
60
|
2. **If valid** — append a new `CR-` entry to `CODE-REVIEW.md` following the code review logging procedure (Entry ID, Scope, Validation Matrix, Findings with `file:line` evidence and severity, Verification Notes).
|
|
56
61
|
3. **If not valid** — explain to the user why the reported behavior is expected or not reproducible.
|
|
57
62
|
|
|
63
|
+
## Understanding, Planning & Approval
|
|
64
|
+
|
|
65
|
+
- Always confirm the understanding in Vietnamese
|
|
66
|
+
- Always present the approach based on the confirming understanding
|
|
67
|
+
- Always wait for the user's approval on the understanding and the approach
|
|
68
|
+
- Make a task after being approved
|
|
69
|
+
|
|
58
70
|
## Testing
|
|
59
71
|
|
|
60
72
|
1. Run `{{typecheckCommand}}` — must pass with no errors
|
package/templates/CLAUDE.md.hbs
CHANGED
|
@@ -15,6 +15,11 @@ See docs/PRD.md for product requirements and docs/USER-STORIES.md for user stori
|
|
|
15
15
|
{{prCommand}} # Before creating a PR
|
|
16
16
|
```
|
|
17
17
|
|
|
18
|
+
## Documentation Lookup
|
|
19
|
+
|
|
20
|
+
- Always use Context7 MCP to fetch concise, up-to-date documentation for all libraries before implementation
|
|
21
|
+
- Do not rely on training data for API usage — verify with Context7 first
|
|
22
|
+
|
|
18
23
|
## Code Style
|
|
19
24
|
|
|
20
25
|
{{#each codeStyle}}
|
|
@@ -82,6 +87,13 @@ All colors accessed through `C` from `src/lib/theme.ts`. **Never hardcode hex va
|
|
|
82
87
|
- If something goes sideways, STOP and re-plan — don't keep pushing
|
|
83
88
|
- A good plan lets you one-shot the implementation
|
|
84
89
|
|
|
90
|
+
### Understanding, Planning & Approval
|
|
91
|
+
- Always confirm the understanding in Vietnamese
|
|
92
|
+
- Always present the approach based on the confirming understanding
|
|
93
|
+
- Always wait for the user's approval on the understanding and the approach
|
|
94
|
+
- Make a task after being approved
|
|
95
|
+
- Leverage team agents if possible
|
|
96
|
+
|
|
85
97
|
### Documentation Sync
|
|
86
98
|
- After EVERY implementation: update CLAUDE.md, README.md, and product artifacts (docs/PRD.md, docs/USER-STORIES.md) to reflect the current state
|
|
87
99
|
- Architecture descriptions, step counts, component lists, and behavioral descriptions must match the actual code
|