mcpField
M
Meta-Pattern Recognition

Meta-Pattern Recognition

github.com/obraDevelopment756517 installsUpdated 54w ago
Repository

About Meta-Pattern Recognition

Meta-Pattern Recognition is a development skill for identifying recurring structures across domains, abstracting their shared form, and finding where they may apply. It guides users through spotting repetition, comparing variations, and checking new applications.

Key features

  1. 01Spot recurring patterns across domains
  2. 02Abstract a pattern from its context
  3. 03Compare domain-specific variations
  4. 04Identify potential new applications

Use cases

  1. 01Find shared solutions across teams
  2. 02Apply established patterns to new domains

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/obra/superpowers-skills --skill meta-pattern-recognition

After installing, type/meta-pattern-recognitionin Claude Code to confirm it loaded.

Details

From the project README

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 InAbstract FormWhere Else?
CPU/DB/HTTP/DNS cachingStore frequently-accessed data closerLLM prompt caching, CDN
Layering (network/storage/compute)Separate concerns into abstraction levelsArchitecture, organization
Queuing (message/task/request)Decouple producer from consumer with bufferEvent systems, async processing
Pooling (connection/thread/object)Reuse expensive resourcesMemory 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

Comments

Markdown supported