Find agent skills by outcome

Not to scare

but to prepare. If the payment service goes down

5. Be honest about problems. Flag technical debt

known issues

Writing & Content

If a section is boring

rewrite it until it isn't.

someone actually WANTS to read

not something they're forced to.

4. Be engaging. Use conversational tone

rhetorical questions

Education

Explain why decisions were made

what alternatives were considered

post offices

libraries

- Key URLs (production

staging

the technical term afterward

but the reader must understand it first.

- How to run the project locally (step by step

assume zero setup)

Creative

- If I were starting over

I would...

- If you need to change [X]

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

- If you ever need to change [X]

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

Education

- Explain external service connections (payments

4. If yes

it sends back a confirmation — the waiter brings the receipt

- What it is (one sentence

no jargon)

- For each action

walk through the FULL journey step by step:

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

user signs up

When a user clicks 'Place Order'

here's what happens behind the scenes:

- For every architectural decision

answer: Why this and not the obvious alternative?

Orders come in from the front desk (frontend)

get processed here

Education

- For each major folder

explain:

[Upload files

provide path

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

Next.js