Add component lifecycle + retroactive review plan
- docs/reference/component-lifecycle.md: 10-stage quality gate sequence (build → stories → audit/critique/harden → fix → polish → present → iterate → normalize → preflight → commit) - docs/reference/retroactive-review-plan.md: Plan to review 30+ existing components using condensed process (~3.5 sessions) - Updated /build-atom, /build-molecule, /build-organism to include internal QA stages automatically - CLAUDE.md: added lifecycle reference as critical rule #8 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -21,4 +21,14 @@ Use the component-builder agent to handle this task. The user wants to build the
|
||||
8. ALL visual values MUST come from the MUI theme — never hardcode
|
||||
9. Write comprehensive Storybook stories with realistic page-level content
|
||||
10. Verify the component renders in Storybook
|
||||
11. Update all memory files when done
|
||||
11. **Run internal QA** (stages 3-5 from `docs/reference/component-lifecycle.md`):
|
||||
- Run `/audit` — fix all P0/P1 issues
|
||||
- Run `/critique` — fix all P0/P1 issues
|
||||
- Run `/harden` — check all edge cases (organisms handle real data)
|
||||
- Run `/polish` — final alignment, spacing, transitions
|
||||
- Run `/typeset` if text-heavy
|
||||
- Run `/adapt` — responsive check (organisms are layout components)
|
||||
- Run `/quieter` if the organism handles sensitive moments (pricing, forms, errors)
|
||||
- Run `/clarify` if the organism has decision points or complex information
|
||||
12. Present to user with summary and scores
|
||||
13. Update all memory files when done
|
||||
|
||||
Reference in New Issue
Block a user