meta-pattern-recognition
Spot patterns appearing in 3+ domains to find universal principles
When & Why to Use This Skill
Meta-Pattern Recognition is an advanced analytical skill designed to identify universal principles by spotting recurring patterns across three or more distinct domains. By extracting abstract frameworks from specific technical solutions—such as caching, layering, or queuing—it enables users to apply battle-tested architectural patterns to new challenges, significantly improving problem-solving efficiency and preventing the redundant 'reinvention of the wheel' in complex system design.
Use Cases
- System Architecture: Identify and apply proven resource management patterns, such as pooling or multi-level abstraction, to new software infrastructures based on cross-domain success.
- Cross-Domain Innovation: Adapt established concepts from one field to another, such as applying API rate-limiting logic to manage LLM token budgets and prevent context exhaustion.
- Strategic Problem Solving: Recognize structural similarities between current technical bottlenecks and historical solutions to implement faster, more reliable architectural fixes.
- Knowledge Synthesis: Extract abstract principles from diverse technical experiences to build a robust internal knowledge base of universal design patterns for engineering teams.
| 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 |
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