Deterministic Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Standards

--- description: Deterministic Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Standards - Enforces strict configuration schema compliance for Biome 1.9 single-binary toolchains across monorepo architectures. Prevents non-deterministic linting and formatting regressions by mandating native VCS integration, explicit extends resolution paths, and structured inline suppression syntax with explanatory justifications. globs: biome.json, biome.jsonc, **/*.{js,mjs,cjs,ts,jsx,tsx,json,jsonc,css} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/biome-v1-9-config-inheritance-suppression-guardrail" --- # Deterministic Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Standards > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Ad-hoc ESLint/Prettier Hybrid Drift, Loose Global Ignores, and Unjustified Suppression Comments ## System Constraints You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate strict adherence to root-anchored biome.json configuration inheritance, deterministic ignore patterns using native vcs integration, and structured inline rule suppression comments containing mandatory technical justifications. ## Strict Guidelines - Engineers MUST ALWAYS configure `vcs.enabled: true`, specify `vcs.clientKind: 'git'`, and set `vcs.useIgnoreFile: true` in the root `biome.json` to prevent divergence between Git working trees and Biome evaluation. - Engineers MUST ALWAYS use relative POSIX file paths prefixed with `./` when declaring configuration inheritance via the `extends` array in child workspace manifests. - Engineers MUST NOT use unanchored glob patterns or legacy `.eslintignore`/`.prettierignore` files; all format/lint exclusions must be declared within the canonical `files.ignore` array. - Engineers MUST NEVER use bare suppression comments; every `biome-ignore` comment MUST specify the exact diagnostic category, the precise rule name, and an explicit explanatory explanation string (e.g., `// biome-ignore lint/suspicious/noExplicitAny: Temporary boundary parsing from untyped third-party webhook payload`). - Engineers MUST NOT rely on deprecated Biome schema properties; configurations MUST target `$schema: 'https://biomejs.dev/schemas/1.9.4/schema.json'` to ensure deterministic CLI validation across CI/CD runners. ## Bad vs Good Implementations ### Biome Configuration: Root Manifest and Workspace Inheritance #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Uses an outdated schema, lacks native VCS integration (causing uncommitted ignore file discrepancies), and relies on redundant manual folder ignore lists rather than delegating to `.gitignore` via the Biome VCS engine. ```json { "$schema": "https://biomejs.dev/schemas/1.8.0/schema.json", "files": { "ignore": ["node_modules", "dist", "*.log"] }, "linter": { "enabled": true } } ``` #### Production Standard (Correct) > **Standard**: Adheres to Biome 1.9 schema standards, delegates ignore resolution directly to Git VCS primitives, and explicitly sets strict rule sets with production formatting invariants. ```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 Syntax #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Suppression comments omit the required diagnostic domain and rule identifier, and fail to provide a required technical rationale for bypassing safety checks. ```typescript // biome-ignore: disable rule export function deserializePayload(rawInput: unknown): any { // biome-ignore lint return JSON.parse(rawInput as string); } ``` #### Production Standard (Correct) > **Standard**: Suppression strictly targets specific rule namespaces and embeds an unambiguous technical justification required for automated compliance audits. ```typescript // biome-ignore lint/suspicious/noExplicitAny: Required for runtime boundary interop with upstream unversioned RPC bridge export function deserializePayload(rawInput: unknown): any { // biome-ignore lint/style/noNonNullAssertion: Input is pre-validated by outer schema gateway return JSON.parse(rawInput! as string); } ```

Architectural Specification & Invariant Rationale

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

Deterministic Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration schema compliance for Biome 1.9 single-binary toolchains across monorepo architectures. Prevents non-deterministic linting and formatting regressions by mandating native VCS integration, explicit extends resolution paths, and structured inline suppression syntax with explanatory 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 ESLint/Prettier Hybrid Drift, Loose Global Ignores, and Unjustified Suppression Comments 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 ESLint/Prettier Hybrid Drift, Loose Global Ignores, and Unjustified Suppression Comments	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 `vcs.enabled

Engineers MUST ALWAYS configure `vcs.enabled: true`, specify `vcs.clientKind: 'git'`, and set `vcs.useIgnoreFile: true` in the root `biome.json` to prevent divergence between Git working trees and Biome evaluation.

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.