MCP HubMCP Hub
← 返回技能列表

When Stuck - Problem-Solving Dispatch

Elios-FPT
更新于 Today
19 次查看
1
在 GitHub 上查看
其他general

关于

This skill helps developers identify the right problem-solving technique when they're stuck by matching their specific stuck-symptom to the appropriate method. It provides a quick dispatch system for common scenarios like overwhelming complexity, lack of innovation, or recurring patterns. Use it to efficiently navigate from a blocked state to a targeted solution strategy.

技能文档

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 StuckUse This Skill
Complexity spiraling - Same thing 5+ ways, growing special casesskills/problem-solving/simplification-cascades
Need innovation - Conventional solutions inadequate, can't find fitting approachskills/problem-solving/collision-zone-thinking
Recurring patterns - Same issue different places, reinventing wheelsskills/problem-solving/meta-pattern-recognition
Forced by assumptions - "Must be done this way", can't question premiseskills/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 outputskills/debugging/systematic-debugging
Multiple independent problems - Can parallelize investigationskills/collaboration/dispatching-parallel-agents
Root cause unknown - Symptom clear, cause hiddenskills/debugging/root-cause-tracing

Process

  1. Identify stuck-type - What symptom matches above?
  2. Load that skill - Read the specific technique
  3. Apply technique - Follow its process
  4. 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

快速安装

/plugin add https://github.com/Elios-FPT/EliosCodePracticeService/tree/main/when-stuck

在 Claude Code 中复制并粘贴此命令以安装该技能

GitHub 仓库

Elios-FPT/EliosCodePracticeService
路径: .claude/skills/problem-solving/when-stuck

相关推荐技能

analyzing-dependencies

元

这个Claude Skill能自动分析项目依赖的安全漏洞、过时包和许可证合规问题。它支持npm、pip、composer、gem和go modules等多种包管理器，帮助开发者识别潜在风险。当您需要检查依赖安全性、更新过时包或确保许可证兼容时，可使用"check dependencies"等触发短语来调用。

查看技能

work-execution-principles

其他

这个Claude Skill为开发者提供了一套通用的工作执行原则，涵盖任务分解、范围确定、测试策略和依赖管理。它确保开发活动中的一致质量标准，适用于代码审查、工作规划和架构决策等场景。该技能与所有编程语言和框架兼容，帮助开发者系统化地组织代码结构和定义工作边界。

查看技能

Git Commit Helper

元

Git Commit Helper能通过分析git diff自动生成规范的提交信息，适用于开发者编写提交消息或审查暂存区变更时。它能识别代码变更类型并自动匹配Conventional Commits规范，提供包含功能类型、作用域和描述的标准化消息。开发者只需提供git diff内容即可获得即用型的提交消息建议。

查看技能

nextjs

开发

This Next.js Skill provides architectural standards and BFF patterns for Next.js 15.5+ projects using App Router. It enforces clear server/client component separation, implements Server Actions and Route Handlers, and ensures performance optimization with SEO best practices. Use it when designing App Router structures, implementing data fetching strategies, or building BFF architectures.

查看技能