Skip to content
Back to skills

Meta Pattern Recognition

ASecurity

Spot patterns appearing in 3+ domains to find universal principles

  • 19 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
businessapi

Works with

  • api

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add DangQuangSE/team-development-skills --skill meta-pattern-recognition --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meta Pattern Recognition?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Meta Pattern Recognition
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dangquangse-meta-pattern-recognition/badge)](https://www.skillsdirectory.com/skills/dangquangse-meta-pattern-recognition)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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, browser cache |
| Layering (network/storage/compute) | Separate concerns into abstraction levels | Clean architecture, OS rings |
| Queuing (message/task/request) | Decouple producer from consumer with buffer | Event systems, async processing, print queues |
| Pooling (connection/thread/object) | Reuse expensive resources | Memory management, worker pools |
| Rate limiting (API/traffic/admission) | Bound resource consumption to prevent exhaustion | LLM token budgets, DB connection limits |

## Process

1. **Spot repetition** — See same shape in 3+ places
2. **Extract abstract form** — Describe it independent of any domain
3. **Identify variations** — How does it adapt per domain?
4. **Check applicability** — Where else might this pattern help?

## Example

**Pattern spotted:** Rate limiting in API throttling, traffic shaping, circuit breakers, admission control, connection pooling

**Abstract form:** Bound resource consumption to prevent exhaustion

**Variation points:** What resource, what limit, what happens when exceeded (reject / queue / degrade)

**New application:** LLM token budgets (same pattern — prevent context window exhaustion)

## Red Flags You're Missing Meta-Patterns

- "This problem is unique" (it probably isn't)
- Multiple teams independently solving "different" problems identically
- Reinventing wheels across domains
- "Haven't we done something like this?" (yes — find it)
- Writing the same logic in 3+ different places

## Remember

- 3+ domains = likely universal principle
- Abstract form reveals new applications
- Variations show adaptation points
- Universal patterns are battle-tested across contexts

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…