Find agent skills by outcome

Dependencies: React 18

Next.js 14

Think of our tech stack as a crew

each member with a specialty:

paragraphs

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

When someone visits our site

the server pre-builds the page before

Coding & Debugging

static regeneration

utilizing Next.js App Router with React Server

Not to scare

but to prepare. If the payment service goes down

8. Format for scannability. Use headers

bold key terms

simple version

then go deeper. A reader should be able to stop

5. Be honest about problems. Flag technical debt

known issues

someone actually WANTS to read

not something they're forced to.

post offices

libraries

4. Be engaging. Use conversational tone

rhetorical questions

- Key URLs (production

staging

- How to run the project locally (step by step

assume zero setup)

the technical term afterward

but the reader must understand it first.

- If you need to change [X]

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

Creative

- If I were starting over

I would...

- If you ever need to change [X]

be careful because it also affects [Y] and [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

Orders come in from the front desk (frontend)

get processed here