Find agent skills by outcome

**If the reader has to guess

infer

The core philosophy: If an AI reads this document and has to guess anything

the document has failed.

page.on('console'

msg => console.log('Browser log:'

await page.waitForSelector('#element-id'

{ state: 'visible' });

await page.fill('#password'

'password123');

await page.fill('#username'

'testuser');

Web Application Testing Skill (Imported)

---

console.log('Page title:'

title);

Improve visual hierarchy

clarity

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

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]

- If you ever need to change [X]

be careful because it also affects [Y] and [Z]