Biome
Adopt Biome as a single Rust-based linter and formatter instead of ESLint plus Prettier for faster JS/TS quality checks in agent-assisted edits.
Overview
Biome is an agent skill most often used in Ship (also Build/frontend) that guides fast all-in-one linting and formatting for JavaScript and TypeScript projects.
Install
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill biomeWhat is this skill?
- All-in-one linter and formatter positioned as ESLint + Prettier replacement
- Rust-based toolchain marketed as dramatically faster than ESLint-centric stacks
- Zero-config init via npx @biomejs/biome init
- check --write workflow for fix-on-save style passes
- Progressive disclosure entry with related TypeScript, Vite, and React skills
- Skill documents 100x faster than ESLint positioning
- Quick start: 3 CLI steps (install, init, check --write)
- entry_point_tokens: 169, full_tokens: 5014 in skill metadata
Adoption & trust: 551 installs on skills.sh; 53 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your JS/TS repo runs slow, split ESLint and Prettier setups and your coding agent keeps proposing conflicting style fixes.
Who is it for?
Solo builders on TypeScript or JavaScript web apps who want a single fast formatter-linter and agent-friendly zero-config defaults.
Skip if: Codebases deeply locked to ESLint plugin ecosystems Biome cannot replace yet, or non-JS/TS stacks without Biome support.
When should I use this skill?
When you need fast linting and formatting, replacing ESLint + Prettier, or working with TypeScript/JavaScript with zero-config setup.
What do I get? / Deliverables
Biome is initialized and run with check --write so one command enforces lint and format rules the agent can rely on.
- biome.json configuration
- Formatted and lint-clean file tree after check --write
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Lint and format gates sit on the Ship/review shelf where solo builders enforce consistent style before merge or release. Biome is invoked via check --write and CI-style verification—classic pre-ship code quality, not feature implementation.
Where it fits
Run biome check before opening a PR so agent-generated diffs match project style.
Scaffold a Vite React app and wire Biome init instead of legacy ESLint config.
Add Biome to CI as the fast static gate before unit tests run.
How it compares
Toolchain reference skill for Biome—not an MCP server; replaces documenting ESLint + Prettier separately in agent context.
Common Questions / FAQ
Who is biome for?
Indie developers and agents working on JavaScript or TypeScript apps who want one Biome command instead of separate linter and formatter configs.
When should I use biome?
During Ship/review before merging; during Build/frontend when scaffolding or refactoring TS/JS; when replacing ESLint + Prettier for speed.
Is biome safe to install?
Biome is a standard npm devDependency—review the upstream package and Security Audits panel on this Prism page before adding to your repo.
SKILL.md
READMESKILL.md - Biome
{ "name": "biome", "version": "1.0.0", "category": "toolchain", "toolchain": "javascript", "framework": null, "tags": [ "linting", "formatting", "biome", "tooling", "code-quality", "typescript", "javascript", "rust" ], "entry_point_tokens": 169, "full_tokens": 5014, "related_skills": [ "../../typescript/typescript-core", "../build/vite", "../../frameworks/react" ], "author": "Claude MPM", "license": "MIT", "updated": "2025-12-31", "source_path": "toolchains/javascript/tooling/biome/SKILL.md", "repository": "https://github.com/bobmatnyc/claude-mpm-skills", "description": "Fast all-in-one linter and formatter (Rust-based replacement for ESLint + Prettier)", "when_to_use": [ "When you need fast linting and formatting", "When replacing ESLint + Prettier", "When working with TypeScript/JavaScript", "When you want zero-config setup" ], "quick_start": [ "npm install --save-dev @biomejs/biome", "npx @biomejs/biome init", "npx @biomejs/biome check --write ." ] } --- name: biome description: Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint) user-invocable: false disable-model-invocation: true version: 1.0.0 category: toolchain author: Claude MPM Team license: MIT progressive_disclosure: entry_point: summary: "Fast all-in-one linter and formatter (Rust-based replacement for ESLint + Prettier)" when_to_use: - "When you need fast linting and formatting" - "When replacing ESLint + Prettier" - "When working with TypeScript/JavaScript" - "When you want zero-config setup" quick_start: - "npm install --save-dev @biomejs/biome" - "npx @biomejs/biome init" - "npx @biomejs/biome check --write ." context_limit: 700 tags: - biome - linting - formatting - code-quality - tooling - typescript - javascript requires_tools: [] --- # Biome - Fast All-in-One Toolchain ## Overview Biome is a fast, all-in-one toolchain for web projects written in Rust. It replaces both ESLint and Prettier with a single tool that's 100x faster and provides zero-config defaults. **Key Features**: - Single tool for linting and formatting - 100x faster than ESLint - Zero configuration by default - Built-in import sorting - TypeScript-first design - Partial Prettier compatibility - Native monorepo support - VS Code integration **Installation**: ```bash npm install --save-dev @biomejs/biome ``` ## Quick Start ### 1. Initialize Biome ```bash # Create biome.json configuration npx @biomejs/biome init # Check your project npx @biomejs/biome check . # Fix issues automatically npx @biomejs/biome check --write . # Format only npx @biomejs/biome format --write . # Lint only npx @biomejs/biome lint . ``` ### 2. Package.json Scripts ```json { "scripts": { "check": "biome check .", "check:write": "biome check --write .", "format": "biome format --write .", "lint": "biome lint .", "lint:fix": "biome lint --write ." } } ``` ### 3. Basic Configuration ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }, "files": { "ignoreUnknown": false, "ignore": ["node_modules", "dist", "build", ".next"] }, "formatter": { "enabled": true, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 }, "linter": { "enabled": true, "rules": { "recommended": true } }, "javascript": { "formatter": { "quoteStyle": "single", "semicolons": "asNeeded", "trailingCommas": "all" } } } ``` ## Core Commands ### Check Command (Recommended) The `check` command runs both linting and formatting: ```bash # Check all files biome check . # Fix issues automatically biome check --write . # Unsafe fixes (may change behavior) biome check --write --unsafe . # Apply s