Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-skills
Spots patterns repeating across 3+ domains (e.g., caching in CPU/DB/HTTP/LLM) to extract universal principles. Use when noticing cross-domain similarities or déjà vu in problem-solving.
npx claudepluginhub orban/claude-skills --plugin claude-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-skills:meta-pattern-recognitionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the same pattern appears in 3+ domains, it's probably a universal principle worth extracting.
Discovers recurring patterns across code analyses. Embedded in run-analysis skill; do not invoke separately—use run-analysis instead.
Detects reusable code patterns, workflow automations, best practices, and config setups during implementation for potential new skills.
Identifies structural patterns (repetition, hierarchy, contrast, etc.) in designs, arguments, and solutions. Useful when analyzing why something works or naming its underlying form.
Share bugs, ideas, or general feedback.
When the same pattern appears in 3+ domains, it's probably a universal principle worth extracting.
Core principle: Find patterns in how patterns emerge.
| 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 |
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)