- 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>
1.8 KiB
1.8 KiB
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| build-organism | Build an organism component (Navigation, PricingTable, etc.) | [ComponentName] |
Build an organism component for the FA Design System.
Use the component-builder agent to handle this task. The user wants to build the following organism component:
Component: $ARGUMENTS
Instructions for the agent:
- Read all memory files and conventions before starting
- Check
docs/memory/component-registry.md— confirm the organism is planned - Verify all constituent molecules and atoms are marked
donein the registry — if any are not, STOP and tell the user which dependencies need to be built first - Create the component in
src/components/organisms/{ComponentName}/ - Include:
{ComponentName}.tsx,{ComponentName}.stories.tsx,index.ts - Compose from existing molecule and atom components — import from
@molecules/and@atoms/ - Follow all rules in
docs/conventions/component-conventions.md - ALL visual values MUST come from the MUI theme — never hardcode
- Write comprehensive Storybook stories with realistic page-level content
- Verify the component renders in Storybook
- 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
/typesetif text-heavy - Run
/adapt— responsive check (organisms are layout components) - Run
/quieterif the organism handles sensitive moments (pricing, forms, errors) - Run
/clarifyif the organism has decision points or complex information
- Run
- Present to user with summary and scores
- Update all memory files when done