Biome for Frontend Assets in .NET Repositories

Trigger On

• the repo has biome.json, @biomejs/biome, or the user asks for a faster all-in-one frontend formatter-linter stack
• the repo wants one tool for formatting, linting, and import organization across JS, TS, CSS, JSON, GraphQL, or HTML
• the team is comparing Biome against ESLint plus Prettier or wants to simplify the current stack

Workflow

1. Decide ownership first:

- Biome as the main formatter and linter - Biome only for formatting - Biome in coexistence with ESLint for plugin gaps

1. Prefer a repo-local pinned install so CI and developer machines use the same version.
2. Generate biome.json only after confirming what the repo wants Biome to own.
3. Add repeatable scripts to package.json, for example:

- biome check . - biome check . --write

1. Keep file ownership explicit:

- Biome can own formatting, linting, and import sorting - webhint still owns site-runtime audits - ESLint may stay for plugin-heavy cases the repo intentionally keeps

1. Start migrations with check and bounded folders before flipping the whole repo to --write.
2. Re-run the frontend build and tests after broad formatting or lint-fix passes.

Deliver

• explicit Biome ownership and version pinning
• checked-in config and repeatable check commands
• a migration or coexistence plan versus ESLint and other frontend tools

Validate

• the chosen ownership model is documented
• CI and local runs use the same Biome version
• the target globs exclude generated and vendored assets
• downstream build or test flows still pass after --write runs

Related skills

Related agents