meta-pattern-recognition
Spot patterns appearing in 3+ domains to find universal principles. Use when noticing the same pattern across 3+ different domains or experiencing déjà vu in problem-solving.
When & Why to Use This Skill
The Meta-Pattern Recognition skill is designed to identify universal principles by detecting recurring patterns across three or more distinct domains. By extracting the abstract form of a solution—such as caching, queuing, or resource pooling—it enables users to apply battle-tested strategies to new, complex problems, ensuring architectural consistency and preventing the redundant 'reinvention of the wheel' across different technical or organizational silos.
Use Cases
- System Architecture: Identifying that a specific performance bottleneck follows a universal pattern (e.g., resource exhaustion) and applying proven solutions like rate limiting or circuit breakers.
- Cross-Domain Innovation: Taking a successful abstract principle from one field (e.g., biological feedback loops) and applying its logic to stabilize software deployment pipelines.
- Organizational Efficiency: Recognizing when multiple independent teams are solving the same underlying problem and consolidating their efforts into a single, universal framework.
- Strategic Problem Solving: Using the '3+ domains' rule to validate whether a challenge requires a custom solution or if it can be addressed using a fundamental, battle-tested principle.
| name | meta-pattern-recognition |
|---|---|
| description | Spot patterns appearing in 3+ domains to find universal principles. Use when noticing the same pattern across 3+ different domains or experiencing déjà vu in problem-solving. |
| tier | e |
| morpheme | e |
| dewey_id | e.3.1.3 |
Meta-Pattern Recognition
Part of the GONAD: Gremlin Obnoxious Network of Actual Discovery
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