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
Decision gist · record as of 2026-07-25
Biome sets up unified formatting and linting for JavaScript, TypeScript, and CSS in .NET repositories with Node-based frontend assets. 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.
Use it when
- Biome migration involves three steps: audit your current Prettier, ESLint, and Stylelint rules to map them into biome.json.
- Biome can coexist with specialized linters during transition.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/biome · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 2 files
catalog/Tools/Biome/skills/biome/SKILL.md
catalog/Tools/Biome/skills/biome/manifest.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Set up Biome as a unified formatter and linter for JavaScript/TypeScript/CSS in .NET repos”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
webhint runs runtime audits against .NET browser-facing sites, catching accessibility, performance, security header, SEO, and PWA issues that static linters miss. Configure a `.hintrc` baseline, point it at your local or deployed URL, and get categorized findings ready for the team to act on.
Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
sonarjs integrates SonarJS-derived rules into ESLint for .NET repositories shipping JavaScript or TypeScript frontends. It surfaces cognitive complexity limits, bug-prone patterns, and maintainability issues beyond baseline linting, supporting both local developer workflows via eslint-plugin-sonarjs and server-side SonarQube or SonarCloud gates.
Chous adds architectural guardrails to growing frontend codebases in .NET projects by linting folder structure, naming conventions, and file placement against a checked-in policy. It runs as a CLI gate to catch layout drift before it compounds, complementing semantic linters without replacing them. Use it when structure policy matters more than syntax enforcement.
Ultracite unifies linting and formatting through multiple providers—Biome (default), ESLint+Prettier, or Oxlint—delivering framework-specific presets and sensible defaults out of the box. It replaces traditional multi-tool setups with a single, faster solution optimized for React, Next.js, Vue, Svelte, and other modern frameworks. Includes Git hook integration, AI editor support, and migration tooling for upgrading from legacy configurations.
More skills metalint (MIT) · biome (MIT) · Linter Formatter Init (unlicensed) · htmlhint (MIT) · Biome Validator (unlicensed) · type-inference (Apache-2.0) · biome-developer (Apache-2.0) · ultracite (MIT)