When Stuck - Problem-Solving Dispatch
关于
This skill helps developers select the right problem-solving technique when they feel stuck, based on their specific symptom like complexity or lack of innovation. It acts as a dispatch router to other specialized skills, matching the type of "stuck-ness" to the appropriate solution method. Use it when you're uncertain which analytical approach to apply to your coding or design problem.
快速安装
Claude Code
推荐npx skills add obra/superpowers-skills -a claude-code/plugin add https://github.com/obra/superpowers-skillsgit clone https://github.com/obra/superpowers-skills.git ~/.claude/skills/When Stuck - Problem-Solving Dispatch在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
When Stuck - Problem-Solving Dispatch
Overview
Different stuck-types need different techniques. This skill helps you quickly identify which problem-solving skill to use.
Core principle: Match stuck-symptom to technique.
Quick Dispatch
digraph stuck_dispatch {
rankdir=TB;
node [shape=box, style=rounded];
stuck [label="You're Stuck", shape=ellipse, style=filled, fillcolor=lightblue];
complexity [label="Same thing implemented 5+ ways?\nGrowing special cases?\nExcessive if/else?"];
innovation [label="Can't find fitting approach?\nConventional solutions inadequate?\nNeed breakthrough?"];
patterns [label="Same issue in different places?\nFeels familiar across domains?\nReinventing wheels?"];
assumptions [label="Solution feels forced?\n'This must be done this way'?\nStuck on assumptions?"];
scale [label="Will this work at production?\nEdge cases unclear?\nUnsure of limits?"];
bugs [label="Code behaving wrong?\nTest failing?\nUnexpected output?"];
stuck -> complexity;
stuck -> innovation;
stuck -> patterns;
stuck -> assumptions;
stuck -> scale;
stuck -> bugs;
complexity -> simp [label="yes"];
innovation -> collision [label="yes"];
patterns -> meta [label="yes"];
assumptions -> invert [label="yes"];
scale -> scale_skill [label="yes"];
bugs -> debug [label="yes"];
simp [label="skills/problem-solving/\nsimplification-cascades", shape=box, style="rounded,filled", fillcolor=lightgreen];
collision [label="skills/problem-solving/\ncollision-zone-thinking", shape=box, style="rounded,filled", fillcolor=lightgreen];
meta [label="skills/problem-solving/\nmeta-pattern-recognition", shape=box, style="rounded,filled", fillcolor=lightgreen];
invert [label="skills/problem-solving/\ninversion-exercise", shape=box, style="rounded,filled", fillcolor=lightgreen];
scale_skill [label="skills/problem-solving/\nscale-game", shape=box, style="rounded,filled", fillcolor=lightgreen];
debug [label="skills/debugging/\nsystematic-debugging", shape=box, style="rounded,filled", fillcolor=lightyellow];
}
Stuck-Type → Technique
| How You're Stuck | Use This Skill |
|---|---|
| Complexity spiraling - Same thing 5+ ways, growing special cases | skills/problem-solving/simplification-cascades |
| Need innovation - Conventional solutions inadequate, can't find fitting approach | skills/problem-solving/collision-zone-thinking |
| Recurring patterns - Same issue different places, reinventing wheels | skills/problem-solving/meta-pattern-recognition |
| Forced by assumptions - "Must be done this way", can't question premise | skills/problem-solving/inversion-exercise |
| Scale uncertainty - Will it work in production? Edge cases unclear? | skills/problem-solving/scale-game |
| Code broken - Wrong behavior, test failing, unexpected output | skills/debugging/systematic-debugging |
| Multiple independent problems - Can parallelize investigation | skills/collaboration/dispatching-parallel-agents |
| Root cause unknown - Symptom clear, cause hidden | skills/debugging/root-cause-tracing |
Process
- Identify stuck-type - What symptom matches above?
- Load that skill - Read the specific technique
- Apply technique - Follow its process
- If still stuck - Try different technique or combine
Combining Techniques
Some problems need multiple techniques:
- Simplification + Meta-pattern: Find pattern, then simplify all instances
- Collision + Inversion: Force metaphor, then invert its assumptions
- Scale + Simplification: Extremes reveal what to eliminate
Remember
- Match symptom to technique
- One technique at a time
- Combine if first doesn't work
- Document what you tried
GitHub 仓库
常见问题
什么是 When Stuck - Problem-Solving Dispatch Skill?
When Stuck - Problem-Solving Dispatch 是一个 Claude Skill,作者为 obra。Skill 将 Claude 按需加载的说明和资源打包,让 Claude 无需额外提示即可执行与 When Stuck - Problem-Solving Dispatch 相关的任务。
如何安装 When Stuck - Problem-Solving Dispatch?
使用本页的安装命令:将 When Stuck - Problem-Solving Dispatch 作为插件添加到 Claude Code,或将其仓库克隆到 skills 目录,然后重启 Claude 以加载该 Skill。
When Stuck - Problem-Solving Dispatch 属于哪个分类?
When Stuck - Problem-Solving Dispatch 属于其他分类。
When Stuck - Problem-Solving Dispatch 可以免费使用吗?
可以。When Stuck - Problem-Solving Dispatch 已收录在 AIMCP,可免费安装。
相关推荐技能
该Skill为开发者提供体育博彩数据分析工具,可分析盘口、大小球和特殊投注,识别价值投注机会。它整合历史数据和情景统计,生成包含时间戳的结构化Markdown报告。适用于需要快速获取博彩市场洞察的娱乐或教育类应用开发。
LlamaGuard是Meta推出的7-8B参数内容审核模型,专门用于过滤LLM的输入和输出内容。它能检测六大安全风险类别(暴力/仇恨、性内容、武器、违禁品、自残、犯罪计划),准确率达94-95%。开发者可通过HuggingFace、vLLM或Sagemaker快速部署,并能与NeMo Guardrails集成实现自动化安全防护。
这个Claude Skill帮助开发者优化云成本,通过资源调整、标记策略和预留实例来降低AWS、Azure和GCP的开支。它适用于减少云支出、分析基础设施成本或实施成本治理策略的场景。关键功能包括提供成本可视化、资源规模调整指导和定价模型优化建议。
这个Skill使用bitsandbytes库量化大语言模型,能在GPU内存有限时通过8位或4位量化减少50-75%内存占用,同时保持精度损失最小。它支持INT8、NF4、FP4等多种量化格式,可与HuggingFace Transformers无缝集成,适用于需要部署更大模型或加速推理的场景。还提供QLoRA训练和8位优化器支持,让开发者能轻松实现高效模型压缩。
