Inherit Legacy Style
Stop AI style drift on legacy codebases: scan implicit conventions across 4 dimensions, resolve conflicts with you one at a time, and crystallize them into an enforceable .ai-style-rules.md.
- What
- Stop AI style drift on legacy codebases: scan implicit conventions across 4 dimensions, resolve conflicts with you one at a time, and crystallize them into an enforceable .ai-style-rules.md.
- Cost
- Free
- Needs
- Use "Inherit Legacy Style" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a workflow skill that stops AI-generated code from drifting away from a hand-written legacy codebase's style. It auto-detects its mode: on a first run it measures the project scale (small, medium or large), scans the codebase across four meta-architecture dimensions (file anatomy, state and control flow, infrastructure placement, error handling), applies signal-threshold noise reduction so weak conflicts auto-resolve without bothering you, then grills you on strong conflicts strictly one question at a time, each with evidence and four options. The consensus becomes a .ai-style-rules.md with Golden Files (real exemplar paths), concrete naming and state-control rules, and DONTs, plus an optional enforcement hook (soft via CLAUDE.md reference, hard via PreToolUse, or none, your call). On later runs it does an incremental sniff: it diffs recent Git changes against the recorded rules, grills new conflicts the same way, and appends evolution logs without overwriting old rules. When hooked, every code-writing task opens with a compliance declaration naming the exemplar followed and the DONTs avoided. A community contribution to the ECC collection. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it needs read/write access to your project root and your answers for the grilling step, so it is interactive by design; it aligns meta-architecture only, not syntax or stack quality, and it never copies bugs from exemplar files. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Inherit Legacy Style" with your Muse. Prerequisites: read/write access to your project root. Git recommended (falls back to file timestamps). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/inherit-legacy-style/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse (in your project) and add: "Onboard yourself onto this legacy codebase without changing its style." 3. Answer the grilling questions one at a time when style conflicts come up, then review the generated .ai-style-rules.md before keeping it. Tip: run it once per project, then re-run after big refactors for the incremental sniff. Safety: a skill is plain-text instructions; it runs nothing by itself. Review the generated rules file and any hook it proposes before accepting them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.