Find agent skills by outcome

1. Inspect the existing codebase

components

Think of our tech stack as a crew

each member with a specialty:

Coding & Debugging

Dependencies: React 18

Next.js 14

Coding & Debugging

static regeneration

utilizing Next.js App Router with React Server

When someone visits our site

the server pre-builds the page before

8. Format for scannability. Use headers

bold key terms

paragraphs

and bullet points for lists. But use prose (not bullets)

simple version

then go deeper. A reader should be able to stop

Not to scare

but to prepare. If the payment service goes down

5. Be honest about problems. Flag technical debt

known issues

someone actually WANTS to read

not something they're forced to.

4. Be engaging. Use conversational tone

rhetorical questions

post offices

libraries

the technical term afterward

but the reader must understand it first.

- Key URLs (production

staging

- How to run the project locally (step by step

assume zero setup)

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

When a user clicks 'Place Order'

here's what happens behind the scenes:

4. If yes

it sends back a confirmation — the waiter brings the receipt

- For each action

walk through the FULL journey step by step:

- For every architectural decision

answer: Why this and not the obvious alternative?

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

user signs up