ui-ux-design-principles — Claude Code skill for UI/UX rules

What ui-ux-design-principles does

The skill gives a shared vocabulary for interface work: usability heuristics, visual hierarchy, accessibility, feedback on actions, information architecture, design tokens, testability. Everything inside is markdown, no scripts — you consult it rather than run it. Each rule points at how it gets checked: the E2E layer with Playwright, a design-adherence pass against design-guide.json, a11y checks. A rule no test defends stays advice; one a check defends joins the build.

The core is a checklist to clear before merge. Seven properties: success and failure feedback on every data-changing action, keyboard and screen-reader access, visual hierarchy, token reuse, screens and flows defined up front, stable selectors such as data-testid, and a loading state for anything past roughly 200 ms with no layout shift. A blank row is fine when scope justifies it. A row nobody considered is the smell.

This is the third of a trio: software-design-principles covers code, architectural-design-principles covers the system, and this one covers how the product looks and how people move through it. In consort the UX Designer pulls it in to author design-guide.{md,json} and ia.md and to set the adherence contract; the Driver pulls it in while building UI. Without ia.md and without an a11y check there is nothing to close the checklist with, so create both before the first line of markup.