agentleFS
G1JoshiG1Joshi/Agent-Skills/skills/tools/biome/SKILL.md

biome

Skill15 starsChanged 43 days agoMITView on GitHub

Expert Biome toolchain assistance covering ultra-fast Rust-based formatting, linting, and imports sorting. Use when configuring Biome, replacing Prettier and ESLint, or enforcing sub-millisecond CI lint gates in JavaScript/TypeScript projects.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run biome ci . in CI pipelines to enforce formatting and lint rules in a fraction of a second.

    line 136
  2. Distinctive:

    Run Prettier and Biome simultaneously on the same files.

    line 142
  3. Very specific:

    Use --unsafe autofix flags in automated CI jobs without human review.

    line 143

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Biome

Biome is a unified, high-performance toolchain written in Rust that provides sub-millisecond code formatting and linting for JavaScript, TypeScript, and JSON.

When to Use

  • Ultra-Fast Rust-Powered Linter & Formatter: Formatting and linting JavaScript, TypeScript, JSX, and JSON 25x faster than Prettier/ESLint.
  • Unified Toolchain Setup: Replacing separate ESLint, Prettier, and import-sorter configs with a single biome.json.
  • Instant CI Verification: Checking formatting, imports, and syntax in sub-seconds in automated CI pipelines.
  • Prettier & ESLint Migration: Automated zero-friction migration using biome migrate.

Quick Start

# Initialize Biome configuration in project
npx @biomejs/biome init

# Format and lint entire workspace in milliseconds
npx @biomejs/biome check --write ./src

Core Concepts

Declarative Configuration (biome.json)

Consolidating formatting, linting, and import sorting:

{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      },
      "style": {
        "useConst": "error"
      }
    }
  },
  "organizeImports": {
    "enabled": true
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "double",
      "semicolons": "always"
    }
  }
}

Biome CLI Execution in Workflows

Formatting, checking, and applying autofixes:

# Check formatting, lint rules, and import ordering
npx @biomejs/biome check .

# Automatically apply safe fixes and formatting across all files
npx @biomejs/biome check --write .

# Format only (drop-in Prettier replacement)
npx @biomejs/biome format --write ./src

# CI verification (fails with non-zero exit code if changes needed)
npx @biomejs/biome ci .

Migrating from Prettier & ESLint

Importing existing rules automatically:

# Migrate from Prettier configuration
npx @biomejs/biome migrate prettier --write

# Migrate from ESLint configuration
npx @biomejs/biome migrate eslint --write

Common Patterns

Complete biome.json Configuration with Recommended Rules

Problem: Slow CI linters (ESLint + Prettier taking >60s on large codebases).

Solution: Adopt unified biome.json replacing both:

{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "organizeImports": { "enabled": true },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": { "noUnusedVariables": "error" }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  }
}

Best Practices

Do:

  • Target Biome 1.9+ as a unified linter, formatter, and import-sorter to eliminate multiple competing tools.
  • Run biome ci . in CI pipelines to enforce formatting and lint rules in a fraction of a second.
  • Enable useIgnoreFile: true so Biome automatically respects your .gitignore rules.
  • Install the official Biome VS Code / Neovim extension for instant formatting on save.

Don't:

  • Run Prettier and Biome simultaneously on the same files; they will conflict.
  • Use --unsafe autofix flags in automated CI jobs without human review.
  • Ignore schema validation; keep $schema set in biome.json for IDE autocomplete.

Troubleshooting

ErrorCauseSolution
Biome failed to parse fileUnsupported syntax or invalid JSON/CSS file extension.Add path glob to files.ignore in biome.json.
Conflict with ESLint / Prettier in editorMultiple formatters configured simultaneously in IDE.Set Biome as default formatter in .vscode/settings.json: editor.defaultFormatter: "biomejs.biome".
biome command not found in CIPackage not installed in dependencies.Use npx @biomejs/biome ci ./src in CI pipeline.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.