Find agent skills by outcome

6. **Every visual property is stated

never inherited by assumption.**

If CSS: use rem as primary

px as annotation

4. **Conditionals use explicit if/else

never as needed.**

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

`text-base` (16px) below

If Tailwind: use Tailwind classes as primary

px as annotation

must have a rule. No as appropriate

no roughly

Before writing any specs

follow these formatting rules exactly:

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

console.log('Page title:'

title);

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