Find agent skills by outcome

Web Application Testing Skill (Imported)

---

Think of our tech stack as a crew

each member with a specialty:

Improve visual hierarchy

clarity

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)

Not to scare

but to prepare. If the payment service goes down

simple version

then go deeper. A reader should be able to stop

5. Be honest about problems. Flag technical debt

known issues

4. Be engaging. Use conversational tone

rhetorical questions

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