biome-configuration

Initialize and migrate Biome configuration files with schema alignment.

187|20|Updated Nov 20, 2025

Search Tags:#schema #config #Biome #VCS #lint #formatter

Ready to run

npx skills add https://github.com/TheBushidoCollective/han --skill biome-configuration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: biome-configuration
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-biome/skills/biome-configuration
Command: npx skills add https://github.com/TheBushidoCollective/han --skill biome-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Biome setup, schema versions, VCS integration, and project organization can be error-prone without a cohesive configuration strategy. This Skill guides Biome users through a solid, scalable configuration.

Core Features & Use Cases

biome.json setup and schema alignment
VCS integration and repository hygiene
Project organization patterns for JS/TS tooling

Quick Start

Initialize or migrate a Biome configuration file, ensuring the $schema matches your Biome version.

Frequently Asked Questions about biome-configuration

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

FAQPage Schema

How do I initialize a Biome configuration file for my JavaScript project?▼

Initialize Biome configuration by creating a biome.json file with the correct $schema matching your Biome version. This ensures IDE autocomplete, schema validation, and consistent formatter and linter settings across your project.

What's the best way to manage Biome schema versions across multiple packages?▼

Use per-package overrides in biome.json to apply version-specific schemas to individual packages while maintaining a root configuration. This approach scales configuration management across monorepos and respects per-project tooling requirements.

How do I integrate Biome configuration with version control and .gitignore?▼

Configure Biome to respect .gitignore patterns in biome.json and commit your configuration file to VCS. This ensures consistent linting and formatting behavior across team members while excluding ignored files from processing.

Can I organize my Biome configuration for multiple JavaScript and TypeScript projects?▼

Yes. Structure your biome.json to support project organization patterns with root and per-package configurations. This enables standardized formatter and linter settings while allowing project-specific overrides at scale.

What should I do when migrating an existing project to Biome?▼

Migrate by initializing biome.json with the appropriate schema version, configuring VCS integration, and establishing project organization patterns. Ensure formatter and linter settings align with your team's standards before deployment.