Deterministic Biome 1.9 Monorepo Configuration, VCS Scoping, and Suppression Invariants

--- description: Deterministic Biome 1.9 Monorepo Configuration, VCS Scoping, and Suppression Invariants - Enforces strict configuration inheritance patterns, Git VCS-aware file targeting, and deterministic inline suppression syntax in Biome 1.9. Prevents divergence between root workspace policies and leaf package overrides, eliminates untracked file linting churn, and mandates explanatory justification for all lint bypasses. globs: biome.json, biome.jsonc, apps/**/biome.json, packages/**/biome.json, **/*.{ts,tsx,js,jsx,json,jsonc} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/biome-1-9-monorepo-vcs-deterministic-suppression" --- # Deterministic Biome 1.9 Monorepo Configuration, VCS Scoping, and Suppression Invariants > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Ad-hoc ESLint-style suppressions, broken monorepo config inheritance, and CI-breaking untracked file formatting loops. ## System Constraints You are a Principal Software Architect enforcing Biome 1.9 Single-Binary Linter & Formatter invariants. You must mandate strict schema-validated configuration inheritance across monorepo packages, deterministic Git-aware VCS filtering, and syntactically valid Biome 1.9 inline suppressions with mandatory technical justifications. Reject deprecated configurations, legacy ESLint suppression comments, and unsanctioned override patterns. ## Strict Guidelines - Engineers MUST ALWAYS declare `$schema`: 'https://biomejs.dev/schemas/1.9.4/schema.json' at the top of every `biome.json` or `biome.jsonc` file. - Leaf packages in monorepos MUST use `extends: ["../../biome.json"]` (relative array pathing) rather than duplicating root formatter or linter rule dictionaries. - VCS integration MUST be explicitly configured at the root via `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` to prevent formatting ignored or transient artifacts. - Engineers MUST NOT use legacy comments like `// eslint-disable-next-line` or bare `// biome-ignore`; every suppression MUST follow the exact format `// biome-ignore <category>/<rule>: <explanation>`. - Overrides targeting specific file patterns MUST be encapsulated within the `overrides` array inside `biome.json`, rather than spawning standalone disjoint configuration files. - CI pipelines MUST run `biome check --diagnostic-level=error --error-on-warnings` when enforcing zero-debt thresholds. ## Bad vs Good Implementations ### Root vs Leaf Biome 1.9 Configuration with VCS Integration #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Uses an outdated schema, omits crucial Git VCS integration settings, uses the overly aggressive and unstable 'all: true' wildcard, and does not declare root-level configuration inheritance structure. ```json { "$schema": "https://biomejs.dev/schemas/1.8.0/schema.json", "formatter": { "enabled": true, "indentStyle": "space" }, "linter": { "rules": { "all": true } } } ``` #### Production Standard (Correct) > **Standard**: Explicitly declares Biome 1.9.4 schema, hooks into Git-native VCS exclusion behavior to honor .gitignore, and selectively defines rules based on the recommended preset. ```json { "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "defaultBranch": "main" }, "formatter": { "enabled": true, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 }, "linter": { "enabled": true, "rules": { "recommended": true, "correctness": { "noUnusedVariables": "error" } } } } ``` ### Deterministic Inline Lint Suppression Syntax #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Employs an unsupported ESLint suppression directive, followed by a naked Biome suppression comment lacking an explanation, which fails Biome's strict lint audits. ```typescript // eslint-disable-next-line @typescript-eslint/no-explicit-any export function deserializePayload(raw: string): any { // biome-ignore lint/suspicious/noExplicitAny return JSON.parse(raw) as any; } ``` #### Production Standard (Correct) > **Standard**: Adheres to the Biome 1.9 suppression standard `biome-ignore <category>/<rule>: <explanation>`, providing full traceability and preventing suppression regression. ```typescript // biome-ignore lint/suspicious/noExplicitAny: External payload schema is strictly validated downstream via Zod safeParse export function deserializePayload(raw: string): any { // biome-ignore lint/suspicious/noExplicitAny: Dynamic deserialization boundary required for generic parsing return JSON.parse(raw) as any; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Biome 1.9 Monorepo Configuration, VCS Scoping, and Suppression Invariants

Deterministic Biome 1.9 Monorepo Configuration, VCS Scoping, and Suppression Invariants defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance patterns, Git VCS-aware file targeting, and deterministic inline suppression syntax in Biome 1.9. Prevents divergence between root workspace policies and leaf package overrides, eliminates untracked file linting churn, and mandates explanatory justification for all lint bypasses. 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-style suppressions, broken monorepo config inheritance, and CI-breaking untracked file formatting loops. 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-style suppressions, broken monorepo config inheritance, and CI-breaking untracked file formatting loops.	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 declare `$schema`

Engineers MUST ALWAYS declare `$schema`: 'https://biomejs.dev/schemas/1.9.4/schema.json' at the top of every `biome.json` or `biome.jsonc` file.

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.