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-1-9-config-vcs-suppression-guardrail

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

Standardizes Biome 1.9 adoption across enterprise codebases by enforcing native VCS ignore-file integration, deterministic configuration inheritance (`extends`), and strict, documented rule suppressions. Prevents configuration drift, eliminates duplicate ignore files, and forbids opaque rule bypasses.

Prohibited Anti-Pattern: Ghost Ignores, Divergent Package Configs, and Undocumented ESLint-Style Lint 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 Explicit Rule Suppression Standards - Standardizes Biome 1.9 adoption across enterprise codebases by enforcing native VCS ignore-file integration, deterministic configuration inheritance (`extends`), and strict, documented rule suppressions. Prevents configuration drift, eliminates duplicate ignore files, and forbids opaque rule bypasses.
globs: biome.json, biome.jsonc, **/*.ts, **/*.tsx, **/*.js, **/*.jsx, **/*.json
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-config-vcs-suppression-guardrail"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ghost Ignores, Divergent Package Configs, and Undocumented ESLint-Style Lint Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 as the authoritative single-binary formatter and linter. You must reject all ESLint/Prettier legacy comment directives, enforce root configuration inheritance across monorepo workspaces via `extends`, mandate `vcs.useIgnoreFile: true` with Git integration, and strictly require documented suppression comments (`// biome-ignore <category>/<rule>: <explanation>`).

## Strict Guidelines
- Engineers MUST configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent divergence between `.gitignore` and Biome's traversal pipeline.
- Engineers MUST extend root configurations in monorepo sub-packages using explicit relative paths (e.g., `"extends": ["../../biome.json"]`) to preserve workspace-wide parity while allowing scoped overrides.
- Engineers MUST use explicit, documented suppression comments matching `// biome-ignore <category>/<rule>: <explanation>` whenever suppressing diagnostics; unreasoned suppressions or ESLint directives (`// eslint-disable-next-line`) are strictly forbidden.
- Engineers MUST NOT maintain duplicate `.biomeignore` files when ignore patterns are already tracked by `.gitignore`.
- CI pipelines MUST execute `biome check --diagnostic-level=error` to block regressions, and CI commits MUST be formatted deterministically using identical Biome binary versions.

## Bad vs Good Implementations
### Biome Monorepo Configuration and VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure native VCS integration, causing manual, desynchronized maintenance of ignore lists between `.gitignore` and Biome. Missing monorepo schema inheritance references.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enables native Git VCS integration so `.gitignore` automatically dictates ignored files without manual duplication, and establishes explicit top-level formatting and linting standards.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": false
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax with Mandatory Explanation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses inert ESLint suppression comments that Biome ignores, and uses a Biome suppression comment that omits the mandatory colon-delimited explanation.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(input) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Employs the canonical Biome 1.9 suppression syntax (`// biome-ignore lint/<group>/<rule>: <rationale>`) containing an explicit explanation explaining why type safety was bypassed.
```typescript
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Legacy downstream contract requires dynamic shape before schema validation
  return JSON.parse(input) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server MCP
Provides programmatic access to real-time Biome AST linting, formatting, and diagnostic reports directly in the agent workspace.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes `biome check --write` and verifies configuration hierarchy across monorepo packages.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Standardizes Biome 1.9 adoption across enterprise codebases by enforcing native VCS ignore-file integration, deterministic configuration inheritance (`extends`), and strict, documented rule suppressions. Prevents configuration drift, eliminates duplicate ignore files, and forbids opaque rule 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: Ghost Ignores, Divergent Package Configs, and Undocumented ESLint-Style Lint 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 DriftGhost Ignores, Divergent Package Configs, and Undocumented ESLint-Style Lint 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 configure `vcs.enabled

Engineers MUST configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent divergence between `.gitignore` and Biome's traversal pipeline.

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 extend root configurations in monorepo sub-packages using explicit relative paths (e.g., `"extends"

Engineers MUST extend root configurations in monorepo sub-packages using explicit relative paths (e.g., `"extends": ["../../biome.json"]`) to preserve workspace-wide parity while allowing scoped 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.
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 explicit, documented suppression comments matching `// biome-ignore <category>/<rule>

Engineers MUST use explicit, documented suppression comments matching `// biome-ignore <category>/<rule>: <explanation>` whenever suppressing diagnostics; unreasoned suppressions or ESLint directives (`// eslint-disable-next-line`) are strictly forbidden.

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

Engineers MUST NOT maintain duplicate `.biomeignore` files when ignore patterns are already tracked by `.gitignore`.

Engineers MUST NOT maintain duplicate `.biomeignore` files when ignore patterns are already tracked by `.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.
5

CI pipelines MUST execute `biome check --diagnostic-level=error` to block regressions, and CI commits MUST be formatted deterministically using identical Biome binary versions.

CI pipelines MUST execute `biome check --diagnostic-level=error` to block regressions, and CI commits MUST be formatted deterministically using identical Biome binary versions.

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 Explicit Rule Suppression Standards critical for AI coding assistants?

Standardizes Biome 1.9 adoption across enterprise codebases by enforcing native VCS ignore-file integration, deterministic configuration inheritance (`extends`), and strict, documented rule suppressions. Prevents configuration drift, eliminates duplicate ignore files, and forbids opaque rule bypasses. 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 (Ghost Ignores, Divergent Package Configs, and Undocumented ESLint-Style Lint 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