biome

Lint and format JavaScript and TypeScript code with Biome.

Updated May 6, 2026
One-click install
npx skills add https://github.com/franzosterkamp/card2contact --skill biome-franzosterkamp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biome
Source: https://github.com/franzosterkamp/card2contact/tree/main/.agents/skills/biome
Command: npx skills add https://github.com/franzosterkamp/card2contact --skill biome-franzosterkamp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @biomejs/biome, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Biome addresses the slow and complex workflows of traditional JavaScript and TypeScript linters and formatters, streamlining code quality checks with blazing speed.

Core Features & Use Cases

  • Unified Toolchain: Replaces ESLint and Prettier with a single Rust-based tool for linting and formatting.
  • High Performance: Runs 100x faster than traditional solutions, making real-time code quality feasible in large projects.
  • Use Case: Automate code quality enforcement in CI pipelines for multi-repo monorepos, ensuring consistent coding standards across teams.

Quick Start

Use the biome skill to run a comprehensive code check on your project before deploying, ensuring all code adheres to style and quality standards.

Frequently Asked Questions about biome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate JavaScript and TypeScript code linting and formatting in a CI pipeline?

Automate JavaScript and TypeScript code linting and formatting in CI pipelines by running a unified tool that performs zero-configuration code analysis and correction. This enforces consistent coding standards across multi-repo monorepos before deployment.

What is the best way to replace ESLint and Prettier with a single tool for web projects?

Replacing ESLint and Prettier is best achieved with a unified Rust-based toolchain that handles both linting and formatting. It provides high performance and runs significantly faster than traditional solutions, streamlining web project workflows.

How does a fast linter improve code quality checks in large monorepos?

A fast linter improves code quality checks in large monorepos by running up to 100x faster than traditional solutions. This unparalleled speed makes real-time code analysis and correction feasible without slowing down development workflows.

Do I need to configure rules manually to perform code analysis on my TypeScript project?

Manual rule configuration is not required to perform code analysis on TypeScript projects. The tool performs fast, zero-configuration code analysis and correction out of the box, suitable for immediate integration into development workflows.

Can I check and format code across multiple repositories in a monorepo efficiently?

Checking and formatting code across multiple repositories in a monorepo is highly efficient. The tool's unified toolchain and high performance ensure consistent coding standards are maintained across all teams with blazing speed.

Why is a unified toolchain better than separate linters and formatters for maintaining code quality?

A unified toolchain is better than separate linters and formatters because it replaces multiple complex tools with a single Rust-based solution. This eliminates slow workflows and streamlines code quality checks with unparalleled speed.