UI Design Skills for Claude

UI design skills for Claude write down a project's visual rules in a form the model can actually follow: which spacing scale is in use, which colors are allowed, how component states are defined. Without them Claude reinvents the styling on every run and the interface drifts apart quickly — especially when several people build components in parallel.

The key to a working design skill is tokens instead of adjectives. "Make it clean and modern" carries no information for a model and produces arbitrary output. "Spacing only from the 4/8/12/16/24 scale, colors only from these variables, one corner radius across the project" is reproducible and checkable.

The second layer is accessibility. Text contrast, tap target size, a visible keyboard focus state, behavior under reduced motion — these are rules with unambiguous verification, and keeping them in a skill is more reliable than catching them during design review.

The collection below covers design systems, interface markup and landing pages.

Skills in this collection

FAQ

Can Claude Code build an interface from a Figma file?

Yes, when Figma access is wired in through the matching MCP server — the model then reads the file structure, variables and tokens. The skill's job in that pipeline is deciding what the design becomes: which components, under which class names, and by which responsive rules.

How do I stop the model from inventing new styling every time?

Give the skill closed sets: the list of allowed colors, the spacing scale, the set of radii and shadows, the type scale. While the choice is bounded by a list, output stays inside the system. The moment a rule is phrased as "a modern look", the variance comes back.

All Claude Code skills