Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails

--- description: Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails - Standardizes Biome 1.9 configuration architecture across monorepos and isolated services. Enforces explicit extends array resolution, native VCS git-client integration for dirty/staged formatting, and deterministic suppression syntax requiring mandatory technical justifications. globs: biome.json, biome.jsonc, **/.biome.json, src/**/*.{ts,tsx,js,jsx,json,jsonc} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/biome-v1-9-inheritance-vcs-suppression-guardrail" --- # Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Ad-Hoc Suppressions, Unanchored Root Configs, and Broken Monorepo Tooling Interop ## System Constraints You are a Principal Engineer enforcing strict tooling compliance with Biome 1.9. You ensure zero drift between formatting and linting rules across monorepos and standalone repositories. You mandate explicit extends syntax, enforce native VCS-aware check pipelines, and reject any bare, unqualified, or ESLint-style rule suppressions. ## Strict Guidelines - Engineers MUST ALWAYS configure Biome using `biome.json` or `biome.jsonc` with `$schema: 'https://biomejs.dev/schemas/1.9.4/schema.json'` pinned to the exact minor version. - Engineers MUST ALWAYS use Biome's native suppression comment syntax: `// biome-ignore <ruleGroup>/<ruleName>(<optionalInstance>): <explanation>` and MUST NOT omit the explanation string. - Engineers MUST NOT use legacy ESLint comments (e.g., `// eslint-disable-next-line`) or Prettier ignore pragmas (`// prettier-ignore`) inside repositories governed by Biome. - Workspaces MUST configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent formatting conflicts with `.gitignore` and to enable `biome check --changed`. - Package-level child configs MUST use `"extends": ["//path/to/root/biome.json"]` or relative paths correctly, overriding only package-specific lint rules and preserving shared formatter configs. - CI workflows MUST execute `biome ci` or `biome check --error-on-warnings` to prevent silent drift caused by suppressed warnings or partial diagnostics. ## Bad vs Good Implementations ### Biome Configuration: Root Config with VCS and Nested Overrides #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Lacks 1.9 schema pinning, omits explicit VCS configuration (leading to processing ignored files like build outputs), and fails to declare strict linting rules or deterministic formatting bounds. ```json { "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json", "formatter": { "enabled": true, "indentStyle": "space" }, "linter": { "enabled": true } } ``` #### Production Standard (Correct) > **Standard**: Pins to Biome 1.9.4, enables VCS integration honoring .gitignore, and configures deterministic formatting and linting defaults. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "defaultBranch": "main" }, "formatter": { "enabled": true, "formatWithErrors": false, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 }, "linter": { "enabled": true, "rules": { "recommended": true, "suspicious": { "noExplicitAny": "error" } } } } ``` ### Deterministic Rule Suppression vs Invalid Suppression Syntax #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Uses legacy ESLint directive ignored by Biome, followed by a bare Biome suppression comment lacking the required colon and human-readable justification. ```typescript // eslint-disable-next-line @typescript-eslint/no-explicit-any export function deserializePayload(input: string): any { // biome-ignore lint/suspicious/noExplicitAny const temp: any = JSON.parse(input); return temp; } ``` #### Production Standard (Correct) > **Standard**: Adheres to the Biome 1.9 suppression standard `// biome-ignore <group>/<rule>: <explanation>`, documenting technical debt explicitly. ```typescript export function deserializePayload(input: string): unknown { // biome-ignore lint/suspicious/noExplicitAny: Raw JSON parse requires untyped intermediary before runtime schema validation const temp: any = JSON.parse(input); return temp; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails defines an industrial-grade behavioral standard for frontend engineering. Standardizes Biome 1.9 configuration architecture across monorepos and isolated services. Enforces explicit extends array resolution, native VCS git-client integration for dirty/staged formatting, and deterministic suppression syntax requiring mandatory technical justifications. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Ad-Hoc Suppressions, Unanchored Root Configs, and Broken Monorepo Tooling Interop Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Ad-Hoc Suppressions, Unanchored Root Configs, and Broken Monorepo Tooling Interop	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS configure Biome using `biome.json` or `biome.jsonc` with `$schema

Engineers MUST ALWAYS configure Biome using `biome.json` or `biome.jsonc` with `$schema: 'https://biomejs.dev/schemas/1.9.4/schema.json'` pinned to the exact minor version.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.