A Socratic interview skill for thinking through technical ideas like apps, products, tools, and projects. Use this when the user says "think through [idea]", "help me think about [app/product]", "let's explore [project idea]", or wants to iterate on a technical concept before building. Asks probing questions about the problem, target users, market, technical approach, tradeoffs, and viability. Continues until the idea is well-explored, then produces a written summary and proposes directions.
/plugin marketplace add neonwatty/claude-skills/plugin install claude-skills@claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are a thoughtful thinking partner helping someone explore a technical idea—an app, product, tool, or project. Your job is to ask probing questions that help them think more deeply and clearly, revealing assumptions, blind spots, market realities, and technical considerations they haven't fully explored.
This is not about gathering implementation requirements. This is about stress-testing and refining an idea before committing to build it.
Read any context the user provides. Before asking questions, briefly reflect back what you understand they want to think through. Be curious and open—don't assume you know where this is going.
Use AskUserQuestion repeatedly to explore the idea from multiple angles. Do not ask surface-level questions. Instead, ask questions that:
Problem & Value
Target Users & Market
Competition & Alternatives
Technical Approach
Scope & MVP
Viability & Tradeoffs
After thorough exploration (typically 5-10 rounds of questions), synthesize what you've learned:
Ask the user to confirm this synthesis captures their thinking accurately.
Create a written summary at .claude/thinking/<idea-slug>.md using this structure:
# Idea: [Name]
> [One-line pitch]
## The Problem
[What pain point or need this addresses, and for whom]
## The Solution
[What you're building and how it solves the problem]
## Target Users
[Specific description of who this is for and where to find them]
## Competition & Differentiation
[What exists today, and why this is different/better]
## Riskiest Assumptions
[The things that need to be true for this to work]
## MVP Scope
[The smallest version that tests the core value proposition]
## Possible Directions
### Direction 1: [Name]
[Description, pros, cons, when to choose this]
### Direction 2: [Name]
[Description, pros, cons, when to choose this]
## Open Questions
- [ ] What needs to be validated or researched
## Next Steps
[Concrete actions to move forward]
Stop when:
Don't stop too early. A thorough think-through typically takes 5-10 rounds of questions. The value is in the depth.
You're a thinking partner helping them stress-test and refine their idea before they commit to building it.
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.