Find agent skills by outcome

simple version

then go deeper. A reader should be able to stop

Writing & Content

If a section is boring

rewrite it until it isn't.

someone actually WANTS to read

not something they're forced to.

5. Be honest about problems. Flag technical debt

known issues

Education

Explain why decisions were made

what alternatives were considered

post offices

libraries

4. Be engaging. Use conversational tone

rhetorical questions

- How to run the project locally (step by step

assume zero setup)

- Key URLs (production

staging

the technical term afterward

but the reader must understand it first.

Creative

- If I were starting over

I would...

- If you ever need to change [X]

be careful because it also affects [Y] and [Z]

- If you need to change [X]

you'd update [Y] — but be careful because [Z]

4. If yes

it sends back a confirmation — the waiter brings the receipt

Education

- Explain external service connections (payments

- What it is (one sentence

no jargon)

When a user clicks 'Place Order'

here's what happens behind the scenes:

- Pick 2-3 core user actions (e.g.

user signs up

- For each action

walk through the FULL journey step by step:

Orders come in from the front desk (frontend)

get processed here

- For every architectural decision

answer: Why this and not the obvious alternative?

Education

- For each major folder

explain:

Writing & Content

Write the FORME.md with these sections

in this order:

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

Next.js