Find agent skills by outcome

- Type scale table (name

size

Communication

- Spacing scale (visual representation: 4

- Project name

description

Each token entry: name

value

Creative

CLAUDE.md Assembly

You are compiling the definitive CLAUDE.md design system reference file.

patterns (import paths

className conventions

Markdown

structured with headers per section. This will be directly

- State variants: default

hover

Coding & Debugging

- Content guidelines (label length

capitalization

- Maximum instances per viewport (e.g.

only 1 primary CTA per section)

Creative

- List every visual part (e.g.

Button = container + label + icon-left + icon-right)

- Size variants with exact token values (padding

font-size

- Name

type

- Component to document: [Component name

or all components from inventory]

(Claude

Cursor

## For Each Component

Document:

Education

For each decision

explain the trade-off. I may disagree with your consolidation

choices

so transparency matters more than confidence.,FALSE,TEXT,gokbeyinac

Creative

Component Documentation

You are a design systems documentarian creating the component specification

4. Decision log — every judgment call you made (why you merged X into Y

etc.)

2. Establish a consistent spacing scale (4px base recommended

flag deviations)

1. Merge values within 2px of each other (e.g.

14px and 15px → pick one

Named

immutable values. No semantic meaning.

- Radii: `radius-sm`

`radius-md`