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
- none. No account, no API key, no payment — this skill is a single guidance file.
- Level
- Beginner
- 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:
Quick answer
Inherit Legacy Style is a free Muse skill that stops AI style drift on legacy codebases by scanning implicit conventions, resolving conflicts one at a time, and crystallizing them into enforceable style rules. It auto-detects its mode: on a first run it measures project scale, then scans across four dimensions, file anatomy, state and control flow, naming and formatting.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none. No account, no API key, no payment — this skill is a single guidance file. Install "Inherit Legacy Style" for me. It prevents AI style drift on legacy projects: it scans a codebase for its implicit conventions, resolves conflicts with me one at a time, and writes an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs), plus an optional CLAUDE.md hook. Once it is installed, I use it by pointing my agent at a legacy codebase I own. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/inherit-legacy-style/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. It is the only file this skill needs. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 ccce44b6240e346e2d564a035f45abf01842cfc03f4c0253050b8304c505f709 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none, this file is guidance text only) - every shell command it runs (expected: none during installation; when the skill is used later, it runs read-only scan commands on my codebase, such as listing tracked files, and writes a rules file into my project) - every place credentials, API keys or personal data are read, stored or sent (expected: none) - any obfuscated or encoded code (expected: none, plain markdown guidance) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "inherit-legacy-style". 6. Verify with no network calls: frontmatter valid, skill name is inherit-legacy-style, and the file is in place. 7. Report what was installed, where, and what I still need to do myself. Nothing else is required: to use the skill afterwards, I point my agent at a legacy codebase and let it scan for the unwritten style rules. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.