inherit-legacy-style
Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/inherit-legacy-style/SKILL.md
- License
- MIT
- Jobs
- Documentation, Guardrails
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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`) ## Workflow ### Step 0 — Auto-Detect Mode Silently check for `.ai-style-rules.md` at the project root: | File exists? | Mode | |---|---| | No | **Branch A — First-time Full-Scan** | …