sp-design

Generates and audits a DESIGN.md design-system contract before UI implementation work.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-design-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-design
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-design
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-design-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI work often starts without a stable visual and interaction system, leading to inconsistent styling, ad-hoc tokens, and rework. This Skill produces, refines, synthesizes, or audits a root DESIGN.md design-system contract so downstream specification, planning, and implementation workflows consume an approved design baseline. ## Core Features & Use Cases - Design-system synthesis: Create or refine DESIGN.md with spec-kit-design-v1 YAML front matter, token categories for color, spacing, radius, and typography, plus component state rules and accessibility intent. - Four operating modes: create, synthesize, refine, or audit an existing design system, with two or three project-specific design directions and inspectable visual artifacts for user approval. - Workflow governance: Enforces a phase lock with allowed and forbidden writes, a blocked-exit contract, review artifacts under .specify/design/, and a single recommended next command such as /sp.specify or /sp.plan. - Use Case: Before building a new product dashboard, run the design workflow to produce an approved DESIGN.md with tokens, component rules, and a UI QA checklist, then hand off to specification and planning. ## Quick Start Ask the agent to run the sp-design workflow to create a DESIGN.md design system for the current spec-kit project before any UI implementation begins.

Frequently Asked Questions about sp-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a design system before starting UI implementation?▼

Run the sp-design workflow in a spec-kit project. It reads project context, proposes two or three design directions with visual artifacts, and writes an approved DESIGN.md with tokens, component rules, and accessibility intent after you approve a direction.

What does the DESIGN.md output file contain?▼

DESIGN.md contains spec-kit-design-v1 YAML front matter with approval status, product context, token categories for color, spacing, radius, and typography, plus Markdown sections for Product Feel, Platforms, Component Rules, Anti-Patterns, UI QA Checklist, and Design Change Policy.

Does sp-design require a spec-kit project structure?▼

Yes, it requires a .specify/ directory. It stores state and review artifacts under .specify/design/ and reads shared templates and memory files, so it only works inside spec-kit-style projects.

Can sp-design write UI code or CSS files?▼

No. The workflow explicitly forbids writing source code, UI components, CSS or theme implementation files, tests, and plan or task artifacts. It is design-only and hands off to downstream workflows for implementation.

What happens if the design workflow gets blocked?▼

It follows a blocked-exit contract using .specify/templates/workflow-blocker-template.md, preserving state and defining agent-owned repair steps. It only marks human action as required for authority, credentials, or human decisions, and never claims false completion.