Files
Parsons/.claude/skills/build-organism/SKILL.md
Richie 87e596ddb2 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>
2026-03-27 16:49:48 +11:00

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:

  1. Read all memory files and conventions before starting
  2. Check docs/memory/component-registry.md — confirm the organism is planned
  3. Verify all constituent molecules and atoms are marked done in the registry — if any are not, STOP and tell the user which dependencies need to be built first
  4. Create the component in src/components/organisms/{ComponentName}/
  5. Include: {ComponentName}.tsx, {ComponentName}.stories.tsx, index.ts
  6. Compose from existing molecule and atom components — import from @molecules/ and @atoms/
  7. Follow all rules in docs/conventions/component-conventions.md
  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. 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