Meta-Pattern Recognition
This skill helps users extract universally applicable core principles by identifying recurring patterns across at least three different domains. It enables developers, architects, or any problem-solver to abstract seemingly independent challenges, thereby discovering and applying proven solutions, avoiding redundant work. This Skill significantly enhances the elegance of system design, the efficiency of problem-solving, and innovation, fostering cross-domain knowledge reuse and the promotion of best practices.
git clone https://github.com/obra/superpowers-skills.gitBefore / After Comparison
1 组Before this skill, users often treated new problems as unique challenges, spending significant time designing solutions from scratch. This led to duplicated efforts across different teams or projects, resulting in inefficiency and difficulty in promoting universal best practices.
This Skill empowers users to recognize recurring patterns across domains, abstracting them into universal principles. This allows for rapid application of mature solutions or the design of more elegant system architectures, significantly reducing the time to solve new problems and fostering knowledge reuse and innovation.
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
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill