meta-pattern-recognition
Extracts universal principles by identifying recurring patterns across three or more different domains.
Install
mkdir -p .claude/skills/meta-pattern-recognition && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/175" && unzip -o skill.zip -d .claude/skills/meta-pattern-recognition && rm skill.zipInstalls to .claude/skills/meta-pattern-recognition
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Spot patterns appearing in 3+ domains to find universal principlesKey capabilities
- →Spot repetition across 3+ domains
- →Extract domain-independent abstract forms
- →Identify variations per domain
- →Check applicability in new contexts
How it works
The process involves identifying a recurring shape across multiple domains, abstracting it into a domain-independent form, and analyzing variations to find new application areas.
Inputs & outputs
When to use meta-pattern-recognition
- →Solve architectural bottlenecks
- →Identify reusable abstractions
- →Optimize resource management
- →Simplify complex system designs
About this skill
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
When not to use it
- →When a problem is truly unique
- →When patterns are only observed in 1-2 domains
Limitations
- →Requires at least 3 domains to identify a universal principle
- →Risk of misidentifying patterns if variations are not properly analyzed
How it compares
Unlike manual problem-solving which often treats issues as unique, this approach systematically extracts universal principles to apply battle-tested solutions to new contexts.
Compared to similar skills
meta-pattern-recognition side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| meta-pattern-recognition (this skill) | 10 | 9mo | No flags | Intermediate |
| research-engineer | 2 | 6mo | No flags | Advanced |
| tech-decision | 1 | 7mo | No flags | Intermediate |
| tech-stack-evaluator | 0 | 3mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mrgoonie
View all by mrgoonie →You might also like
research-engineer
davila7
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tech-decision
team-attention
This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
tech-stack-evaluator
alirezarezvani
Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.
microsoft-learn-research
Insightpulseai
Meta-skill for querying Microsoft Learn MCP server to resolve Azure architecture questions and validate configurations against official documentation
gsd-research-phase
WilderHerrera13
Research how to implement a phase (standalone - usually use /gsd-plan-phase instead)
ito-research
withakay
Conduct structured research for feature development, technology evaluation, or problem investigation. Use when the user needs to explore options, analyze trade-offs, or investigate technical approaches.