biome
Biome integrates into .NET repositories to provide combined formatting, linting, and import organization across JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML. The skill handles ownership decisions between Biome and existing tools like ESLint or Prettier, generates configuration, and establishes repeatable commands for CI and local development. It guides migration strategies and validates that your build and test flows remain stable after changes.
Biome sets up unified formatting and linting for JavaScript, TypeScript, and CSS in .NET repositories with Node-based frontend assets.
AI-generated summary based on this skill's SKILL.md
Install
managedcode/dotnet-skills/biome · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/Biome/skills/biome ~/.claude/skills/biomenpx skillfed install managedcode/dotnet-skills/biomeFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up Biome as a unified formatter and linter for JavaScript/TypeScript/CSS in .NET repos?
Biome integrates into .NET repositories as a single tool replacing Prettier, ESLint, and Stylelint. Install Biome via npm or your package manager, create a biome.json configuration file at your repo root, and define rules for JavaScript, TypeScript, CSS, JSON, and HTML. Run `biome check` to lint and format in one pass, or `biome check --write` to apply fixes. Pin Biome's version in package.json and CI scripts to ensure consistency across local and build environments.
What is the best way to replace Prettier, ESLint, and Stylelint with Biome?
Biome migration involves three steps: audit your current Prettier, ESLint, and Stylelint rules to map them into biome.json; run Biome in check mode alongside your existing tools to validate rule parity; then gradually disable or remove the old tools once Biome passes all checks. Biome's import organizer and unified formatter reduce configuration complexity. Test your CI pipeline and build output before fully committing to the migration.
How do I configure Biome ownership and coexistence with existing frontend tools?
Biome can coexist with specialized linters during transition. Use biome.json to define which file types and rules Biome owns—for example, formatting all JavaScript and TypeScript, while ESLint handles custom business logic rules. Document ownership in your team's style guide and CI configuration. Exclude generated assets and node_modules using Biome's ignore patterns to prevent conflicts and reduce noise.
How do I bootstrap Biome with pinned versions and repeatable CI commands?
Biome bootstrap starts with installing a specific version in package.json (e.g., "biome": "1.x.y") and committing the lock file. Create npm scripts in package.json: `"lint": "biome check"` and `"format": "biome check --write"`. In your CI pipeline, run the same scripts to ensure local and build environments use identical Biome behavior. Store biome.json in version control so all team members and CI agents apply the same rules.
Can Biome handle JSON, GraphQL, and HTML formatting alongside JavaScript and TypeScript?
Biome supports formatting and linting for JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML in a single tool. Configure each language's rules in biome.json and run `biome check` across your entire codebase. Biome's import organizer also works on supported file types, reducing the need for separate tools and simplifying your frontend toolchain in .NET projects.
How do I exclude generated assets and configure Biome for .NET node_modules?
Biome respects .gitignore patterns and allows explicit ignore rules in biome.json under the `files` section. Exclude node_modules, dist, build, and generated directories to prevent linting and formatting unnecessary files. For .NET projects, also exclude bin, obj, and other build artifacts. This keeps Biome focused on source code and speeds up check and format operations in your CI pipeline.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
catalog/Tools/Biome/skills/biome/SKILL.md
catalog/Tools/Biome/skills/biome/manifest.json