Inherit Legacy Style

This one's for when you're onboarding Claude to a hand-written legacy codebase and don't want it rewriting everything in its own preferred style. It scans your project across four meta-architecture dimensions (file anatomy, state handling, infrastructure placement, error patterns), figures out what's consensus versus what's noise, then grills you one question at a time on real conflicts it found. The output is a `.ai-style-rules.md` with golden file examples and concrete DONTs that gets referenced in your CLAUDE.md so every subsequent code task opens with a compliance check. It's language-agnostic and works incrementally via Git diffs. Use it when style drift is a bigger risk than the hour you'll spend teaching the model your project's actual conventions.

skills.sh installs: 4.8K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill inherit-legacy-style --agent claude-code

Installs into .claude/skills of the current project.

Files

Inherit Legacy Style

Prevents AI code style drift in legacy projects by scanning the codebase for implicit conventions across 4 meta-architecture dimensions, resolving conflicts with the user one at a time, and crystallizing the consensus into an enforceable .ai-style-rules.md. Fully language- and framework-agnostic.

When to Activate

User types /inherit-legacy-style
User mentions onboarding AI onto a hand-written legacy project
User is worried about AI-generated code "drifting" from existing project conventions
User wants to extract and codify their project's implicit coding rules

When to Use

Use this skill when you need to preserve legacy project style and prevent AI-generated style drift. See When to Activate above for trigger conditions.

Prerequisites

Git (recommended; non-Git projects fall back to file timestamps for incremental mode)
Read/Write access to the project root (generates .ai-style-rules.md and optionally CLAUDE.md)