Find agent skills by outcome

Write the FORME.md with these sections

in this order:

- Tech stack (if you know it): [e.g.

Next.js

[Upload files

provide path

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

narrative

- What it does (one sentence): [e.g.

A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators]

- My role: [e.g.

I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions]

- Keep the same voice — if the original is casual

stay casual

Writing & Content

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

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

- If a technology was replaced

update the crew analogy (or equivalent)

Writing & Content

- 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

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

Creative

Maintenance Prompt for Design System

You are a design system auditor performing a sync check.

- 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

- Named presets table (name

duration

- Rules: when to animate

when not to

- Full palette with swatches description (name

hex

Each token entry: name

value

- Type scale table (name

size