Skill

lean-claude-md

Trim a CLAUDE.md file to only the lines that change behavior. Applies the 30-line principle from Claude Code's creator. Use when CLAUDE.md feels bloated.

Install

npx claudepluginhub artmin96/forge-studio --plugin context-engine

Tool Access

This skill is limited to using the following tools:

ReadWriteGlob

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

138.8k

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

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Process

Read the CLAUDE.md at the path in $ARGUMENTS (default: ./CLAUDE.md)

For every line, ask: "If I remove this, would Claude make mistakes?"

If YES → keep it
If NO → mark for removal

Check for redundancy with Claude's defaults:

Claude already reads files before editing (don't need to say so)
Claude already uses git (don't need to explain git workflows)
Claude already follows language conventions (don't need to specify them)
Claude already writes tests (don't need generic test instructions)

Check for lines that should be hooks instead:

"Always run linter" → should be a PostToolUse hook
"Never force push" → should be a PreToolUse blocking hook
If it says "always" or "never", it might belong in a hook

Apply primacy/recency placement:

Most-violated rules at the TOP (first 5 lines)
Same critical rules at the BOTTOM (last 5 lines)
Less critical in the middle

Lean CLAUDE.md: Every Line Must Earn Its Place

Based on Boris Cherny's (Claude Code creator) workflow: ~100 lines that outperform 500-line files. The key: every rule exists because it solved a real problem.

Process

Read the CLAUDE.md at the path in $ARGUMENTS (default: ./CLAUDE.md)
For every line, ask: "If I remove this, would Claude make mistakes?"
- If YES → keep it
- If NO → mark for removal
Check for redundancy with Claude's defaults:
- Claude already reads files before editing (don't need to say so)
- Claude already uses git (don't need to explain git workflows)
- Claude already follows language conventions (don't need to specify them)
- Claude already writes tests (don't need generic test instructions)
Check for lines that should be hooks instead:
- "Always run linter" → should be a PostToolUse hook
- "Never force push" → should be a PreToolUse blocking hook
- If it says "always" or "never", it might belong in a hook
Apply primacy/recency placement:
- Most-violated rules at the TOP (first 5 lines)
- Same critical rules at the BOTTOM (last 5 lines)
- Less critical in the middle

Output

Present two versions:

Annotated original: Each line marked [KEEP], [REMOVE], or [→ HOOK]
Trimmed version: The lean CLAUDE.md with only the keepers

Ask before overwriting the original. Suggest saving the original as CLAUDE.md.backup first.

The 30-Line Test

If your trimmed version is still over 100 lines, you're probably including things Claude already does. Be more aggressive.