Find agent skills by outcome

someone actually WANTS to read

not something they're forced to.

the technical term afterward

but the reader must understand it first.

post offices

libraries

- How to run the project locally (step by step

assume zero setup)

- Key URLs (production

staging

- 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)

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:

- 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?

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

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

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

- 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

2. Impact Assessment: For each change

determine:

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

- Summary stats: X new tokens

Y deprecated