problem-solving
5 techniques for different problem types. Use when stuck or facing complex challenges.
Best use case
problem-solving is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
5 techniques for different problem types. Use when stuck or facing complex challenges.
Teams using 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 problem-solving Compares
| Feature / Agent | 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?
5 techniques for different problem types. Use when stuck or facing complex challenges.
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
> **AI-consumed reference.** Optimized for Claude to read during execution.
> Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md)
> or [docs/getting-started/](../../../docs/getting-started/) depending on topic.
# Problem Solving Techniques
Use when stuck, need breakthrough, or evaluating approaches.
## Decision Matrix
```toon
techniques[5]{symptom,technique,approach}:
"Tried everything / spiraling",Simplification Cascades,"Strip to minimal → rebuild one piece at a time → find breaking layer"
"Need creative idea",Collision-Zone Thinking,"Combine principles from unrelated domains into novel solution"
"Same issue keeps recurring",Meta-Pattern Recognition,"List all similar issues → find shared root → fix the pattern"
"Stuck in only-one-way thinking",Inversion Exercise,"State assumption → ask 'what if opposite?' → explore inverted approach"
"Will it scale?",Scale Game,"Test at 10x/100x/1000x → find breaking point → design for 10x actual need"
```
## Simplification Cascades (Most Used)
1. Remove ALL features except core
2. Make it work with hardcoded values
3. Add ONE thing back
4. Repeat until issue appears
5. Fix at that layer
## Inversion Exercise
1. State current assumption: "We must do X"
2. Ask: "What if we never do X?" or "What if we do the opposite?"
3. Explore — often reveals a better design
## Scale Game
Test at 10x, 100x, 1000x current load. Find breaking point. Design for 10x actual need (not 1000x).
## Quick Reference
Stuck → Simplify first. Creative block → Collision zones. Recurring → Meta-patterns. Tunnel vision → Invert. Scaling → Scale game.Related Skills
vue-expert
Vue 3 gotchas and decision criteria. Covers reactivity traps, Composition API pitfalls, and Pinia patterns.
typescript-expert
TypeScript gotchas and decision criteria covering nullish coalescing pitfalls (|| vs ??), strict tsconfig settings (noUncheckedIndexedAccess, exactOptionalPropertyTypes), type guard patterns, discriminated unions, and as const vs enum. Use when writing TypeScript, configuring tsconfig, implementing type guards, or debugging null/undefined errors.
tree-of-thoughts
Branch, evaluate, prune, expand — structured search over solution space. Use for architecture with multi-step decisions, refactor planning, or complex debug hypothesis trees. Paper: Yao et al. 2023.
test-writer
Write tests with TDD following structured patterns. Ensures consistent AAA structure, proper coverage targets, and framework-specific conventions. Without this skill, tests lack consistent naming, miss coverage targets, and skip anti-pattern checks.
stitch-design
Generate UI designs using Google Stitch AI with optimized prompts
session-continuation
Manage workflow state across sessions with handoff and resume. TOON-based state persistence.
sequential-thinking
Structured thinking process for complex analysis. Supports revision, branching, and dynamic adjustment.
self-improve
Apply learned improvements to the Aura Frog plugin. Updates rules, adjusts agent routing, modifies workflow configurations, and generates knowledge base entries.
self-healing-orchestrator
Proposes patches for F2 (local-logic) and F3 (local-design) failures. NEVER applies without user approval. Confidence ≥0.7 to propose; below that, escalates raw findings. Counts toward replan_budget. Per-task: max 1; per-session: max 5.
self-consistency
Generate N independent reasoning paths and vote on the answer. Use for architectural trade-offs, ambiguous design decisions, or when single-path reasoning risks locking onto the first plausible answer. Paper: Wang et al. 2022.
scalable-thinking
Design for scale while keeping implementation simple (KISS).
run-orchestrator
Execute 5-phase TDD workflow for complex features. Use when the user invokes /run, asks to build/create/implement a feature, requests a complex multi-file change, or types 'fasttrack:'. Enforces phase gates, sprint contracts, and builder!=reviewer discipline.