Skill Detail
One design skill, with explicit modes and rigorous playbooks.
The single public design entrypoint for system creation, playgrounds, UI/token/component/accessibility audits, implementation, proof, verification, and shipping.
Problem
Design work spans tokens, components, layout, accessibility, screenshots, and implementation. Without one public entrypoint, the operator has to choose among overlapping commands and determine when centralization still needs a site-wide migration.
Outcome
You get the right design route: audit, token creation, playground, component or accessibility review, spec-first implementation, browser proof, verification, and ship routing when the work is ready.
Why It Matters
This is the practical default when the request is simply about design. It keeps specialist quality without making you memorize the design-system workflow.
Arguments
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
system [scope]Loads the design-system creation playbook from existing UI evidence.
Use when no coherent token authority exists.
audit <ui|tokens|components|a11y> [scope]Loads exactly the named audit playbook; bare audit asks for a subtype.
Use for a bounded professional diagnosis without another public command.
playground [route-path]Routes to the design-system playground when a token layer exists.
Useful for live visual token review.
redesign [scope]Audits the current surface, resolves visual direction, and routes broad implementation through a ready spec.
Use when the intended result changes visual direction rather than only repairing drift.
migration [scope]Measures design-token consumption and routes a bounded cross-surface migration through the lifecycle.
Use when the authority exists but pages or components still bypass it.
Related Skills
Run non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill pageCheck whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.