fit-inlisted

# Fit In ## The failure mode this fixes Agents write correct code in the wrong dialect. The repo uses result types; the agent throws. Tests live next to the source; the agent creates `__tests__/`. Everything is `snake_case`; the new file is `camelCase`. None of it is a bug, and all of it is cost: every divergence is a seam a reader must mentally translate across, and a codebase edited by agents long enough becomes a patchwork of five house styles with no house. The deepest version of this failure is solving a problem the codebase has *already solved* — writing a second retry helper, a second date formatter, a second pagination pattern — because the agent never looked. This skill makes reading the neighborhood a mandatory first step: match the local idiom, reuse the local solutions, and treat "improving" the style as a separate, deliberate act. ## When to Use This Skill - Writing new code (function, file, module, test) into an existing codebase - Reviewing AI-generated code that is correct but stylistically foreign - Starting work in an unfamiliar repo where your defaults would otherwise win - A reviewer keeps saying "we don't do it that way here" **Don't use when:** the repo is greenfield with no established conventions (pick good ones; there's nothing to match), or when the local pattern is itself a failure mode a sibling skill exists to fix — don't replicate swallowed errors to fit in (`loud-errors` wins), and don't copy vague naming to match the neighbors (`name-thin