The Complete Production SOP: How to Deploy and Run Biome Toolchain Fast Rust-Based Linter and Formatter in Autonomous AI Agents

Autonomous coding runtimes (Claude Code, Cursor, Windsurf, Codex) read skill directives dynamically from local workspace configuration paths or root agent stores (~/.agents/skills/ or .claude/skills/). Mounting the biome-linter-formatter-rust SKILL.md injects procedural boundaries directly into the agent's system awareness without bloating long-term session context. The agent parses the frontmatter triggers ('configure biome.json', 'run biome check write', 'replace prettier eslint biome') to activate Rust-powered linting whenever file modifications occur.

---
name: "biome-linter-formatter-rust"
description: "Format and lint JavaScript, TypeScript, and JSON in milliseconds using Rust-powered Biome."
metadata:
  author: "Biome"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "configure biome.json"
  - "run biome check write"
  - "replace prettier eslint biome"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Biome Toolchain Fast Rust-Based Linter and Formatter SOP

1. Initialize: Execute `npx @biomejs/biome init` to generate a canonical `biome.json`.
2. Configure rules: Enforce 2-space indentation, double quotes, and enable recommended linting rules.
3. Format & Lint: Run `npx @biomejs/biome check --write <target-path>` to fix formatting and lint errors.
4. Clean Conflicts: When replacing Prettier and ESLint, remove legacy configuration files (`.prettierrc`, `.eslintrc*`) to avoid toolchain contention.
5. Verify: Ensure return code is 0 before closing execution loop.

Biome requires zero external API keys or remote tokens, ensuring an exceptional security profile (98/100). However, the agent must ensure that the `@biomejs/biome` binary or package is properly pinned in `devDependencies` to avoid version drift between developer workstations and CI runners. The agent runs a non-destructive package manager check to install the local binary before modifying any source code.

Once triggered by phrases like 'configure biome.json' or 'replace prettier eslint biome', the agent invokes Biome's initialization command and creates a fine-tuned configuration. If existing ESLint or Prettier setups exist, the agent consumes Biome's migration tool (`npx @biomejs/biome migrate prettier`) to preserve existing line widths and quote rules seamlessly without manual translation errors.

{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true
  },
  "files": {
    "ignoreUnknown": false,
    "includes": ["src/**", "tests/**"]
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "style": {
        "useConst": "error",
        "noNonNullAssertion": "warn"
      },
      "suspicious": {
        "noExplicitAny": "warn"
      }
    }
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "double",
      "semicolons": "always"
    }
  }
}

The skill mandates that the AI agent execute a deterministic quality gate prior to reporting a task complete. By running `npx @biomejs/biome check --write src/`, the agent simultaneously checks formatting, organizes imports, and applies safe linter autofixes. If unsafe lint errors are encountered, the agent parses the stderr output, fixes the source code directly, and re-executes the check until a clean return code (0) is achieved.