vc:problem-solving
Skill0 starsChanged 3 months agoMITView on GitHub
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 68
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths.
- Very specific: line 77
Load detailed reference: - Read specific technique from references/
- Distinctive: line 78
Apply systematically: - Follow technique's process
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Identify stuck-type - Match symptom to technique above
- Load detailed reference - Read specific technique from
references/ - Apply systematically - Follow technique's process
- Document insights - Record what worked/failed
- 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 treereferences/simplification-cascades.md- Cascade detection and extractionreferences/collision-zone-thinking.md- Metaphor collision processreferences/meta-pattern-recognition.md- Pattern abstraction techniquesreferences/inversion-exercise.md- Assumption flipping methodologyreferences/scale-game.md- Extreme testing proceduresreferences/attribution.md- Source and adaptation notes
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- opencue/cuecards★ 699% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- vc:kitSkill
- vc:auditSkill
- vc:autoresearchSkill
- vc:chrome-devtoolsSkill
- vc:context-engineeringSkill
- vc:debugSkill
- vc:docs-seekerSkill
- vc:generate-contextSkill
- vc:generate-planSkill
- vc:mcp-managementSkill
- vc:merge-worktreeSkill
- vc:previewSkill
- vc:publishSkill
- vc:repomixSkill
- vc:scoutSkill
- vc:securitySkill
- vc:sequential-thinkingSkill
- vc:setupSkill
- vc:stress-testSkill
- vc:tech-graphSkill
- vc:updateSkill
- vc:watzupSkill
- vc:web-testingSkill
- vc:xiaSkill
- vc:kitSkill
- vc:auditSkill
- vc:autoresearchSkill
- vc:chrome-devtoolsSkill
- vc:context-engineeringSkill
- vc:debugSkill
- vc:docs-seekerSkill
- vc:generate-contextSkill
- vc:generate-planSkill
- vc:mcp-managementSkill
- vc:merge-worktreeSkill
- vc:previewSkill
- vc:problem-solvingSkill
- vc:publishSkill
- vc:repomixSkill
- vc:scoutSkill
- vc:securitySkill
- vc:sequential-thinkingSkill
- vc:setupSkill
- vc:stress-testSkill
- vc:tech-graphSkill
- vc:updateSkill
- vc:watzupSkill
- vc:web-testingSkill
- vc:xiaSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

