Singular · overview
Skill Reference
Reference for the design skills, their arguments and the --skip-checks flag.
Design Skills
| Skill | Command | Description |
|---|---|---|
| Empathize | /design-empathize <name> | Research user needs, context, and existing patterns |
| Define | /design-define-component <name> | Create a component contract with specs and constraints |
| Ideate | /design-ideate <name> | Explore multiple design approaches |
| Prototype | /design-prototype <name> | Build the component in Figma via MCP |
| Test | /design-test <name> | Validate against WCAG and component contract |
| Export Tokens | /design-export-tokens | Export design tokens to CSS, Tailwind, or JSON |
| A11y Audit | /design-a11y-audit | Run comprehensive WCAG accessibility audit |
| Design Review | /design-design-review <name> | Generate Figma Slides presentation from design phases |
| System Overview | /design-system-overview | High-level design system summary |
Common Arguments
All design skills accept a component name as the primary argument:
/design-<phase> <component-name>The component name is used to namespace artifacts in .singularskills/design/<component-name>/.
Flags
--skip-checks
Skip the phase's gate (scripts/gate.sh) for this run. Before writing the artifact, the skill appends a skipped event naming that artifact to .singularskills/log.jsonl; in Claude Code, the gate hook allows the write only once that event is in the log.
/design-define-component button --skip-checksFigma
The Figma steps of the design skills (empathize, define, ideate, prototype, test and the Figma utilities) need a Figma MCP server configured in your agent; the pack ships none. See the design workflow page.