meta-pattern-recognition
Spot patterns appearing in 3+ domains to find universal principles
When & Why to Use This Skill
The Meta-Pattern Recognition skill empowers users to identify and extract universal principles by analyzing recurring patterns across three or more distinct domains. By abstracting complex problems into their fundamental forms, it facilitates high-level system architecture design, helps avoid redundant engineering efforts, and allows for the application of battle-tested strategies to emerging technological challenges like LLM resource management.
Use Cases
- System Architecture Optimization: Identifying and applying universal principles like caching, pooling, and layering to create scalable and decoupled software infrastructures.
- Cross-Domain Innovation: Adapting established solutions from traditional networking (e.g., rate limiting) to solve modern AI constraints like token budget management.
- Reducing Organizational Redundancy: Recognizing when different teams are solving the same underlying problem to prevent 'reinventing the wheel' across a company.
- Strategic Problem Solving: Using abstract pattern extraction to identify variations and applicability of proven methods to entirely new technical domains.
| 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