Find agent skills by outcome

- Write the REPLACEMENT text (not the whole document

just the changed parts)

2. Impact Assessment: For each change

determine:

- Maintain the same tone

analogy system

Update/Sync Prompt

You are updating an existing FORME.md documentation file to reflect

- Known changes (if any): [e.g.

We added Stripe integration and switched from REST to tRPC — or I don't know what changed

Identify what's new

what changed

Coding & Debugging

- Code that breaks CLAUDE.md rules (inline colors

missing focus states

- Summary stats: X new tokens

Y deprecated

- Named presets table (name

duration

Coding & Debugging

CLAUDE.md and the actual code

the CLAUDE.md should be updated to

- Rules: when to animate

when not to

Each token entry: name

value

- Type scale table (name

size

- Full palette with swatches description (name

hex

- Project name

description

Coding & Debugging

- Content guidelines (label length

capitalization

Markdown

structured with headers per section. This will be directly

patterns (import paths

className conventions

- Maximum instances per viewport (e.g.

only 1 primary CTA per section)

- State variants: default

hover

- Size variants with exact token values (padding

font-size

- Name

type

## For Each Component

Document:

- Component to document: [Component name

or all components from inventory]