Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.