Find agent skills by outcome

| 3 | Button | `src/components/ui/Button.tsx` | Tokens

Typography | Medium | 3 variants × 3 sizes × 6 states |

4. **Conditionals use explicit if/else

never as needed.**

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

`text-base` (16px) below

If CSS: use rem as primary

px as annotation

Before writing any specs

follow these formatting rules exactly:

If Tailwind: use Tailwind classes as primary

px as annotation

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

await page.fill('#password'

'password123');

Web Application Testing Skill (Imported)

---

await page.fill('#username'

'testuser');

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

8. Format for scannability. Use headers

bold key terms

Not to scare

but to prepare. If the payment service goes down

simple version

then go deeper. A reader should be able to stop

someone actually WANTS to read

not something they're forced to.

5. Be honest about problems. Flag technical debt

known issues