Find agent skills by outcome

RIGHT: if data fetch takes >300ms

show skeleton. If fetch fails

4. **Conditionals use explicit if/else

never as needed.**

If CSS: use rem as primary

px as annotation

RIGHT: `text-lg` (18px) at ≥768px

`text-base` (16px) below

If Tailwind: use Tailwind classes as primary

px as annotation

Before writing any specs

follow these formatting rules exactly:

**If the reader has to guess

infer

must have a rule. No as appropriate

no roughly

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

console.log('Page title:'

title);

await page.fill('#username'

'testuser');

await page.fill('#password'

'password123');

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)

simple version

then go deeper. A reader should be able to stop

8. Format for scannability. Use headers

bold key terms

Not to scare

but to prepare. If the payment service goes down

5. Be honest about problems. Flag technical debt

known issues

someone actually WANTS to read

not something they're forced to.