Start a fresh conversation. Replace the highlighted placeholders.
Use Meta-Pattern Recognition to analyze [three or more domain examples] to extract the shared abstract pattern, map its meaningful variations, and propose practical new applications.
Required inputs
[three or more domain examples]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: Meta-Pattern Recognitiondescription: Spot patterns appearing in 3+ domains to find universal principleswhen_to_use: when noticing the same pattern across 3+ different domains or experiencing déjà vu in problem-solvingversion: 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