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-vcs-inheritance-suppression-standards

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance

Enforces deterministic Biome 1.9 configurations across single-repo and monorepo architectures. Mandates explicit VCS Git ignore inheritance, strict JSON schema validation, deterministic extends resolution, and audit-compliant rule suppression syntax requiring fully-qualified rule names and documented justifications.

Prohibited Anti-Pattern: Ad-Hoc File Globbing, Broken Git Ignore Inheritance, and Bare Rule Suppressions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance - Enforces deterministic Biome 1.9 configurations across single-repo and monorepo architectures. Mandates explicit VCS Git ignore inheritance, strict JSON schema validation, deterministic extends resolution, and audit-compliant rule suppression syntax requiring fully-qualified rule names and documented justifications.
globs: biome.json, biome.jsonc, **/biome.json, src/**/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-vcs-inheritance-suppression-standards"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-Hoc File Globbing, Broken Git Ignore Inheritance, and Bare Rule Suppressions

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 invariants across frontend codebases. Mandate deterministic configuration inheritance via relative paths, ensure VCS ignore integration (`vcs.useIgnoreFile: true`, `vcs.clientKind: 'git'`), and reject bare, unspecific, or reason-less `// biome-ignore` directives.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `$schema` key pointing to `https://biomejs.dev/schemas/1.9.0/schema.json` (or exact active patch version) at the root of `biome.json`.
- Engineers MUST ALWAYS set `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent scanning of build artifacts and ensure CLI parity with `.gitignore`.
- Engineers MUST NOT use unanchored or vague globs in `files.ignore` when `.gitignore` already handles artifact exclusion.
- Code MUST NEVER suppress diagnostics with bare comments; suppressions MUST strictly adhere to `// biome-ignore <category>/<rule>: <explanation>` or `// biome-ignore format: <explanation>`.
- Workspaces MUST inherit configuration using `extends: ["../../biome.json"]` with valid relative file paths; nested configurations MUST only override package-specific deviations.
- Engineers MUST NOT mix ESLint or Prettier suppression directives (`eslint-disable`, `prettier-ignore`) in projects migrated to Biome 1.9.

## Bad vs Good Implementations
### Biome Configuration: Root VCS Integration and Schema Anchoring

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` breaks IDE validation and migration tools. Missing `vcs` block causes Biome to ignore `.gitignore` by default, forcing manual maintenance of standard ignore patterns and causing CI divergence.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  },
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next"]
  }
}
```

#### Production Standard (Correct)
> **Standard**: Declares explicit schema version 1.9.0, binds Biome directly to Git tracking and ignore files, and provides consistent formatting/linter baselines without manual artifact blacklists.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Diagnostic Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: ESLint directives are ignored by Biome. Bare `// biome-ignore` is rejected by Biome 1.9's parser. Suppression without explanation lacks architectural justification and violates maintainability audits.
```typescript
// eslint-disable-next-line
const legacyToken: any = getStoredToken();

// biome-ignore
const payload: any = parseToken(legacyToken);

// biome-ignore lint/suspicious/noExplicitAny
function processRaw(data: any): void {
  console.log(data);
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly declares the lint group, rule ID, and a mandatory explanatory string documenting why the type escape hatch is required.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Required for third-party un-typed JWT handshake
const legacyToken: any = getStoredToken();

// biome-ignore lint/suspicious/noExplicitAny: Upstream deserializer returns arbitrary JSON schema
const payload: any = parseToken(legacyToken);

// biome-ignore lint/suspicious/noExplicitAny: Hardware event envelope delivers arbitrary dynamic payload
function processRaw(data: any): void {
  console.log(data);
}
```

### Monorepo Package Configuration Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Redefines global rules in a nested subpackage without extending the root configuration, leading to config drift across packages.
```json
{
  "linter": {
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Extends the monorepo root config deterministically via relative file path while declaring only package-specific deviations (e.g., legacy JSX runtime).
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "extends": ["../../biome.json"],
  "javascript": {
    "jsxRuntime": "reactClassic"
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP Server
Validates biome.json inheritance chains and verifies local directory structures against ignore rules.
Git MCP Server
Verifies Git ignore state and staged changes to ensure Biome VCS integration matches git tracked status.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --write --vcs-client-kind=git' to format, lint, and import-sort with native VCS support.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configurations across single-repo and monorepo architectures. Mandates explicit VCS Git ignore inheritance, strict JSON schema validation, deterministic extends resolution, and audit-compliant rule suppression syntax requiring fully-qualified rule names and documented justifications. 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 File Globbing, Broken Git Ignore Inheritance, and Bare 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAd-Hoc File Globbing, Broken Git Ignore Inheritance, and Bare Rule 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 the `$schema` key pointing to `https

Engineers MUST ALWAYS configure the `$schema` key pointing to `https://biomejs.dev/schemas/1.9.0/schema.json` (or exact active patch version) at the root of `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.
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 set `vcs.enabled

Engineers MUST ALWAYS set `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent scanning of build artifacts and ensure CLI parity with `.gitignore`.

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 NOT use unanchored or vague globs in `files.ignore` when `.gitignore` already handles artifact exclusion.

Engineers MUST NOT use unanchored or vague globs in `files.ignore` when `.gitignore` already handles artifact exclusion.

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 MUST NEVER suppress diagnostics with bare comments

Code MUST NEVER suppress diagnostics with bare comments; suppressions MUST strictly adhere to `// biome-ignore <category>/<rule>: <explanation>` or `// biome-ignore format: <explanation>`.

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

Workspaces MUST inherit configuration using `extends

Workspaces MUST inherit configuration using `extends: ["../../biome.json"]` with valid relative file paths; nested configurations MUST only override package-specific deviations.

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

Engineers MUST NOT mix ESLint or Prettier suppression directives (`eslint-disable`, `prettier-ignore`) in projects migrated to Biome 1.9.

Engineers MUST NOT mix ESLint or Prettier suppression directives (`eslint-disable`, `prettier-ignore`) in projects migrated to Biome 1.9.

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 Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance critical for AI coding assistants?

Enforces deterministic Biome 1.9 configurations across single-repo and monorepo architectures. Mandates explicit VCS Git ignore inheritance, strict JSON schema validation, deterministic extends resolution, and audit-compliant rule suppression syntax requiring fully-qualified rule names and documented justifications. 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 (Ad-Hoc File Globbing, Broken Git Ignore Inheritance, and Bare Rule 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

Biome