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>
1.2 KiB
1.2 KiB
WP-44 — gen:context generator
Status: todo Phase: 8 — platform/DX/showcase Priority: P3 Depends on: WP-38, WP-43
Why
Adding a bounded context is currently a manual multi-file edit (folders + tsconfig alias + copied
ESLint boundary block + lazy route) — the new-context skill's most error-prone steps. Mechanise it.
Decisions
gen:context(same tool as WP-43) emits{domain,application,infrastructure,ui,contracts}folders + the@ctx/*tsconfig path alias + a lazy route + the boundary entry.- Simpler because of WP-38: boundaries are declarative by then, so the generator adds one config entry instead of hand-copying ESLint blocks.
- Replaces the manual portion of the
new-contextskill.
Files
- Extend the WP-43 generator setup with a
contextgenerator + templates. - Wire tsconfig alias + boundary config + route insertion (idempotent edits).
- Update
.claude/skills/new-context/SKILL.md.
Acceptance criteria
npm run gen:context <name>produces a context that lints clean (boundaries recognised) and routes lazily.- Boundary tool (WP-38) validates the new context's allowed edges.
npm run cigreen.