No AI-style code

Match the file you're editing. New code should read like the maintainer who owns this file wrote it on an ordinary day — not like a textbook example generated in isolation.

Core rules

• Short, natural names over descriptive-but-bloated ones: cfg, repo, srv, pool — not applicationConfiguration, userRepositoryInstance, httpServerInstance, databaseConnectionPool.
• Error context is a phrase, not a sentence: "create user: %w", not "failed to create user in the database: %w".
• Don't split a type into an Interface + Impl pair for one concrete implementation — see [[z-no-over-engineering]].
• Before writing, read a neighboring file in the same package and match its naming density, abstraction level, and idiom. A diff that looks more "polished" than its surroundings is a signal, not a compliment.
• Prefer the shape the codebase already uses over a textbook-correct alternative it doesn't use — consistency with the file beats abstract correctness.

Examples

AI-style — avoid: