atomic-design-poc/docs/project/backlog/WP-45-create-ssp-generator.md

WP-45 — create-ssp bootstrap generator

Status: done (ad7ca31) 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-ssp script (Node/plop-driven) that clones-and-strips per the new-ssp recipe: drop the business contexts, prune their routes/aliases/boundary entries, rename BigRegister.*, re-point the --rhc-* token bridge, re-seed the backend, re-run gen: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:context to 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 ci with 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-ssp skill.