Back to skills
SkillHub ClubShip Full StackFull Stack
meta-pattern-recognition
Imported from https://github.com/paopp2/dotfiles.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
0
Hot score
74
Updated
March 20, 2026
Overall rating
C2.5
Composite score
2.5
Best-practice grade
C61.2
Install command
npx @skill-hub/cli install paopp2-dotfiles-meta-pattern-recognition
Repository
paopp2/dotfiles
Skill path: .claude/skills/problem-solving/meta-pattern-recognition
Imported from https://github.com/paopp2/dotfiles.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: paopp2.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install meta-pattern-recognition into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/paopp2/dotfiles before adding meta-pattern-recognition to shared team environments
- Use meta-pattern-recognition for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- 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 1. **Spot repetition** - See same shape in 3+ places 2. **Extract abstract form** - Describe independent of any domain 3. **Identify variations** - How does it adapt per domain? 4. **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