Configure BiomeJS biome.jsonc files with extends and files.includes patterns.
npx skills add https://github.com/PaulRBerg/agent-skills --skill biome-js
Please help me install this Agent Skill. Skill: biome-js Source: https://github.com/PaulRBerg/agent-skills/tree/main/skills/biome-js Command: npx skills add https://github.com/PaulRBerg/agent-skills --skill biome-js
BiomeJS configuration can be complex, requiring careful setup of extends, file patterns, and project-specific overrides. This skill provides practical guidance to configure BiomeJS across projects, ensuring consistent linting and formatting configurations.
Create or update biome.jsonc at the root of your project with an extends entry (for example, ["@sablier/devkit/biome"]) and a files.includes pattern appropriate for your project (e.g., "/*.{js,json,jsonc,ts}", "!node_modules//*"). If working in a monorepo, ensure the root biome.jsonc is inherited by packages via the ["//"] syntax and add package-specific overrides as needed.
High-intent search queries and answers about installing and using this skill.
Configure BiomeJS in a monorepo by creating a root biome.jsonc with an extends entry pointing to a shared config (e.g., @sablier/devkit/biome) and explicit files.includes patterns. Use the ["//"] syntax to inherit the root config in package-level biome.jsonc files, then add package-specific overrides as needed for linting and formatting rules.
Extends in BiomeJS allows you to inherit shared configurations via npm exports. Declare extends as an array in biome.jsonc (e.g., ["@sablier/devkit/biome"]), then pair it with explicit files.includes patterns to specify which files the configuration applies to, ensuring consistent linting across your project.
In each package's biome.jsonc, inherit from the root config using ["//"] syntax, then define package-specific overrides for linting and formatting rules. This allows you to maintain a shared base configuration while customizing behavior for individual packages based on their needs.
BiomeJS works with UI projects through concrete configuration patterns for root configs and typical exclusions. Use files.includes to target your source files and node_modules exclusions, then extend shared configs to enforce consistent formatting and linting across your UI codebase.
Explicit files.includes patterns in BiomeJS ensure precise scoping of linting and formatting rules to your project's files. This prevents unintended rule application and maintains clarity about which files are covered, especially important in monorepos where different packages may have different requirements.
A biome.jsonc must include an extends entry (referencing shared configs as npm exports) and files.includes patterns defining which files the configuration applies to. This structure aligns with Biome's configuration rules and ensures explicit, maintainable configurations across your project.
sovriumValidate eslint.config.ts and tsconfig.json against documented architecture patterns.
MezzleConfigure BiomeJS linting, formatting, and code style via biome.json and npm scripts.
seo-jinseokEnforce TRUST 5 validation and code quality gates across multiple languages.
trystan2kConfigure Biome as a unified linter and formatter for JavaScript/TypeScript projects.
