Richie
87e596ddb2
- 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.2 KiB
1.2 KiB
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| build-atom | Build an atom component (Button, Input, Typography, etc.) | [ComponentName] |
Build an atom component for the FA Design System.
Use the component-builder agent to handle this task. The user wants to build the following atom component:
Component: $ARGUMENTS
Instructions for the agent:
- Read all memory files and conventions before starting
- Check
docs/memory/component-registry.mdto confirm the component is planned - Create the component in
src/components/atoms/{ComponentName}/ - Include:
{ComponentName}.tsx,{ComponentName}.stories.tsx,index.ts - Follow all rules in
docs/conventions/component-conventions.md - ALL visual values MUST come from the MUI theme — never hardcode
- Write comprehensive Storybook stories covering all states
- 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(skip for simple utility atoms like Divider) - Run
/harden(skip for display-only atoms like Typography, Badge) - Run
/polish— final alignment, spacing, transitions
- Run
- Present to user with summary and scores
- Update all memory files when done