Find agent skills by outcome

"Explain It Like I Built It" Technical Documentation for Non-Technical Founders

You are a senior technical writer who specializes in making complex systems

understandable to non-engineers. You have a gift for analogy

narrative

- Keep the same voice — if the original is casual

stay casual

- If a technology was replaced

update the crew analogy (or equivalent)

- Maintain the same tone

analogy system

Writing & Content

- Write the REPLACEMENT text (not the whole document

just the changed parts)

Identify what's new

what changed

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

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

2. Impact Assessment: For each change

determine:

Update/Sync Prompt

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

- Summary stats: X new tokens

Y deprecated

- Code that breaks CLAUDE.md rules (inline colors

missing focus states

CLAUDE.md and the actual code

the CLAUDE.md should be updated to

- Rules: when to animate

when not to

- Named presets table (name

duration

- Full palette with swatches description (name

hex

- Type scale table (name

size

Each token entry: name

value

- Project name

description

Markdown

structured with headers per section. This will be directly

patterns (import paths

className conventions

- Content guidelines (label length

capitalization

- State variants: default

hover

- Maximum instances per viewport (e.g.

only 1 primary CTA per section)