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:
2026-03-27 16:49:48 +11:00
parent 5765875741
commit 87e596ddb2
6 changed files with 319 additions and 4 deletions

View File

@@ -19,4 +19,10 @@ Use the component-builder agent to handle this task. The user wants to build the
6. ALL visual values MUST come from the MUI theme — never hardcode
7. Write comprehensive Storybook stories covering all states
8. Verify the component renders in Storybook
9. Update all memory files when done
9. **Run internal QA** (stages 3-5 from `docs/reference/component-lifecycle.md`):
- Run `/audit` — fix all P0/P1 issues
- Run `/critique` (skip for simple utility atoms like Divider)
- Run `/harden` (skip for display-only atoms like Typography, Badge)
- Run `/polish` — final alignment, spacing, transitions
10. Present to user with summary and scores
11. Update all memory files when done

View File

@@ -20,4 +20,11 @@ Use the component-builder agent to handle this task. The user wants to build the
7. ALL visual values MUST come from the MUI theme — never hardcode
8. Write comprehensive Storybook stories with realistic content
9. Verify the component renders in Storybook
10. Update all memory files when done
10. **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 edge cases for interactive molecules
- Run `/polish` — final alignment, spacing, transitions
- Run `/typeset` if text-heavy (cards, form fields)
11. Present to user with summary and scores
12. Update all memory files when done

View File

@@ -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