inherit-legacy-style

Topics in the source

• Inherit Legacy Style
• When to Activate
• When to Use
• Prerequisites
• Workflow
• Step 0 — Auto-Detect Mode
• Branch A — First-time Full-Scan
• Branch B — Incremental Sniff

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. 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 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. 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) Silently check for .ai-style-rules.md at the project root: | File exists? | Mode | |---|---| | No | Branch A — First-time Full-Scan | | Yes | Branch B — Incremental Sniff | Announce the mode in one line and proceed — never ask the user to pick. 1. Measure scale, pick a scanning tier | Tier | Source files | Strategy |

This is an excerpt. Refer to the complete source and its current requirements.