Menu

Individual skill

ux-buttons

0upvotes

Design or critique UI buttons — pick the right button type for the action's importance, apply sizing/label/state best practices, and gate stylistic levers like shape, shadows, FABs, and icon-only buttons. Trigger when the user asks to design, choose, style, or review buttons, CTAs, button labels, button hierarchy, or button states.

ux/components/buttons/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.

---
Back to top