think-through
Think-Through Skill
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.
Process
Phase 1: Initial Understanding
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.
Phase 2: Deep Exploration
Use AskUserQuestion repeatedly to explore the idea from multiple angles. Do not ask surface-level questions. Instead, ask questions that:
- Reveal hidden assumptions about the market or users
- Expose technical considerations they haven't thought through
- Uncover competition or alternatives they may have overlooked
More from neonwatty/claude-skills
mobile-ux-ci
Generates Playwright tests that detect iOS/mobile UX anti-patterns in CI. Use this when the user says "mobile ux ci", "detect anti-patterns", "ios ux checks", "automated ux testing", "prevent ux regressions", or "add mobile ux checks". Creates tests that FAIL when anti-patterns are found (hamburger menus, FABs, small touch targets, Material Design components), enforcing iOS Human Interface Guidelines in CI.
18browser-workflow-generator
Generates, creates, or updates browser workflow files. Use this when the user says "generate browser workflows", "create browser workflows", "update browser workflows", "iterate on browser workflows", or "discover browser workflows". Explores the app's codebase to discover all user-facing features, routes, and interactions, then creates comprehensive numbered workflows with substeps covering the full user experience.
18ios-workflow-executor
Executes web app workflows in Safari on the iOS Simulator from /workflows/ios-workflows.md. Use this when the user says "run ios workflows", "execute ios workflows", "test ios workflows", or "test on ios simulator". Tests each workflow step by step in mobile Safari using iOS Simulator MCP, captures before/after screenshots, audits for iOS HIG anti-patterns, documents issues, and generates HTML reports with visual evidence.
17pr-creator
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
15feature-interview
Deeply interviews the user about a feature idea before implementation. Use this when the user says "interview me about [feature]", "I want to create a new feature", "let's create a new feature", "new feature", "plan a feature", or describes a feature they want to build. Asks probing, non-obvious questions about technical implementation, UI/UX decisions, edge cases, concerns, tradeoffs, and constraints. Continues interviewing until the feature is fully understood, then writes a detailed implementation plan.
15browser-workflow-executor
Executes browser-based user workflows from /workflows/browser-workflows.md using Claude-in-Chrome MCP. Use this when the user says "run browser workflows", "execute browser workflows", "test browser workflows", or "audit browser flows". Tests each workflow step by step, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
15