ss-page

# Product Page Scaffolder ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. ## When NOT to use - For a single composed pattern within an existing page → use `/ss-pattern` - For multi-page navigation structure → use `/ss-flow` first - For tweaking an existing page — edit the file directly Create a new page: **$0** Description: $ARGUMENTS ## Instructions 1. Resolve and read the active design method: - If either registry file exists, require a complete valid registry and resolve the selected artifact with `--artifact <id>`. Read `.styleseed/bundles/<id>.md` and `.styleseed/manifests/<id>.json`; never restart setup or use a legacy fallback on errors. - Only when neither registry file exists, resolve `STYLESEED.md` and read `.styleseed/effective-rules.md` and `.styleseed/manifest.json`. - For missing/stale outputs in this authorized build, resolve from the corresponding project-owned configuration and re-check without changing approved decisions. - `components/patterns/page-shell.tsx` for page layout - `components/patterns/top-bar.tsx` for header pattern - `components/patterns/bottom-nav...