code-style

Apply the repo conventions: braced if/else blocks with blank-line spacing, type over interface, camelCase functions and PascalCase types, and ~/ path-alias imports. Run npm run format so Biome applies double quotes, semicolons, and line width 130.

Run a simplicity review over the diff or whole repo. It emits one-line findings tagged dup, delete, stdlib, native, shrink, or speculative, with every dead-code claim verified by grep across src, sanity, templates, and scripts before reporting.

Prefer type for object shapes, props, and contracts, including Astro component Props. The only exception is ambient declaration-merging blocks such as ImportMetaEnv in env.d.ts, which must use interface because type cannot merge declarations.

No. Biome only sees the frontmatter of .astro files, so template markup must be kept consistent by hand. Biome does enforce braced statements via useBlockStatements, but the blank-line spacing between blocks is a manual convention.

Do not flag single-implementation abstractions that are documented extension seams, such as Plop templates, create-* schema factories, or anything a SKILL.md or docs file names as an edit point. Flag speculative code only when grep shows zero usage and no documented purpose.