eng-skills 0.2.0 → 0.3.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/README.md +6 -0
- package/package.json +1 -1
- package/templates/CLAUDE.md +19 -0
package/README.md
CHANGED
|
@@ -95,6 +95,12 @@ architecture as ADRs — so the knowledge base starts warm, not empty.
|
|
|
95
95
|
|
|
96
96
|
## The daily workflow
|
|
97
97
|
|
|
98
|
+
You don't have to remember the slash commands. CLAUDE.md contains an
|
|
99
|
+
**intent-routing table**: a plain "add a dark mode toggle" triggers the same
|
|
100
|
+
clarify → research → plan → implement → verify → document workflow as typing
|
|
101
|
+
`/feature` — casual phrasing doesn't skip steps. The commands are just explicit
|
|
102
|
+
shortcuts:
|
|
103
|
+
|
|
98
104
|
| Command | What it does |
|
|
99
105
|
|---|---|
|
|
100
106
|
| `/kickoff <idea>` | From-scratch projects: interviews you (mandatory questions), researches the competitive landscape ("what are others doing"), locks stack decisions as ADRs, writes the spec and phase roadmap — *then* scaffolds. |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "eng-skills",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"description": "Scaffold battle-tested Claude Code engineering conventions into any repo: enforced docs protocol (features/fixes/decisions/phases), pre/post/stop hooks, research-first slash commands, and a CLAUDE.md that Claude fills in by reading your codebase.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"claude",
|
package/templates/CLAUDE.md
CHANGED
|
@@ -44,6 +44,25 @@ Notes:
|
|
|
44
44
|
- If the Stop hook blocks you, it's working as designed: write the missing doc, then finish.
|
|
45
45
|
- If hooks don't fire at all, the workspace may be untrusted — verify with `/hooks`.
|
|
46
46
|
|
|
47
|
+
## 🧭 Intent routing (applies WITHOUT slash commands)
|
|
48
|
+
|
|
49
|
+
The workflows below are how work is done in this repo — **whether or not the user
|
|
50
|
+
types the slash command**. When a plain-language request matches an intent, read
|
|
51
|
+
the corresponding command file and follow its workflow:
|
|
52
|
+
|
|
53
|
+
| The user asks to… | Follow the workflow in |
|
|
54
|
+
|---|---|
|
|
55
|
+
| build/add/implement anything non-trivial | `.claude/commands/feature.md` (clarify → research → plan → implement → verify → document) |
|
|
56
|
+
| fix a bug, investigate an error or wrong behavior | `.claude/commands/fix.md` + the `root-cause` skill |
|
|
57
|
+
| choose between approaches / anything with a real trade-off | `.claude/commands/decide.md` (record the ADR) |
|
|
58
|
+
| start a new project or major subsystem | `.claude/commands/kickoff.md` |
|
|
59
|
+
| "where are we" / review progress | `.claude/commands/phase.md` |
|
|
60
|
+
|
|
61
|
+
Do not skip steps because the user phrased the request casually. "Can you quickly
|
|
62
|
+
add X" still gets clarifying questions if the design is ambiguous, still gets
|
|
63
|
+
verified, and still gets documented. Only genuinely trivial changes (typo, rename,
|
|
64
|
+
one-line tweak) may skip the plan — never the verification or the docs.
|
|
65
|
+
|
|
47
66
|
## Phase roadmap
|
|
48
67
|
|
|
49
68
|
<!-- TODO(onboard): bullet list of phases, one marked `← CURRENT`, each pointing
|