User Input
$ARGUMENTS
Outline
- Read
docs/skills/catalog.md#create-module. - Read
docs/modules.md— theStudioModulecontract and the 5 touchpoints. - Pin down the module shape:
id(kebab-case),navGroup, leaf-vs-parent nav,ownedPaths,required,defaultEnabled, and whether the first page is a real list page or aComingSoonplaceholder. - Produce the exact file list before editing:
features/<id>/module.ts,lib/modules/registry.ts,lib/modules/route-manifest.ts,app/(app)/<owned-path>/page.tsx,messages/en.json+messages/nl.json.
If the user has not explicitly approved implementation, stop with the plan and
file list. After approval, implement all five touchpoints, keeping
registry.ts and route-manifest.ts in lock-step (the dev-only drift check
throws otherwise) and route-manifest.ts icon-free/React-free. Then run the
designer-verify routine and confirm the new nav entry and Settings toggle
behave.