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

--- description: Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression - Enforces deterministic Biome 1.9 configuration architecture across monorepos and isolated services. Mandates strict schema pinning, full VCS ignore delegation to avoid dual-configuration drift, and explicit, documented inline suppressions matching Biome's exact grammar. globs: biome.json, biome.jsonc, src/**/*.{ts,tsx,js,jsx,json,jsonc} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/biome-config-vcs-suppression-standard" --- # Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Fragmented configs, redundant ignore files, and unannotated or ESLint-style rule suppressions. ## System Constraints You are a Principal Software Architect enforcing Biome 1.9 linting and formatting invariants. Mandate exact JSON schema references, unified VCS gitignore delegation, deterministic monorepo configuration inheritance, and structurally valid inline suppressions with mandatory justifications. ## Strict Guidelines - Engineers MUST ALWAYS pin Biome configuration to the exact version schema (e.g., https://biomejs.dev/schemas/1.9.4/schema.json) in biome.json to guarantee deterministic rule validation across all environments. - Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root biome.json instead of duplicating ignore glob lists. - Engineers MUST ALWAYS format inline suppressions using the strict Biome 1.9 grammar `// biome-ignore lint/<group>/<rule>: <explanation>` and MUST NOT omit the explanation token. - Engineers MUST NOT rely on ESLint-style comments (e.g., `// eslint-disable-next-line` or `/* eslint-disable */`) or Biome suppressions without explicit rule target IDs. - Packages in a monorepo MUST inherit from the root configuration using `extends: ['../../biome.json']` rather than redefining global formatter and linter rules. ## Bad vs Good Implementations ### Root Biome 1.9 Configuration with VCS and Schema Pinning #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Missing `$schema` causes loss of IDE validation and config regression across versions. Duplicating .gitignore entries in `files.ignore` creates configuration drift and increases file traversal overhead. ```json { "files": { "ignore": ["node_modules/**", "dist/**", ".turbo/**", ".next/**"] }, "linter": { "enabled": true } } ``` #### Production Standard (Correct) > **Standard**: Includes exact schema validation, delegates ignore resolution directly to Git via native VCS integration, and defines unambiguous formatting boundaries. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "defaultBranch": "main" }, "linter": { "enabled": true, "rules": { "recommended": true } }, "formatter": { "enabled": true, "formatWithErrors": false, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 } } ``` ### Deterministic Rule Suppression Syntax #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Biome completely ignores ESLint pragmas, causing silent CI failures. The second line uses a Biome suppression but omits the mandatory explanation colon and justification, violating clean suppression grammar. ```typescript // eslint-disable-next-line @typescript-eslint/no-explicit-any export function deserializePayload(raw: string): any { // biome-ignore lint/suspicious/noExplicitAny const parsed = JSON.parse(raw) as any; return parsed; } ``` #### Production Standard (Correct) > **Standard**: Uses canonical Biome suppression syntax targeting the specific group and rule name, followed by an explicit architectural justification for why the rule is suppressed. ```typescript export function deserializePayload(raw: string): unknown { // biome-ignore lint/suspicious/noExplicitAny: Legacy wire contract requires untyped payload migration boundary const parsed: any = JSON.parse(raw); return parsed; } ```

Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configuration architecture across monorepos and isolated services. Mandates strict schema pinning, full VCS ignore delegation to avoid dual-configuration drift, and explicit, documented inline suppressions matching Biome's exact grammar. 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: Fragmented configs, redundant ignore files, and unannotated or ESLint-style rule suppressions. 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	Fragmented configs, redundant ignore files, and unannotated or ESLint-style rule suppressions.	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 pin Biome configuration to the exact version schema (e.g., https

Engineers MUST ALWAYS pin Biome configuration to the exact version schema (e.g., https://biomejs.dev/schemas/1.9.4/schema.json) in biome.json to guarantee deterministic rule validation across all environments.

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.