Skill

patterns

Explore detected workflow patterns, review skill suggestions, and manage the patterns wiki. Use when asked to 'show patterns', 'what patterns', 'suggest skills', 'pattern report', or '/patterns'. Also trigger when the user asks about their workflow habits or wants to understand recurring behaviors across sessions.

Install

npx claudepluginhub sebastianbreguel/claude-engram

Tool Access

This skill uses the workspace's default tool permissions.

Preview

You are reviewing the user's detected workflow patterns from their session history.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

smart-explore

Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.

claude-mem

65.8k

Stats

Stars1

Forks0

Last CommitApr 13, 2026

Actions

View Source View Plugin View on GitHub View README

Patterns: Workflow Pattern Explorer

You are reviewing the user's detected workflow patterns from their session history.

The patterns wiki lives at ~/.claude/patterns/ and is updated automatically on each context compaction. It tracks:

File co-edits — files that are always modified together
Error recurrence — errors that keep appearing across sessions
Project streaks — consecutive days of activity on a project
Tool anomalies — unusual tool usage patterns per project

Step 1: Show current patterns

Run:

uv run ~/.claude/tools/mempatterns.py --report

Show the results to the user, grouped by kind.

Step 2: Check for skill suggestions

Run:

uv run ~/.claude/tools/mempatterns.py --suggest

If there are pending suggestions, present them conversationally:

Explain what the pattern is and why it might be useful as a skill
Ask the user what they'd want the skill to do — don't just generate it
Shape the skill together through conversation
Only create the SKILL.md once the user agrees on what it should do

Step 3: Handle user requests

If the user asks to:

Forget a pattern: uv run ~/.claude/tools/mempatterns.py --forget <name>
See wiki stats: uv run ~/.claude/tools/mempatterns.py --status
Rebuild from scratch: uv run ~/.claude/tools/mempatterns.py --rebuild

Key rule

Never create or update a skill without asking first. The system proposes, the user decides. Always.