Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression

--- description: Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression - Enforces strict configuration architecture for Biome 1.9+ across monorepos and standalone repositories. Mandates native VCS ignore file integration to prevent linting build artifacts, centralized configuration inheritance via the 'extends' array, and deterministic, documented inline suppression comments. globs: biome.json, biome.jsonc, **/*.{ts,tsx,js,jsx,json,jsonc} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/biome-configuration-inheritance-suppression-standard" --- # Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Duplicated Root Configs, Missing VCS Bindings, and Naked Legacy ESLint Suppression Comments ## System Constraints You are a Principal Software Architect enforcing Biome 1.9 production standards. You must strictly enforce configuration inheritance through the 'extends' array, verify native Git integration via the 'vcs' block, and reject any lint suppression lacking the deterministic 'biome-ignore <rule>: <explanation>' syntax. ## Strict Guidelines - Engineers MUST ALWAYS configure the top-level 'vcs' block with 'clientKind': 'git', 'enabled': true, and 'useIgnoreFile': true in the root biome.json. - Engineers MUST ALWAYS format inline suppressions using the exact syntax: '// biome-ignore <group>/<rule>: <deterministic reason>', providing explicit architectural justification. - Engineers MUST NOT use legacy '// eslint-disable-next-line' or unreasoned '// biome-ignore' directives under any circumstance. - Monorepo packages MUST inherit shared configurations via the 'extends': ["@scope/biome-config"] or 'extends': ["../../biome.json"] attribute rather than redefining base linter and formatter rules. - CI/CD pipelines and pre-commit hooks MUST execute 'biome check --diagnostic-level=error --suppression-reason=mandatory' to fail builds on undocumented suppressions. ## Bad vs Good Implementations ### Biome Root Configuration (biome.json) #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Manually maintains an ignore list instead of leveraging native VCS integration, risking divergence from .gitignore and accidental linting of untracked build artifacts. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "files": { "ignore": ["node_modules", "dist", "build", ".next"] }, "linter": { "enabled": true } } ``` #### Production Standard (Correct) > **Standard**: Enables native git ignore parsing through 'vcs' and ignores unknown file types, eliminating duplicate maintenance across .gitignore and biome.json. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "defaultBranch": "main" }, "files": { "ignoreUnknown": true }, "linter": { "enabled": true, "rules": { "recommended": true } } } ``` ### Deterministic Suppression Syntax vs Legacy/Naked Suppressions #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The first example uses dead ESLint annotations ignored by Biome. The second example omits the required trailing colon and explanatory reason for suppression. ```typescript // eslint-disable-next-line @typescript-eslint/no-explicit-any const legacyPayload: any = JSON.parse(raw); // biome-ignore lint/suspicious/noExplicitAny const nextPayload: any = JSON.parse(raw); ``` #### Production Standard (Correct) > **Standard**: Uses canonical Biome 1.9 suppression syntax with the rule category, specific rule name, colon separator, and an immutable technical justification. ```typescript // biome-ignore lint/suspicious/noExplicitAny: third-party webhook payload schema is unversioned and validated at runtime via Zod const validatedPayload: any = JSON.parse(raw); ``` ### Monorepo Package Configuration Inheritance #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Copies root configuration directly into a child workspace package, creating configuration drift when organization-wide formatting or lint standards evolve. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "formatter": { "lineWidth": 100, "indentStyle": "space" }, "linter": { "rules": { "recommended": true } } } ``` #### Production Standard (Correct) > **Standard**: Inherits base formatting and linting invariants from the root configuration via 'extends' while defining package-scoped overrides only where strictly necessary. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "extends": ["../../biome.json"], "javascript": { "jsxRuntime": "transparent" } } ```

Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration architecture for Biome 1.9+ across monorepos and standalone repositories. Mandates native VCS ignore file integration to prevent linting build artifacts, centralized configuration inheritance via the 'extends' array, and deterministic, documented inline suppression comments. 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: Duplicated Root Configs, Missing VCS Bindings, and Naked Legacy ESLint 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	Duplicated Root Configs, Missing VCS Bindings, and Naked Legacy ESLint 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 the top-level 'vcs' block with 'clientKind'

Engineers MUST ALWAYS configure the top-level 'vcs' block with 'clientKind': 'git', 'enabled': true, and 'useIgnoreFile': true in the root biome.json.

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.