AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: biome-configuration-vcs-suppression-guardrail

Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression

Enforces strict configuration architecture, deterministic VCS integration, and explanatory suppression syntax for Biome 1.9 in enterprise monorepos. Mandates the use of Biome's native VCS ignore resolution to eliminate drift between Git and Biome, enforces structured suppression syntax with mandatory human-readable justifications, and standardizes configuration inheritance across package boundaries.

Prohibited Anti-Pattern: Leaking Legacy ESLint Suppressions, Bypassing VCS Ignore Synchronization, and Using Unjustified Biome Suppressions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression - Enforces strict configuration architecture, deterministic VCS integration, and explanatory suppression syntax for Biome 1.9 in enterprise monorepos. Mandates the use of Biome's native VCS ignore resolution to eliminate drift between Git and Biome, enforces structured suppression syntax with mandatory human-readable justifications, and standardizes configuration inheritance across package boundaries.
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-configuration-vcs-suppression-guardrail"
---

# Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Legacy ESLint Suppressions, Bypassing VCS Ignore Synchronization, and Using Unjustified Biome Suppressions

## System Constraints
You are a Principal Software Architect enforcing enterprise-grade Biome 1.9 standards. Enforce strict configuration inheritance, native VCS gitignore resolution, and deterministic, fully documented suppression syntax across all frontend repositories. Reject any legacy ESLint/Prettier suppression comments or unjustified biome-ignore pragmas.

## Strict Guidelines
- Engineers MUST ALWAYS configure VCS integration in root biome.json using 'vcs': { 'enabled': true, 'clientKind': 'git', 'useIgnoreFile': true } instead of manually duplicating .gitignore patterns into 'files.ignore'.
- Engineers MUST ALWAYS supply an explicit explanation when applying suppressions using the format: '// biome-ignore <category>/<rule>: <explanation>'. Unexplained suppressions or legacy ESLint/Prettier comment pragmas (e.g., eslint-disable-next-line) MUST NOT be committed.
- Engineers MUST use the 'extends' array in nested workspace package configurations to inherit root biome.json presets rather than duplicating root rule matrices.
- Code SHOULD leverage Biome's top-level 'organizeImports.enabled: true' to ensure deterministic import sorting across all supported TypeScript/JavaScript targets.
- Overrides within biome.json MUST target specific file globs using the 'overrides' array rather than scattering unanchored suppression comments across source code.
- Workspaces MUST NOT maintain conflicting formatter configurations across monorepo packages; indentStyle, lineWidth, and quoteStyle MUST be unified in the base configuration.

## Bad vs Good Implementations
### Biome Configuration: Root VCS Integration & Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually duplicating .gitignore entries into files.ignore leads to synchronization drift, misses newly ignored build artifacts, and bypasses native git-aware resolution introduced in modern Biome releases.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", ".next", "coverage", "build"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Delegates ignore resolution to Git via vcs.useIgnoreFile, enables deterministic import sorting, and establishes a single source of truth for repository hygiene.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "organizeImports": {
    "enabled": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Legacy ESLint comments have zero effect in Biome and create technical debt. Bare '// biome-ignore' without an explanation fails deterministic audit standards and hides the architectural rationale for rule bypasses.
```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**: Eliminates dead ESLint comments and satisfies Biome 1.9 strict suppression requirements by appending an explicit colon-delimited architectural justification.
```typescript
export function deserializePayload(raw: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Upstream RPC schema v1 returns untyped polymorphic payload
  const parsed = JSON.parse(raw) as any;
  return parsed;
}
```

### Monorepo Package Configuration Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Redefining isolated formatting rules in subpackages without extending the root biome.json causes monorepo formatting conflicts, inconsistent diffs, and broken CI validation.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "formatter": {
    "enabled": true,
    "indentStyle": "tab",
    "lineWidth": 120
  }
}
```

#### Production Standard (Correct)
> **Standard**: Inherits base formatting and linting definitions via 'extends' and confines package-specific relaxations strictly to deterministic glob-based overrides.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.json"],
  "overrides": [
    {
      "include": ["src/legacy/**/*.ts"],
      "linter": {
        "rules": {
          "suspicious": {
            "noExplicitAny": "warn"
          }
        }
      }
    }
  ]
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Biome Language Server Protocol MCP
Provides instant diagnostic feedback, autofix capabilities, and AST-level rule inspection via the official Biome single-binary CLI engine.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Biome CLI Orchestrator
Executes 'biome check --write --staged' and validates configuration inheritance across multi-package workspaces with zero external node dependencies.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression

Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration architecture, deterministic VCS integration, and explanatory suppression syntax for Biome 1.9 in enterprise monorepos. Mandates the use of Biome's native VCS ignore resolution to eliminate drift between Git and Biome, enforces structured suppression syntax with mandatory human-readable justifications, and standardizes configuration inheritance across package boundaries. 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: Leaking Legacy ESLint Suppressions, Bypassing VCS Ignore Synchronization, and Using Unjustified Biome 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftLeaking Legacy ESLint Suppressions, Bypassing VCS Ignore Synchronization, and Using Unjustified Biome SuppressionsCritical
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 InconsistencyAI 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:

1

Engineers MUST ALWAYS configure VCS integration in root biome.json using 'vcs'

Engineers MUST ALWAYS configure VCS integration in root biome.json using 'vcs': { 'enabled': true, 'clientKind': 'git', 'useIgnoreFile': true } instead of manually duplicating .gitignore patterns into 'files.ignore'.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST ALWAYS supply an explicit explanation when applying suppressions using the format

Engineers MUST ALWAYS supply an explicit explanation when applying suppressions using the format: '// biome-ignore <category>/<rule>: <explanation>'. Unexplained suppressions or legacy ESLint/Prettier comment pragmas (e.g., eslint-disable-next-line) MUST NOT be committed.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST use the 'extends' array in nested workspace package configurations to inherit root biome.json presets rather than duplicating root rule matrices.

Engineers MUST use the 'extends' array in nested workspace package configurations to inherit root biome.json presets rather than duplicating root rule matrices.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Code SHOULD leverage Biome's top-level 'organizeImports.enabled

Code SHOULD leverage Biome's top-level 'organizeImports.enabled: true' to ensure deterministic import sorting across all supported TypeScript/JavaScript targets.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Overrides within biome.json MUST target specific file globs using the 'overrides' array rather than scattering unanchored suppression comments across source code.

Overrides within biome.json MUST target specific file globs using the 'overrides' array rather than scattering unanchored suppression comments across source code.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Workspaces MUST NOT maintain conflicting formatter configurations across monorepo packages

Workspaces MUST NOT maintain conflicting formatter configurations across monorepo packages; indentStyle, lineWidth, and quoteStyle MUST be unified in the base configuration.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Rule Suppression critical for AI coding assistants?

Enforces strict configuration architecture, deterministic VCS integration, and explanatory suppression syntax for Biome 1.9 in enterprise monorepos. Mandates the use of Biome's native VCS ignore resolution to eliminate drift between Git and Biome, enforces structured suppression syntax with mandatory human-readable justifications, and standardizes configuration inheritance across package boundaries. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Leaking Legacy ESLint Suppressions, Bypassing VCS Ignore Synchronization, and Using Unjustified Biome Suppressions) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Deterministic