القائمة
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when initializing or maintaining agent-friendly repo context, setting up AGENTS.md or CLAUDE.md, adding local rules, defining verification commands, or checking whether context files are stale.
Use when the user asks to run workflow:ship, ship a branch, publish a feature branch, open and merge a PR, or push/PR/merge/cleanup completed work.
Use when the user asks to run workflow:commit, create a commit, make a git commit, stage changes, write a commit message, or prepare local changes for shipping.
Turn any rough prompt, half-formed idea, or task description into a finished, ready-to-send prompt optimized for Opus 4.7 (with adaptive thinking) inside the chat app — claude.ai, the Mac app, the iOS app — NOT the API. Use this skill whenever the user wants to write, rewrite, optimize, improve, sharpen, or polish a prompt for the chat app. Trigger phrases include "rewrite this prompt", "make this a better prompt", "optimize this prompt", "turn this into a prompt", "help me prompt this", "draft a prompt that...", "I want to ask...", or whenever the user pastes a draft prompt and asks for improvements. Also trigger when the user describes a task they plan to send into the chat app and clearly wants a reusable, well-structured prompt rather than a direct answer. The output is always a single, copy-pasteable prompt in a code block that the user sends as-is — never a template with placeholders. Always ends with the exact line "Think before answering (maximum reasoning)".
Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
Pre-discovery intent exploration for genuinely vague ideas. Use when the user pitches an idea where the real user-need, problem framing, or core assumptions are unclear — before /kiro-discovery. Delegates to the intent-explorer skill, which produces .kiro/specs/<slug>/intent-spec.md. The output is auto-detected by /kiro-discovery and downstream spec skills, so the user does not need to pass intent context as an argument. Skip this skill entirely when the user already has a clear problem statement.
استنادا إلى تصنيف SOC المهني
| name | collision-zone-thinking |
| description | Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?" |
| when_to_use | when conventional approaches feel inadequate and you need breakthrough innovation by forcing unrelated concepts together |
| version | 1.1.0 |
Revolutionary insights come from forcing unrelated concepts to collide. Treat X like Y and see what emerges.
Core principle: Deliberate metaphor-mixing generates novel solutions.
| Stuck On | Try Treating As | Might Discover |
|---|---|---|
| Code organization | DNA/genetics | Mutation testing, evolutionary algorithms |
| Service architecture | Lego bricks | Composable microservices, plug-and-play |
| Data management | Water flow | Streaming, data lakes, flow-based systems |
| Request handling | Postal mail | Message queues, async processing |
| Error handling | Circuit breakers | Fault isolation, graceful degradation |
Problem: Complex distributed system with cascading failures
Collision: "What if we treated services like electrical circuits?"
Emergent properties:
Where it works: Preventing cascade failures Where it breaks: Circuits don't have retry logic Insight gained: Failure isolation patterns from electrical engineering
