Handbook
Page implementation micro-prompt
Implement or redesign [PAGE NAME] at [ROUTE] for [PRIMARY PERSONA].
Updated
Before editing:
- Read feature row [FEATURE ID], external page [PATH], internal spec [PATH], role matrix, route map, and design rules.
- Inspect existing route, components, API, permissions, tests, and related pages.
- Report assumptions, files, authorization/data classes, states, and test plan.
Page purpose: [ONE SENTENCE]
Primary action: [ACTION]
Secondary actions: [ACTIONS]
Required layout:
- Product page header with title, purpose, scope/status, primary action
- [SECTIONS]
- Responsive behavior: [MOBILE/TABLET/DESKTOP]
Required states:
- Loading
- First-use empty
- Filtered empty
- Partial/incomplete
- Recoverable error
- Permission limited
- Success/confirmation
- Archived/retired if applicable
Constraints:
- Reuse shared components/tokens.
- Enforce permission server-side.
- No raw JSON, IDs, secrets, or system jargon.
- No sensitive content in analytics/logs.
- Add contextual docs link.
Acceptance criteria:
- [LIST]
Tests:
- Unit/component
- Authorization negative
- Accessibility/keyboard
- Responsive
- End-to-end happy and failure path
After implementation, update both wikis, traceability, tests, and release notes where user-visible.