Files
Parsons/.claude/skills/build-organism/SKILL.md
Richie 732c872576 Initial commit: FA 2.0 Design System foundation
Token pipeline (Style Dictionary v4, DTCG format):
- Primitive tokens: colour palettes (brand, sage, neutral, feedback),
  typography (3 font families, 21-variant type scale), spacing (4px grid),
  border radius, shadows, opacity
- Semantic tokens: text, surface, border, interactive, feedback colours;
  typography roles; layout spacing
- Component tokens: Button (4 sizes), Input (2 sizes)
- Generated outputs: CSS custom properties, JS ES6 module, flat JSON

Atoms (3 components):
- Button: contained/soft/outlined/text × primary/secondary, 4 sizes,
  loading state, underline for text variant
- Typography: 21 variants across display/heading/body/label/caption/overline,
  maxLines truncation
- Input: external label, helper text, error/success validation,
  start/end icons, required indicator, 2 sizes, multiline support

Infrastructure:
- MUI v5 theme with full token mapping
- Storybook 8 with autodocs
- Claude Code agents and skills for token/component workflows
- Design system documentation and cross-session memory

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-25 15:08:15 +11:00

25 lines
1.2 KiB
Markdown

---
name: build-organism
description: Build an organism component (Navigation, PricingTable, etc.)
argument-hint: "[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. Update all memory files when done