Mimic — Coding-style extraction & reproduction

What this produces

A style-profile.md: a set of decisions (not prose descriptions) an author makes, each backed by real examples mined from the repo, with do/avoid pairs and a confidence score. The profile is written to be consumed as a skill or CLAUDE.md fragment so future code generation reproduces the style. The skill ends with a hold-out validation loop that measures reproduction fidelity — do not skip it.

Core principle

Style worth extracting = the residual after auto-formatting. Strip everything Prettier/ESLint/EditorConfig already enforce (whitespace, quotes, semicolons, import order, naming case). That is reproducible by tooling and is pure noise. Target only the decisions no linter can impose: decomposition, type modeling, error handling, async patterns, test philosophy, abstraction level, and where business logic lives.

A second principle: a rule with no concrete example is worthless. Abstract rules ("prefer immutability") do not reproduce anything. A before/after pulled from the actual repo does. Every entry in the profile must cite path:line.