design
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
Best use case
design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
Teams using design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design Compares
| Feature / Agent | design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Design Thinking Process Work through the full design thinking process—Empathize, Define, Ideate, Prototype, Test. ## Instructions Move through each phase, building on insights from the previous one. The process is iterative—expect to loop back based on what you learn. ### Output Format **Challenge**: [What we're trying to solve] **Users**: [Who we're designing for] --- ## 1. EMPATHIZE *Understand the user and their context* ### User Profile | Attribute | Description | |-----------|-------------| | Who are they? | [Demographics, role] | | What's their context? | [Environment, circumstances] | | What are they trying to do? | [Goals, tasks] | ### User Pain Points | Pain Point | Severity | Current Workaround | |------------|----------|-------------------| | [pain] | High/Med/Low | [how they cope] | ### Empathy Map | Quadrant | Observations | |----------|--------------| | **Say** | [Quotes, statements] | | **Think** | [Beliefs, concerns] | | **Do** | [Actions, behaviors] | | **Feel** | [Emotions, reactions] | --- ## 2. DEFINE *Frame the problem worth solving* ### Point of View Statement **[User]** needs **[need]** because **[insight]**. ### How Might We Questions - How might we [opportunity 1]? - How might we [opportunity 2]? ### Problem Statement > **The Challenge**: [Specific, actionable problem to solve] --- ## 3. IDEATE *Generate many possible solutions* ### Ideas Generated | # | Idea | Type | |---|------|------| | 1 | [idea] | Safe / Moderate / Wild | | 2 | [idea] | Safe / Moderate / Wild | | 3 | [idea] | Safe / Moderate / Wild | ### Top Ideas to Prototype | Idea | Why This One? | Feasibility | |------|---------------|-------------| | [idea] | [rationale] | High/Med/Low | --- ## 4. PROTOTYPE *Make ideas tangible quickly* **Idea to prototype**: [Which idea] **Prototype type**: Paper mockup / Wireframe / Physical model / Storyboard **What we're testing**: - [Assumption/question 1] - [Assumption/question 2] --- ## 5. TEST *Learn from real users* **Who to test with**: [User profile] **Questions to answer**: 1. [Question]? 2. [Question]? **Success indicators**: [What would indicate this works] **Failure indicators**: [What would indicate this fails] --- ## Next Iteration Based on what we learn, we'll likely need to revisit: - [ ] Empathize / [ ] Define / [ ] Ideate / [ ] Prototype / [ ] Test ## Guidelines - Empathy is research, not assumption—talk to real users - "How might we" keeps problems open and generative - Prototype to think, not just to test - Test early, test often, test cheaply $ARGUMENTS
Related Skills
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
dotnet-design-pattern-review
Review the C#/.NET code for design pattern implementation and suggest improvements.
designing-workflow-skills
Guides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure. Use when creating skills that involve sequential pipelines, routing patterns, safety gates, task tracking, phased execution, or any multi-step workflow. Also applies when reviewing or refactoring existing workflow skills for quality.
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", or "de-risk before building". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.
design-orchestration
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", or "fault tolerance". Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.
ddd-strategic-design
Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.
technical-design-doc-creator
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...
database-design
Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.