Pattern Extraction

Three-tier system for documenting code patterns to optimize token usage

8 stars 3 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Freddy-CHEN-ux/00_claude_skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Freddy-CHEN-ux/00_claude_skills --skill pattern-extraction
Manual install
git clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/pattern-extraction ~/.claude/skills/pattern-extraction

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Pattern Extraction Workflow

## Purpose

Optimize token usage and ensure consistency by documenting code patterns once instead of repeatedly exploring codebases.

## Problem

When implementing features in existing codebases, agents typically:
1. Explore the codebase to understand patterns
2. Find example files demonstrating patterns
3. Extract imports, structure, and style
4. Adapt patterns for new features

**Inefficiency**: Repeating exploration wastes tokens and risks inconsistency.

**Solution**: Extract patterns once using a three-tier documentation system, then reference docs instead of re-exploring.

---

## Three-Tier Documentation System

### Tier 1: Architecture Patterns (Conceptual)

**File**: `systems/{system}/architecture-patterns.md`

**Purpose**: Explain **WHY** patterns exist and **WHAT** the rules are.

**Contents**:
- Non-negotiable patterns and mandatory rules
- Architectural reasoning and trade-offs
- When each pattern applies
- Quick reference table of canonical files
- Common import paths

**Example**: VioletDashboard's API Proxy Pattern explains why all backend calls must go through Next.js API routes.

---

### Tier 2: Reference Implementations (Concrete)

**File**: `systems/{system}/reference-implementations.md`

**Purpose**: Point to specific **EXAMPLES** in the actual codebase.

**Contents**:
- File paths with line numbers
- Detailed code excerpts from actual files
- What each reference file demonstrates
- When to use each as a template
Read the full skill on GitHub

Details

Skill name
pattern-extraction
Path
skills/pattern-extraction/SKILL.md
Repo updated
10 January 2026

FAQ

What does the Pattern Extraction skill do?

Three-tier system for documenting code patterns to optimize token usage

How do I install the Pattern Extraction skill?

Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Pattern Extraction popular?

It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.

Related skills

Add Integration

8

Freddy-CHEN-ux/00_claude_skills

Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.

Software Development

AI Agents

8

Freddy-CHEN-ux/00_claude_skills

Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)

AI, LLMs & Agents

AI LLM

8

Freddy-CHEN-ux/00_claude_skills

Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.

AI, LLMs & Agents

Philosophy of Software Design

5

vnovakovits/claude-skills

Apply John Ousterhout's "A Philosophy of Software Design" (2018; 2nd ed. 2021) — design as the fight against complexity. Covers complexity's symptoms (change amplification, cognitive load, unknown unknowns) and causes (dependencies, obscurity), strategic vs tactical programming, deep vs shallow modules, information hiding and leakage, temporal decomposition, somewhat-general-purpose interfaces, different layer different abstraction, pass-through methods, pulling complexity downwards, defining errors out of existence, design it twice, comments as design, and the red-flags catalogue. Adds the de

Software Development

Linear Manager

8

Freddy-CHEN-ux/00_claude_skills

Create, update, search, and comment on Linear issues. Use for project management and issue tracking during development.

Software Development

Pi Extension Dev

5

bolasblack/claude-skills

End-to-end workflow for developing, debugging, configuring, and shipping pi-coding-agent extensions and pi packages. Use when building or maintaining extensions, skills, prompt templates, themes, settings.json setups, provider integrations, or when updating this skill after pi releases. Do NOT use for general coding questions unrelated to pi extension development.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.