ehoandClaude Opus 4.8
a828e604d1
New phase from the 5-item analysis: linked showcase snippets + animations, runnable scaffolding generators (pages/wizards/context/SSP), dependency graph + declarative boundaries, PII hardening (branded Bsn VO + masked-value atom + persisted no-PII audit) doubling as a privacy showcase, and Vitest coverage. Goal: both a teaching showcase and a production starter template. Sequenced with priorities + dependencies in the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
# WP-43 — Runnable leaf generators
|
|
|
|
Status: todo
|
|
Phase: 8 — platform/DX/showcase
|
|
Priority: P3
|
|
|
|
## Why
|
|
|
|
The house patterns (value object, form machine, bff endpoint, ui component) are documented only as
|
|
agent-executed prose skills; there's no `npm run gen:*` a developer runs to emit the boilerplate.
|
|
For a template meant to bootstrap real registers, mechanise the highest-churn recipes.
|
|
|
|
## Decisions
|
|
|
|
- **Step 1 — tool fork:** plop (recommended: tiny, readable templates, `npm run gen:*`) vs Angular
|
|
schematics (native `ng generate`, heavier to author). Decide before building.
|
|
- Generators emit house-pattern files **with co-located spec/story**, matching current idioms:
|
|
`gen:value-object`, `gen:form-machine` (page/wizard), `gen:bff-endpoint`, `gen:ui-component`.
|
|
- Templates become the single source; each matching skill gets a one-line "run `npm run gen:x`, then …".
|
|
|
|
## Files
|
|
|
|
- New `plopfile.mjs` (or `schematics/`) + template files; `package.json` `gen:*` scripts.
|
|
- Update the corresponding `.claude/skills/*/SKILL.md` to invoke the generator.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] Each generator emits files that pass `npm run lint` + `npm run ci` with no hand-edits beyond
|
|
filling in the domain specifics.
|
|
- [ ] Generated units include their spec/story per house rules.
|
|
- [ ] A smoke run of each generator is documented; `npm run ci` green.
|