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.
npx -y skills add affaan-m/ecc --skill inherit-legacy-style --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
metabase/metabase
metabase/metabase
telagod/code-abyss
github/awesome-copilot
DietrichGebert/ponytail