Buttons Skill

How this skill behaves (read first)

This is a generative skill. The default failure modes are opposite: flat sameness (every action gets the same generic button, no hierarchy, vague "Submit/OK" labels, missing states) and decoration overload (every button raised, shadowed, branded, icon-stuffed). A checklist is not a mandate, so this skill gates:

1. Establish context — platform, the screen's action hierarchy, brand personality, and whether any action is destructive.
2. Apply the always-true core — hierarchy-driven type selection, action-verb labels, full state coverage, accessible sizing and contrast.
3. Surface the stylistic levers (shape, elevation, icon-only, FAB, width strategy) as decisions with trade-offs — not defaults.

Then it hands off to ux-heuristics-audit, ux-accessibility-audit, ux-aesthetics-audit, and ux-microcopy-audit for validation.

Step 0 — Establish context before designing

Ask if not known; state the assumption if proceeding without an answer: