Menu
Spot patterns appearing in 3+ domains to find universal principles
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | meta-pattern-recognition |
| description | Spot patterns appearing in 3+ domains to find universal principles |
| when_to_use | when noticing the same pattern across 3+ different domains or experiencing déjà vu in problem-solving |
| version | 1.1.0 |
When the same pattern appears in 3+ domains, it's probably a universal principle worth extracting.
Core principle: Find patterns in how patterns emerge.
| Pattern Appears In | Abstract Form | Where Else? |
|---|---|---|
| CPU/DB/HTTP/DNS caching | Store frequently-accessed data closer | LLM prompt caching, CDN |
| Layering (network/storage/compute) | Separate concerns into abstraction levels | Architecture, organization |
| Queuing (message/task/request) | Decouple producer from consumer with buffer | Event systems, async processing |
| Pooling (connection/thread/object) | Reuse expensive resources | Memory management, resource governance |
Pattern spotted: Rate limiting in API throttling, traffic shaping, circuit breakers, admission control
Abstract form: Bound resource consumption to prevent exhaustion
Variation points: What resource, what limit, what happens when exceeded
New application: LLM token budgets (same pattern - prevent context window exhaustion)
