Find agent skills by outcome

Think of our tech stack as a crew

each member with a specialty:

Coding & Debugging

Dependencies: React 18

Next.js 14

Productivity

App Router for this

which is like the kitchen's workflow system that

Coding & Debugging

static regeneration

utilizing Next.js App Router with React Server

paragraphs

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

When someone visits our site

the server pre-builds the page before

8. Format for scannability. Use headers

bold key terms

Not to scare

but to prepare. If the payment service goes down

simple version

then go deeper. A reader should be able to stop

Writing & Content

If a section is boring

rewrite it until it isn't.

someone actually WANTS to read

not something they're forced to.

5. Be honest about problems. Flag technical debt

known issues

Education

Explain why decisions were made

what alternatives were considered

post offices

libraries

4. Be engaging. Use conversational tone

rhetorical questions

- How to run the project locally (step by step

assume zero setup)

- Key URLs (production

staging

the technical term afterward

but the reader must understand it first.

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]

4. If yes

it sends back a confirmation — the waiter brings the receipt

Education

- Explain external service connections (payments

- What it is (one sentence

no jargon)