ysskrishna/ai-agent-skills / skills/design-thinking
design-thinking
VerifiedUse for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| references/example.md | markdown | 1.9 KB |
references/example.md
View on GitHub# Example: Design Thinking (light path)
Illustrative case. All details are invented.
**User:** "We want to add a 'team dashboard' to our expense app because managers asked for it. Help me think it through before we build."
**Design challenge:** team managers who approve expenses; unclear what they need from a dashboard.
**Pass:** Empathize, Define, Ideate, Prototype, Test plan.
**Empathize**
- Who: team managers who approve expenses (stated by the user). Their other duties and tools are `[INFERRED]`.
- Pain (stated): they "asked for a dashboard". The underlying job is `[INFERRED]`: know quickly which claims need attention.
- Context: no interview notes were supplied, so nothing more is claimed.
**Define**
- Insight: managers ask for a dashboard, but the likely need is "tell me what needs my approval and what looks wrong".
- POV: **Team managers** need **to see only the claims that need action** because **reviewing every claim wastes their limited time**.
- HMW: How might we surface unusual claims without a full report? How might we let managers approve in bulk with confidence?
**Ideate** (hypotheses)
- Weekly digest of claims that need action (`desirable`, `feasible`).
- Dashboard with spend by category (`feasible`, desirability unproven).
- Flag claims above a manager-set threshold (`desirable`, `feasible`, `viable`).
**Prototype**
- Email mockup of the weekly digest. **Purpose:** do managers act on a digest without opening the app? **Fidelity:** static sketch.
- Paper layout of the dashboard. **Purpose:** which numbers do managers point at first? **Fidelity:** sketch only.
**Test plan**
- Learning goal: the digest is the wrong direction if managers still ask for a dashboard after seeing it.
- Participants: 5 managers to be decided with the user.
- Signals: do they act on a claim from the digest within the session; which number they point to on the paper layout.
- Next iteration: if managers split, test a digest with a link to a small spend view.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |