Dispatch to the right problem-solving technique based on how you're stuck
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
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.
| How You're Stuck | Use This Skill |
|---|---|
| Complexity spiraling — Same thing 5+ ways, growing special cases | simplification-cascades/SKILL.md |
| Need innovation — Conventional solutions inadequate, can't find fitting approach | collision-zone-thinking/SKILL.md |
| Recurring patterns — Same issue different places, reinventing wheels | meta-pattern-recognition/SKILL.md |
| Forced by assumptions — "Must be done this way", can't question premise | inversion-exercise/SKILL.md |
| Scale uncertainty — Will it work in production? Edge cases unclear? | scale-game/SKILL.md |
| Multiple independent problems — Can parallelize investigation | Use Agent tool with parallel subagents |
Some problems need multiple techniques:
Same thing implemented 5+ ways? → simplification-cascades
Can't find fitting approach? → collision-zone-thinking
Same issue in 3+ different places? → meta-pattern-recognition
"This must be done this way"? → inversion-exercise
Will this survive production scale? → scale-game
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
中文简介正在准备中。当前显示原文说明。
Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
中文简介正在准备中。当前显示原文说明。
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
中文简介正在准备中。当前显示原文说明。
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
中文简介正在准备中。当前显示原文说明。
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
中文简介正在准备中。当前显示原文说明。
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
中文简介正在准备中。当前显示原文说明。