Meta-Pattern Recognition
Spot patterns appearing in 3+ domains to find universal principles
Best use case
Meta-Pattern Recognition is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Spot patterns appearing in 3+ domains to find universal principles
Teams using Meta-Pattern Recognition should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sp-meta-pattern-recognition/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Meta-Pattern Recognition Compares
| Feature / Agent | Meta-Pattern Recognition | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Spot patterns appearing in 3+ domains to find universal principles
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
Testing Anti-Patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
microservices-patterns
Comprehensive microservices patterns skill covering service mesh, traffic management, circuit breakers, resilience patterns, Istio, and production microservices architecture
meta-cognition
Meta-cognitive framing for analyze-before-doing, ownership routing, risk gating, minimum-closure planning, and retrospective extraction in multi-agent work. Use when the user says 先分析再做 / 先别动手 / 先判断 / 先定方案, when work spans multiple agents or needs dispatch/orchestration, when CEO-style delegation or group command requires owner+deadline+closure, when abnormal sessions/cron/jobs/runs need real follow-through instead of status-only reporting, or when a task needs strategy, PRD, first-principles thinking, verification, and postmortem/retro.
fabric-pattern
Integrate Daniel Miessler's Fabric patterns into local workflows for structured prompting, text transformation, and retrieval-assisted processing.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
claw-metagenomics
Shotgun metagenomics profiling — taxonomy, resistome, and functional pathways
architecture-patterns
Software architecture patterns and best practices
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
agent-patterns
Format SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.
wemp-operator
> 微信公众号全功能运营——草稿/发布/评论/用户/素材/群发/统计/菜单/二维码 API 封装
zsxq-smart-publish
Publish and manage content on 知识星球 (zsxq.com). Supports talk posts, Q&A, long articles, file sharing, digest/bookmark, homework tasks, and tag management. Use when publishing content to 知识星球, creating/editing posts, uploading files/images/audio, managing digests, batch publishing, or formatting content for 知识星球.