design-thinking

melodic-software/claude-code-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/melodic-software/claude-code-plugins --skill design-thinking
0 commentsdiscussion
summary

Use this skill when:

skill.md

Design Thinking

When to Use This Skill

Use this skill when:

  • Design Thinking tasks - Working on design thinking methodology for human-centered innovation. covers the 5-phase ideo/stanford d.school approach (empathize, define, ideate, prototype, test) with workshop facilitation and exercise templates
  • Planning or design - Need guidance on Design Thinking approaches
  • Best practices - Want to follow established patterns and standards

Overview

A human-centered approach to innovation that integrates the needs of people, the possibilities of technology, and the requirements for business success.

What is Design Thinking?

Design Thinking is a problem-solving methodology developed by IDEO and taught at Stanford d.school. It emphasizes understanding users, challenging assumptions, redefining problems, and creating innovative solutions through iterative prototyping and testing.

Core Principles

Principle Description
Human-Centered Start with people, not technology or process
Embrace Ambiguity Comfortable with uncertainty early on
Bias to Action Learn by doing, not just thinking
Radical Collaboration Cross-functional, diverse perspectives
Iterate Rapidly Fail fast, learn fast, improve fast

The 5 Phases

┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐
│         │  │         │  │         │  │         │  │         │
│EMPATHIZE│→│ DEFINE  │→│ IDEATE  │→│PROTOTYPE│→│  TEST   │
│         │  │         │  │         │  │         │  │         │
│Understand│  │Frame the│  │Generate │  │Build to │  │Learn &  │
│the user │  │problem  │  │ideas    │  │learn    │  │refine   │
└─────────┘  └─────────┘  └─────────┘  └─────────┘  └─────────┘
     ▲                                                    │
     └────────────────── Iterate ─────────────────────────┘

Phase Characteristics

Phase Mode Key Question Output
Empathize Diverge What is the user experiencing? Insights, observations
Define Converge What is the core problem? POV statement
Ideate Diverge What are possible solutions? Ideas, concepts
Prototype Converge How can we make it tangible? Prototypes
Test Learn What works and what doesn't? Validated learning

Phase 1: Empathize

Build deep understanding of users and their experiences.

Empathy Methods

Method Duration Participants Best For
User Interviews 30-60 min 1:1 Deep individual insight
Observation Hours-days Field work Natural behavior
Empathy Mapping 15-30 min Workshop Synthesizing research
Journey Mapping 1-2 hours Workshop Experience visualization
Shadowing Half-day Field work Workflow understanding

Empathy Map Template

## Empathy Map: [User/Persona Name]

### Says
[Direct quotes from interviews/observation]
- "[Quote 1]"
- "[Quote 2]"

### Thinks
[What might they be thinking? Hopes/fears?]
- [Thought 1]
- [Thought 2]

### Does
[Actions and behaviors observed]
- [Behavior 1]
- [Behavior 2]

### Feels
[Emotional state, what worries/excites them]
- [Emotion 1]
- [Emotion 2]

### Pains
[Frustrations, obstacles, risks]
- [Pain 1]
- [Pain 2]

### Gains
[Wants, needs, measures of success]
- [Gain 1]
- [Gain 2]

Interview Guide Structure

## User Interview Guide

**Duration:** 45-60 minutes
**Objective:** [What we want to learn]

### Opening (5 min)
- Introduce yourself and purpose
- Explain confidentiality, recording consent
- "There are no right or wrong answers"

### Context (10 min)
- Tell me about your role/day-to-day
- How long have you been doing [X]?
- Walk me through a typical [scenario]

### Deep Dive (25 min)
- Tell me about a time when [specific experience]
- What was the most challenging part?
- What did you try? What happened?
- How did that make you feel?

### Needs & Desires (10 min)
- If you could wave a magic wand, what would change?
- What would that enable you to do?
- What does success look like for you?

### Closing (5 min)
- Is there anything else you'd like to share?
- Can we follow up if we have questions?

Phase 2: Define

Synthesize observations and frame the right problem.

Point of View (POV) Statement

## POV Statement

**User:** [Specific user type/persona]

**Need:** [Verb - what they need to do]

**Insight:** [Because - surprising insight about why]

---

**Full Statement:**
[User] needs to [need] because [insight].

**Example:**
A busy working parent needs to quickly prepare healthy meals
because they want to model good eating habits for their children
but feel guilty about the time-cost tradeoff.

How Might We (HMW) Questions

Transform POV into actionable opportunity statements:

## How Might We Questions

**POV:** [Your POV statement]

### HMW Brainstorm

Generate HMW questions by asking:

| Lens | Question | HMW |
|------|----------|-----|
| **Amplify the good** | What's working? | HMW do more of [good thing]? |
| **Remove the bad** | What's painful? | HMW eliminate [pain point]? |
| **Explore the opposite** | What if we flipped it? | HMW [opposite approach]? |
| **Question assumptions** | What's assumed? | HMW if [assumption] wasn't true? |
| **Change status quo** | What's expected? | HMW change when/where/who? |
| **Break it into parts** | What are components? | HMW address just [component]? |

### Selected HMW Questions
1. HMW [question 1]?
2. HMW [question 2]?
3. HMW [question 3]?

**Priority HMW:** [The one to ideate on]

Phase 3: Ideate

Generate a wide range of creative solutions.

Ideation Rules

Rule Description
Defer judgment No criticism during brainstorming
Go for quantity More ideas = better ideas
Build on others' ideas "Yes, and..."
Encourage wild ideas Think big, no constraints
Be visual Sketch, don't just talk
One conversation Listen, build, riff
Stay focused Keep the HMW visible

Brainstorming Session Template

## Ideation Session

**HMW:** [The How Might We question]
**Duration:** 30-45 minutes
**Participants:** [Names]

### Warm-Up (5 min)
[Quick creative exercise to loosen up]

### Silent Brainstorm (10 min)
- Write one idea per sticky note
- Work individually
- Aim for 10+ ideas each

### Share & Build (15 min)
- Share ideas one by one
- Build on others' ideas
- No criticism, only "Yes, and..."

### Cluster & Theme (10 min)
- Group similar ideas
- Name each cluster
- Identify promising directions

### Ideas Generated
| Cluster | Ideas | Count |
|---------|-------|-------|
| [Theme 1] | [List] | [N] |
| [Theme 2] | [List] | [N] |

### Top Ideas to Prototype
1. [Idea 1]
how to use design-thinking

How to use design-thinking on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add design-thinking
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/melodic-software/claude-code-plugins --skill design-thinking

The skills CLI fetches design-thinking from GitHub repository melodic-software/claude-code-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/design-thinking

Reload or restart Cursor to activate design-thinking. Access the skill through slash commands (e.g., /design-thinking) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.730 reviews
  • Kwame Farah· Dec 16, 2024

    design-thinking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 15, 2024

    design-thinking reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Oct 6, 2024

    design-thinking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Sep 21, 2024

    design-thinking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mia Garcia· Sep 13, 2024

    design-thinking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zara Bhatia· Sep 9, 2024

    Keeps context tight: design-thinking is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Diego Agarwal· Sep 1, 2024

    We added design-thinking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Liam Johnson· Aug 28, 2024

    We added design-thinking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Valentina Ndlovu· Aug 20, 2024

    Keeps context tight: design-thinking is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Pratham Ware· Aug 12, 2024

    design-thinking has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 30

1 / 3