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.3 KiB
1.3 KiB
WP-45 — create-ssp bootstrap generator
Status: todo Phase: 8 — platform/DX/showcase Priority: P4 Depends on: WP-43, WP-44
Why
new-ssp is a manual fork-and-strip recipe. To actually bootstrap a production-ready frontend for
a different Dutch register quickly, mechanise it into a runnable script that produces a clean
scaffold keeping the enforced architecture + shared building blocks.
Decisions
- A
create-sspscript (Node/plop-driven) that clones-and-strips per thenew-ssprecipe: drop the business contexts, prune their routes/aliases/boundary entries, renameBigRegister.*, re-point the--rhc-*token bridge, re-seed the backend, re-rungen:api. - Keep-as-is list from
new-ssp(shared kernel/ui/layout, eslint/boundary config, check-tokens, CI, nswag, storybook, auth shell, ADRs, CLAUDE.md, the skills). - Reuse WP-44's
gen:contextto seed the first real context of the new portal.
Files
- New
scripts/create-ssp.*(+ any templates); documented in.claude/skills/new-ssp/SKILL.md.
Acceptance criteria
- Running it yields a portal that builds, lints (boundaries intact), and passes
npm run ciwith no business contexts left over. - The generated scaffold's
gen:api+ token bridge point at the new backend/theme. - Documented end-to-end in the
new-sspskill.