Agent skill
Meta-Pattern Recognition
Spot patterns appearing in 3+ domains to find universal principles
Install this agent skill to your Project
npx add-skill https://github.com/obra/superpowers-skills/tree/main/skills/problem-solving/meta-pattern-recognition
SKILL.md
Meta-Pattern Recognition
Overview
When the same pattern appears in 3+ domains, it's probably a universal principle worth extracting.
Core principle: Find patterns in how patterns emerge.
Quick Reference
| 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 |
Process
- Spot repetition - See same shape in 3+ places
- Extract abstract form - Describe independent of any domain
- Identify variations - How does it adapt per domain?
- Check applicability - Where else might this help?
Example
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)
Red Flags You're Missing Meta-Patterns
- "This problem is unique" (probably not)
- Multiple teams independently solving "different" problems identically
- Reinventing wheels across domains
- "Haven't we done something like this?" (yes, find it)
Remember
- 3+ domains = likely universal
- Abstract form reveals new applications
- Variations show adaptation points
- Universal patterns are battle-tested
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
Systematic Debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Defense-in-Depth Validation
Validate at every layer data passes through to make bugs impossible
Verification Before Completion
Run verification commands and confirm output before claiming success
Root Cause Tracing
Systematically trace bugs backward through call stack to find original trigger
Brainstorming Ideas Into Designs
Interactive idea refinement using Socratic method to develop fully-formed designs
Requesting Code Review
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Didn't find tool you were looking for?