A collection of techniques for breaking through stuck points and finding elegant solutions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproblem-solvingExecute the skills CLI command in your project's root directory to begin installation:
Fetches problem-solving from mrgoonie/claudekit-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate problem-solving. Access via /problem-solving in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
4
total installs
4
this week
2.0K
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
2.0K
stars
A collection of techniques for breaking through stuck points and finding elegant solutions.
Location: when-stuck/SKILL.md
Start here when stuck. Matches your stuck-type to the right technique. Quick dispatch table for routing to the appropriate sub-skill.
Location: collision-zone-thinking/SKILL.md
Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?" Revolutionary insights come from deliberate metaphor-mixing.
Location: inversion-exercise/SKILL.md
Flip every assumption and see what still works. "What if the opposite were true?" Exposes hidden constraints and alternative approaches.
Location: meta-pattern-recognition/SKILL.md
Spot patterns appearing in 3+ domains to find universal principles. Extract abstract forms that apply across domains.
Location: scale-game/SKILL.md
Test at extremes (1000x bigger/smaller) to expose fundamental truths. What breaks? What survives? Extremes reveal what normal scales hide.
Location: simplification-cascades/SKILL.md
Find one insight that eliminates multiple components. "If this is true, we don't need X, Y, or Z." Look for unifying principles.
| How You're Stuck | Use This |
|---|---|
| Don't know which technique | when-stuck |
| Need breakthrough innovation | collision-zone-thinking |
| Forced by assumptions | inversion-exercise |
| Same issue in different places | meta-pattern-recognition |
| Unsure about production scale | scale-game |
| Complexity spiraling | simplification-cascades |
Conventional solutions inadequate? → collision-zone-thinking
"This must be done this way"? → inversion-exercise
Same pattern 3+ places? → meta-pattern-recognition
Will it work at scale? → scale-game
Same thing implemented 5+ ways? → simplification-cascades
"One powerful abstraction > ten clever hacks"
These techniques help you find the elegant solution that makes complexity unnecessary, rather than managing complexity through brute force.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for problem-solving matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend problem-solving for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
problem-solving fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
problem-solving reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: problem-solving is focused, and the summary matches what you get after install.
I recommend problem-solving for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: problem-solving is focused, and the summary matches what you get after install.
problem-solving fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in problem-solving — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added problem-solving from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 75