brand-rulesWrite and check the brand files of a product - DESIGN.md (the visual rules), PRODUCT.md (users, terms, and voice), and design tokens in the DTCG format - and split the rules into hard rules that a script checks and soft rules for the review. Use when a project has no DESIGN.md, PRODUCT.md, or tokens
claude-designUse Claude Design with the Design and Design System artifact types - read a Claude Design System as the design-system source, turn checked HTML mockups into a Design canvas with one artboard for each state, and make or update a Design System from DTCG tokens. Use when the design facts of the project
figmaWork with Figma through the official Figma MCP server - read frames, variables, and Code Connect in a fixed order with a call budget, map the Figma variables to the project tokens, and write mockups only in a draft or duplicate file with the official figma-use skill. Use when the design facts of the
openpencilDesign with OpenPencil (.op files, the op CLI, the OpenPencil MCP server) - put checked HTML mockups into OpenPencil with one frame for each state, then edit them with the openpencil-design skill. Use when the design facts of the project (the "## Design" section) name OpenPencil as a design tool or
ui-craftVisual design method for app screens - surface type, hierarchy, grid, type roles, spacing rhythm, color roles, density, and detail, in a fixed order, with a rubric to score concepts and mockups and a list of AI tells. Use when a screen, a concept, or a mockup must be designed or judged on its visual
ux-designRuns the UX design of one item with UI work before the build - the design spec, the mockups of each state, and a prototype for a test with users - with the ux-designer agent, from the ticket to the approved design in the work folder of the item. Sends the state examples and the proposed decisions to
ux-patternsDecision tables that select an interaction pattern from the facts of a task - table or cards, page or modal or side panel, inline edit or form, pagination, filters, bulk and destructive actions, feedback for slow work, empty states, input controls, and icons and toggles. Use when a screen, a list, a
ux-practiceThe method of the ux-designer agent for the UX design of a story, a feature, or a screen - Double Diamond phases, a design spec with a source for each decision, the UX decision log, evidence tags, severity, and the modes light, full, and new-direction. Preloaded by the ux-designer agent. Use when th
ux-prototypeClickable prototype of a designed story in the proto-shell standard, with variants for an A/B test, all states in scope, three sizes, and a test plan with tasks. Use when a design or mockups exist and the team must test the flow or compare variants with users before the build.
ux-reviewUX review of a built feature against its approved design - Playwright walks each flow and state at 390, 820, and 1440 px, axe-core and the tell checks run on each state, and each heuristic gets a verdict - with findings by owner, severity, and origin, and a verdict in ux-review.md in the work folder
ux-setupSet up a project for UX work - finds the design tools, the design-system source, the brand files, the languages, and the run command, asks the human one round of questions, and writes the "## Design" section of .claude/rules/delivery.md that the ux-design commands and the ux-designer agent read. Mov
ux-statesState inventory for each screen - default, empty, loading, partial, error, success, disabled, overflow, offline, and the business states (no permission, stale data, locked by another user, waiting on an external system, bulk result with failures, read only) - with what the user sees, can do, and how
web-accessibilityWeb accessibility to WCAG 2.2 AA - a checklist for the design, the tool checks (axe-core, the Tab walk, reduced motion), and the manual checks that no tool does (screen reader, zoom, status messages) - with the EAA and EN 301 549 status. Use when a design, mockup, or built feature must be checked fo