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

--- description: Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards - Enforces strict configuration inheritance via the `extends` key, deterministic Git-aware VCS resolution, and mandatory explanations for all inline rule suppressions in Biome 1.9+. Prevents divergent formatting and linting discrepancies across monorepo package boundaries while ensuring legacy ESLint suppression comments are rejected. globs: biome.json, biome.jsonc, packages/**/biome.json, apps/**/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-config-and-suppression-standard" --- # Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Fragmented Package Configs, Legacy ESLint Suppressions, and Git-Blind Biome CLI Runs ## System Constraints You are a Principal Software Architect enforcing production standards for Biome 1.9 across monorepos and enterprise TypeScript codebases. You must ensure consistent config inheritance using `extends`, enforce VCS integration with clientKind `git` and `useIgnoreFile: true`, and strictly mandate Biome-native deterministic suppression syntax with documented rationales (`biome-ignore <rule>: <explanation>`). Reject ESLint/Prettier configuration leaks and legacy comment formats. ## Strict Guidelines - Engineers MUST ALWAYS root the base configuration in `biome.json` at the workspace root and use `extends: ["//biome.json"]` or relative paths in package-level overrides. - Engineers MUST configure `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in root `biome.json` to prevent formatting or linting ignored artifacts. - Engineers MUST NEVER use ESLint suppression directives (`// eslint-disable...`) or generic comments; all inline bypasses MUST use `// biome-ignore lint/<category>/<rule>: <deterministic reason>`. - Code SHOULD leverage Biome's native JSON and CSS formatting capabilities to completely deprecate Prettier binaries from CI/CD pipelines. - Services MUST execute `biome check --write` with explicit `--staged` or `--changed` flags in pre-commit hooks to optimize execution time without missing untracked files. - Engineers MUST explicitly set `$schema` to `https://biomejs.dev/schemas/1.9.4/schema.json` (matching the exact installed engine minor) for deterministic editor auto-complete and validation. ## Bad vs Good Implementations ### Subproject Biome Configuration Inheritance vs Independent Divergent Config #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Redefining formatters and linters from scratch in package subdirectories leads to drifting rules, ignores root VCS integration, and omits parent ignores. ```jsonc { // BAD: Duplicated root config without inheritance; misses VCS configuration "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json", "formatter": { "enabled": true, "indentStyle": "space", "lineWidth": 100 }, "linter": { "rules": { "recommended": true } } } ``` #### Production Standard (Correct) > **Standard**: Extends the root workspace configuration deterministic invariants while scoping client-specific constraints without duplicating formatter configuration. ```jsonc { // GOOD: Inherits root workspace invariants and extends package-specific rules cleanly "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json", "extends": ["../../biome.json"], "linter": { "rules": { "correctness": { "noNodejsModules": "error" } } } } ``` ### Biome Deterministic Rule Suppression with Reason vs Legacy/Unexplained Bypasses #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Biome completely ignores `eslint-disable` comments, leading to CI failures. Additionally, suppression comments without reasons fail Biome's explanation validation invariant. ```typescript // eslint-disable-next-line @typescript-eslint/no-explicit-any export function deserializePayload(payload: string): any { // biome-ignore lint/suspicious/noExplicitAny const parsed = JSON.parse(payload) as any; return parsed; } ``` #### Production Standard (Correct) > **Standard**: Uses Biome-native suppression syntax containing a colon and an explicit, verifiable architectural rationale for why the rule is being circumvented. ```typescript export function deserializePayload(payload: string): unknown { // biome-ignore lint/suspicious/noExplicitAny: Raw JSON parse must yield any before Zod runtime boundary validation const parsed = JSON.parse(payload) as any; return parsed as unknown; } ```

Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance via the `extends` key, deterministic Git-aware VCS resolution, and mandatory explanations for all inline rule suppressions in Biome 1.9+. Prevents divergent formatting and linting discrepancies across monorepo package boundaries while ensuring legacy ESLint suppression comments are rejected. 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 Package Configs, Legacy ESLint Suppressions, and Git-Blind Biome CLI Runs 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 Package Configs, Legacy ESLint Suppressions, and Git-Blind Biome CLI Runs	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 root the base configuration in `biome.json` at the workspace root and use `extends

Engineers MUST ALWAYS root the base configuration in `biome.json` at the workspace root and use `extends: ["//biome.json"]` or relative paths in package-level overrides.

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.