Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Collaboratively refines rough ideas into fully-formed designs through targeted questioning and incremental validation. Use before writing code or implementation plans when creating or developing new features.
/plugin marketplace add mthalman/superpowers/plugin install superpowers@claude-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
Understanding the idea:
Prioritize questions by impact:
When you identify competing stakeholder priorities:
Exploring approaches:
⚠️ COGNITIVE CHECKPOINT: Before presenting approaches
For each approach you're considering, you must be able to articulate in one sentence:
If you cannot clearly articulate why an approach fits → Don't present it If you can clearly articulate → Document the reasoning and present
Articulating trade-offs at appropriate depth:
Match trade-off complexity to problem complexity.
For simple, low-risk problems:
For complex, high-stakes problems:
Trade-off: [Principle A] vs [Principle B]
The tension: [Explain why you can't have both]
Option 1 favors [A]:
- Benefit: [specific outcome]
- Cost: [what you give up]
- Choose when: [context factors]
Option 2 favors [B]:
- Benefit: [specific outcome]
- Cost: [what you give up]
- Choose when: [context factors]
Recommendation for this context: [Choice] because [context factor weighs more heavily]
Presenting the design:
Documentation:
docs/plans/YYYY-MM-DD-<topic>-design.mdImplementation (if continuing):
The brainstorming process should scale to match your project context. Not every scenario needs the same depth of exploration.
Well-Defined Feature (clear requirements, known constraints):
Vague Problem (unclear scope, multiple interpretations):
Solo Exploration / Learning Exercise:
Rapid Prototyping (<1 week, may discard):
Sprint Development (1-4 weeks, production-bound):
Enterprise/Long-term Project (>1 month, high stakes):
Indicators of "Keep It Simple":
Indicators of "Standard Depth":
Indicators of "Go Deep":
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies 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.
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 original visual designs, never copying existing artists' work to avoid copyright violations.