[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI may ask user whether to skip.
Quick Summary
Goal: Create structured UI/UX design specification documents from requirements or PBIs for developer handoff.
Workflow:
- Read Source — Extract UI requirements from PBI, story, or Figma URL
- Determine Complexity — Quick Spec (sections 1-4) vs Full Spec (all 7 sections)
- Build Component Inventory — List new vs existing components
- Define States & Tokens — Interactions, design tokens, responsive breakpoints
- Save Artifact — Output to
team-artifacts/design-specs/
Key Rules:
- If Figma URL provided, run
/figma-design first to extract specs
- Reference existing design system tokens from
docs/design-system/
- Include accessibility requirements (keyboard nav, ARIA labels, contrast)
Design Specification
Create structured UI/UX design specification documents from requirements or PBIs for developer handoff.
When to Use
- A PBI or user story needs a design spec before implementation
- Translating requirements into concrete UI layout, states, and tokens
- Documenting component inventory and interaction patterns
- Creating responsive breakpoint specifications
When NOT to Use
- Extracting specs from Figma -- use
figma-design first, then this skill
- Building the actual UI -- use
frontend-design or frontend-angular
- Full UX research and design process -- use
ux-designer
- Reviewing existing UI code -- use
web-design-guidelines
Prerequisites
Read before executing:
- The source PBI, user story, or requirements document
docs/design-system/ -- project design tokens (if applicable)
- Existing design specs in
team-artifacts/design-specs/ for format consistency
Workflow
Read source input
- IF Figma URL provided → run
/figma-design first to extract specs, then continue
- IF PBI/story → extract acceptance criteria and UI requirements
- IF verbal requirements → clarify with user before proceeding
Determine spec complexity
IF single form or simple component → Quick Spec (sections 1-4 only)
IF full page or multi-component view → Full Spec (all 7 sections)
IF multi-page flow → Full Spec + Flow Diagram
Build component inventory
- List all UI components needed
- Identify reusable vs feature-specific components
- Note existing components from shared component library or design system
Define states and interactions
- Default, hover, active, disabled, error, loading, empty states
- User interactions (click, drag, keyboard shortcuts)
- Transitions and animations
Extract design tokens
- Colors, typography, spacing, shadows, border-radius
- Reference existing design system tokens where possible
Document responsive behavior
- Mobile (320-767px), Tablet (768-1023px), Desktop (1024px+)
- What changes at each breakpoint (layout, visibility, sizing)
Save artifact
- Path:
team-artifacts/design-specs/{YYMMDD}-designspec-{feature-slug}.md
Output Format
# Design Spec: {Feature Name}
**Source:** {PBI/story reference}
**Date:** {YYMMDD}
**Status:** Draft | Review | Approved
## 1. Overview
{1-2 sentence summary of what this UI does}
## 2. Component Inventory
| Component | Type | Source | Notes |
| --------- | -------- | ---------------- | --------------------------- |
| UserCard | New | Feature-specific | Displays user avatar + name |
| DataTable | Existing | shared library | Reuse with custom columns |
## 3. Layout
{Description or ASCII wireframe of layout structure}
- Desktop: {layout description}
- Tablet: {layout changes}
- Mobile: {layout changes}
## 4. Design Tokens
| Token | Value | Usage |
| ---------- | -------------- | --------------------- |
| $primary | #1976D2 | Action buttons, links |
| $text-body | 14px/1.5 Inter | Body text |
| $gap-md | 16px | Section spacing |
## 5. States & Interactions
| Element | Default | Hover | Active | Disabled | Error |
| -------- | ---------- | ---------- | ---------- | ---------------- | ----- |
| Save btn | Blue/white | Darken 10% | Scale 0.98 | Gray/50% opacity | -- |
## 6. Accessibility
- Keyboard navigation order
- ARIA labels for interactive elements
- Color contrast compliance notes
## 7. Open Questions
- {Any unresolved design decisions}
Examples
Example 1: Simple form spec
Input: "Design spec for employee onboarding form"
Output: Quick Spec with sections 1-4 covering form fields (name, email, department dropdown, start date picker), validation rules, submit/cancel actions, and mobile stacking behavior.
Example 2: Complex dashboard spec
Input: "Design spec for recruitment pipeline dashboard with drag-and-drop columns"
Output: Full Spec covering Kanban board layout, candidate cards (component inventory), drag-and-drop interactions, column states (empty, populated, over-limit), filter bar, responsive collapse to list view on mobile, and accessibility for keyboard drag operations.
Related Skills
| Skill |
When to use instead |
ux-designer |
Full UX design process with research |
figma-design |
Extract specs from Figma designs |
frontend-design |
Build the actual UI implementation |
web-design-guidelines |
Review existing UI for compliance |
frontend-angular |
Angular 19 components, forms, state, API services |
IMPORTANT Task Planning Notes (MUST FOLLOW)
- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements
1---2name: design-spec3version: 2.0.04description: '[Project Management] Create UI/UX design specifications from requirements, PBIs, or user stories. Produces structured design spec documents with layout, typography, colors, interactions, and responsive breakpoints. Triggers on design spec, design specification, UI specification, component spec, layout spec, wireframe, mockup.'5allowed-tools: Read, Write, Edit, Grep, Glob6metadata:7 source: https://skillmd.com/skills/diegosouzapw/design-spec8---910> **[IMPORTANT]** Use `TaskCreate` to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI may ask user whether to skip.1112## Quick Summary1314**Goal:** Create structured UI/UX design specification documents from requirements or PBIs for developer handoff.1516**Workflow:**17181. **Read Source** — Extract UI requirements from PBI, story, or Figma URL192. **Determine Complexity** — Quick Spec (sections 1-4) vs Full Spec (all 7 sections)203. **Build Component Inventory** — List new vs existing components214. **Define States & Tokens** — Interactions, design tokens, responsive breakpoints225. **Save Artifact** — Output to `team-artifacts/design-specs/`2324**Key Rules:**2526- If Figma URL provided, run `/figma-design` first to extract specs27- Reference existing design system tokens from `docs/design-system/`28- Include accessibility requirements (keyboard nav, ARIA labels, contrast)2930# Design Specification3132Create structured UI/UX design specification documents from requirements or PBIs for developer handoff.3334## When to Use3536- A PBI or user story needs a design spec before implementation37- Translating requirements into concrete UI layout, states, and tokens38- Documenting component inventory and interaction patterns39- Creating responsive breakpoint specifications4041## When NOT to Use4243- Extracting specs from Figma -- use `figma-design` first, then this skill44- Building the actual UI -- use `frontend-design` or `frontend-angular`45- Full UX research and design process -- use `ux-designer`46- Reviewing existing UI code -- use `web-design-guidelines`4748## Prerequisites4950Read before executing:5152- The source PBI, user story, or requirements document53- `docs/design-system/` -- project design tokens (if applicable)54- Existing design specs in `team-artifacts/design-specs/` for format consistency5556## Workflow57581. **Read source input**59 - IF Figma URL provided → run `/figma-design` first to extract specs, then continue60 - IF PBI/story → extract acceptance criteria and UI requirements61 - IF verbal requirements → clarify with user before proceeding62632. **Determine spec complexity**6465 ```66 IF single form or simple component → Quick Spec (sections 1-4 only)67 IF full page or multi-component view → Full Spec (all 7 sections)68 IF multi-page flow → Full Spec + Flow Diagram69 ```70713. **Build component inventory**72 - List all UI components needed73 - Identify reusable vs feature-specific components74 - Note existing components from shared component library or design system75764. **Define states and interactions**77 - Default, hover, active, disabled, error, loading, empty states78 - User interactions (click, drag, keyboard shortcuts)79 - Transitions and animations80815. **Extract design tokens**82 - Colors, typography, spacing, shadows, border-radius83 - Reference existing design system tokens where possible84856. **Document responsive behavior**86 - Mobile (320-767px), Tablet (768-1023px), Desktop (1024px+)87 - What changes at each breakpoint (layout, visibility, sizing)88897. **Save artifact**90 - Path: `team-artifacts/design-specs/{YYMMDD}-designspec-{feature-slug}.md`9192## Output Format9394```markdown95# Design Spec: {Feature Name}9697**Source:** {PBI/story reference}98**Date:** {YYMMDD}99**Status:** Draft | Review | Approved100101## 1. Overview102103{1-2 sentence summary of what this UI does}104105## 2. Component Inventory106107| Component | Type | Source | Notes |108| --------- | -------- | ---------------- | --------------------------- |109| UserCard | New | Feature-specific | Displays user avatar + name |110| DataTable | Existing | shared library | Reuse with custom columns |111112## 3. Layout113114{Description or ASCII wireframe of layout structure}115116- Desktop: {layout description}117- Tablet: {layout changes}118- Mobile: {layout changes}119120## 4. Design Tokens121122| Token | Value | Usage |123| ---------- | -------------- | --------------------- |124| $primary | #1976D2 | Action buttons, links |125| $text-body | 14px/1.5 Inter | Body text |126| $gap-md | 16px | Section spacing |127128## 5. States & Interactions129130| Element | Default | Hover | Active | Disabled | Error |131| -------- | ---------- | ---------- | ---------- | ---------------- | ----- |132| Save btn | Blue/white | Darken 10% | Scale 0.98 | Gray/50% opacity | -- |133134## 6. Accessibility135136- Keyboard navigation order137- ARIA labels for interactive elements138- Color contrast compliance notes139140## 7. Open Questions141142- {Any unresolved design decisions}143```144145## Examples146147### Example 1: Simple form spec148149**Input:** "Design spec for employee onboarding form"150151**Output:** Quick Spec with sections 1-4 covering form fields (name, email, department dropdown, start date picker), validation rules, submit/cancel actions, and mobile stacking behavior.152153### Example 2: Complex dashboard spec154155**Input:** "Design spec for recruitment pipeline dashboard with drag-and-drop columns"156157**Output:** Full Spec covering Kanban board layout, candidate cards (component inventory), drag-and-drop interactions, column states (empty, populated, over-limit), filter bar, responsive collapse to list view on mobile, and accessibility for keyboard drag operations.158159## Related Skills160161| Skill | When to use instead |162| ----------------------- | ------------------------------------------------- |163| `ux-designer` | Full UX design process with research |164| `figma-design` | Extract specs from Figma designs |165| `frontend-design` | Build the actual UI implementation |166| `web-design-guidelines` | Review existing UI for compliance |167| `frontend-angular` | Angular 19 components, forms, state, API services |168169---170171**IMPORTANT Task Planning Notes (MUST FOLLOW)**172173- Always plan and break work into many small todo tasks174- Always add a final review todo task to verify work quality and identify fixes/enhancements