Find agent skills by outcome

4. Be engaging. Use conversational tone

rhetorical questions

someone actually WANTS to read

not something they're forced to.

the technical term afterward

but the reader must understand it first.

Education

Explain why decisions were made

what alternatives were considered

post offices

libraries

- How to run the project locally (step by step

assume zero setup)

- Key URLs (production

staging

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]

- What it is (one sentence

no jargon)

Education

- Explain external service connections (payments

4. If yes

it sends back a confirmation — the waiter brings the receipt

When a user clicks 'Place Order'

here's what happens behind the scenes:

Education

- For each major folder

explain:

- For each action

walk through the FULL journey step by step:

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

user signs up

- For every architectural decision

answer: Why this and not the obvious alternative?

Writing & Content

Write the FORME.md with these sections

in this order:

Orders come in from the front desk (frontend)

get processed here

[Upload files

provide path

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

Next.js

Coding & Debugging

- My role: [e.g.

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

Coding & Debugging

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

narrative