ck:problem-solving
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
Best use case
ck:problem-solving is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
Teams using ck:problem-solving should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/problem-solving/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:problem-solving Compares
| Feature / Agent | ck:problem-solving | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Problem-Solving Techniques Systematic approaches for different types of stuck-ness. Each technique targets specific problem patterns. ## When to Use Apply when encountering: - **Complexity spiraling** - Multiple implementations, growing special cases, excessive branching - **Innovation blocks** - Conventional solutions inadequate, need breakthrough thinking - **Recurring patterns** - Same issue across domains, reinventing solutions - **Assumption constraints** - Forced into "only way", can't question premise - **Scale uncertainty** - Production readiness unclear, edge cases unknown - **General stuck-ness** - Unsure which technique applies ## Quick Dispatch **Match symptom to technique:** | Stuck Symptom | Technique | Reference | |---------------|-----------|-----------| | Same thing implemented 5+ ways, growing special cases | **Simplification Cascades** | `references/simplification-cascades.md` | | Conventional solutions inadequate, need breakthrough | **Collision-Zone Thinking** | `references/collision-zone-thinking.md` | | Same issue in different places, reinventing wheels | **Meta-Pattern Recognition** | `references/meta-pattern-recognition.md` | | Solution feels forced, "must be done this way" | **Inversion Exercise** | `references/inversion-exercise.md` | | Will this work at production? Edge cases unclear? | **Scale Game** | `references/scale-game.md` | | Unsure which technique to use | **When Stuck** | `references/when-stuck.md` | ## Core Techniques ### 1. Simplification Cascades Find one insight eliminating multiple components. "If this is true, we don't need X, Y, Z." **Key insight:** Everything is a special case of one general pattern. **Red flag:** "Just need to add one more case..." (repeating forever) ### 2. Collision-Zone Thinking Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?" **Key insight:** Revolutionary ideas from deliberate metaphor-mixing. **Red flag:** "I've tried everything in this domain" ### 3. Meta-Pattern Recognition Spot patterns appearing in 3+ domains to find universal principles. **Key insight:** Patterns in how patterns emerge reveal reusable abstractions. **Red flag:** "This problem is unique" (probably not) ### 4. Inversion Exercise Flip core assumptions to reveal hidden constraints. "What if the opposite were true?" **Key insight:** Valid inversions reveal context-dependence of "rules." **Red flag:** "There's only one way to do this" ### 5. Scale Game Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths. **Key insight:** What works at one scale fails at another. **Red flag:** "Should scale fine" (without testing) ## Application Process 1. **Identify stuck-type** - Match symptom to technique above 2. **Load detailed reference** - Read specific technique from `references/` 3. **Apply systematically** - Follow technique's process 4. **Document insights** - Record what worked/failed 5. **Combine if needed** - Some problems need multiple techniques ## Combining Techniques Powerful combinations: - **Simplification + Meta-pattern** - Find pattern, then simplify all instances - **Collision + Inversion** - Force metaphor, then invert its assumptions - **Scale + Simplification** - Extremes reveal what to eliminate - **Meta-pattern + Scale** - Universal patterns tested at extremes ## References Load detailed guides as needed: - `references/when-stuck.md` - Dispatch flowchart and decision tree - `references/simplification-cascades.md` - Cascade detection and extraction - `references/collision-zone-thinking.md` - Metaphor collision process - `references/meta-pattern-recognition.md` - Pattern abstraction techniques - `references/inversion-exercise.md` - Assumption flipping methodology - `references/scale-game.md` - Extreme testing procedures - `references/attribution.md` - Source and adaptation notes
Related Skills
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.