Find agent skills by outcome

must have a rule. No as appropriate

no roughly

Before writing any specs

follow these formatting rules exactly:

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

console.log('Page title:'

title);

await page.fill('#username'

'testuser');

Improve visual hierarchy

clarity

Web Application Testing Skill (Imported)

---

Think of our tech stack as a crew

each member with a specialty:

When someone visits our site

the server pre-builds the page before

paragraphs

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

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

Not to scare

but to prepare. If the payment service goes down

someone actually WANTS to read

not something they're forced to.

4. Be engaging. Use conversational tone

rhetorical questions

- Key URLs (production

staging

post offices

libraries

the technical term afterward

but the reader must understand it first.

- If you ever need to change [X]

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

- How to run the project locally (step by step

assume zero setup)