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-19-config-vcs-suppression-standard

Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppression

Enforces strict Biome 1.9 configuration standards across single-repository and monorepo architectures by requiring explicit Git VCS synchronization and deterministic configuration inheritance. Mandates machine-checkable, documented rationale for every lint rule suppression comment while eliminating redundant Prettier and ESLint legacy directives.

Prohibited Anti-Pattern: Ad-hoc lint suppression without rationale, unlinked Git VCS ignore boundaries, and fragmented monolithic Biome configurations.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppression - Enforces strict Biome 1.9 configuration standards across single-repository and monorepo architectures by requiring explicit Git VCS synchronization and deterministic configuration inheritance. Mandates machine-checkable, documented rationale for every lint rule suppression comment while eliminating redundant Prettier and ESLint legacy directives.
globs: biome.json, biome.jsonc, apps/**/biome.json, packages/**/biome.json, src/**/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-19-config-vcs-suppression-standard"
---

# Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-hoc lint suppression without rationale, unlinked Git VCS ignore boundaries, and fragmented monolithic Biome configurations.

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Enforce root configuration inheritance via 'extends', native Git VCS integration to respect '.gitignore' boundaries, and strict '// biome-ignore <group>/<rule>: <explanation>' suppression syntax with mandatory justifications.

## Strict Guidelines
- Engineers MUST ALWAYS enable VCS integration in root 'biome.json' using '"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }' to ensure Git ignore boundaries are respected by Biome.
- Engineers MUST NOT disable rules inline without a mandatory, technical rationale following the colon delimiter: '// biome-ignore <group>/<rule>: <explanation>'.
- Engineers MUST NOT mix legacy ESLint or Prettier comments ('// eslint-disable-next-line', '// prettier-ignore'); these must be stripped or converted to native Biome directives.
- Workspace packages in a monorepo MUST inherit shared baseline configurations using the 'extends' property rather than redefining root formatting and linting rules.
- Configurations MUST define 'formatter.indentStyle', 'formatter.lineWidth', and 'organizeImports.enabled' explicitly to avoid drift across development and CI environments.
- CI pipelines MUST execute 'biome ci' with '--error-on-warnings' or deterministic branch-delta inspection using 'biome check --changed --since=origin/main'.

## Bad vs Good Implementations
### Biome 1.9 Configuration: Monorepo Package Inheritance and Git VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to declare VCS integration, causing Biome to scan untracked/ignored build artifacts unless manually specified. Missing 'extends' leads to config duplication in monorepos.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", "coverage"]
  },
  "formatter": {
    "enabled": true
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages configuration inheritance via 'extends', integrates directly with Git to respect .gitignore automatically, and guarantees deterministic formatting parameters.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "extends": ["../../biome.json"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "organizeImports": {
    "enabled": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Contains obsolete ESLint suppression comments and provides an unmotivated Biome suppression without the colon-delimited justification rationale required by Biome 1.9.
```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**: Eliminates legacy ESLint directives, limits scope, and utilizes fully qualified '// biome-ignore <group>/<rule>: <explanation>' syntax with an audit-ready technical justification.
```typescript
export function deserializePayload(raw: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: External legacy webhook schema is untyped at runtime; casting to any before validation boundary
  return JSON.parse(raw) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server
Language server protocol interface for Biome providing real-time diagnostic reporting and code actions.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
CLI automation skill to execute 'biome check --write' and 'biome ci' across target workspaces.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict Biome 1.9 configuration standards across single-repository and monorepo architectures by requiring explicit Git VCS synchronization and deterministic configuration inheritance. Mandates machine-checkable, documented rationale for every lint rule suppression comment while eliminating redundant Prettier and ESLint legacy directives. 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 lint suppression without rationale, unlinked Git VCS ignore boundaries, and fragmented monolithic Biome configurations. 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 lint suppression without rationale, unlinked Git VCS ignore boundaries, and fragmented monolithic Biome configurations.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 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 enable VCS integration in root 'biome.json' using '"vcs"

Engineers MUST ALWAYS enable VCS integration in root 'biome.json' using '"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }' to ensure Git ignore boundaries are respected by Biome.

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 NOT disable rules inline without a mandatory, technical rationale following the colon delimiter

Engineers MUST NOT disable rules inline without a mandatory, technical rationale following the colon delimiter: '// biome-ignore <group>/<rule>: <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.
3

Engineers MUST NOT mix legacy ESLint or Prettier comments ('// eslint-disable-next-line', '// prettier-ignore')

Engineers MUST NOT mix legacy ESLint or Prettier comments ('// eslint-disable-next-line', '// prettier-ignore'); these must be stripped or converted to native Biome directives.

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

Workspace packages in a monorepo MUST inherit shared baseline configurations using the 'extends' property rather than redefining root formatting and linting rules.

Workspace packages in a monorepo MUST inherit shared baseline configurations using the 'extends' property rather than redefining root formatting and linting rules.

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

Configurations MUST define 'formatter.indentStyle', 'formatter.lineWidth', and 'organizeImports.enabled' explicitly to avoid drift across development and CI environments.

Configurations MUST define 'formatter.indentStyle', 'formatter.lineWidth', and 'organizeImports.enabled' explicitly to avoid drift across development and CI environments.

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

CI pipelines MUST execute 'biome ci' with '--error-on-warnings' or deterministic branch-delta inspection using 'biome check --changed --since=origin/main'.

CI pipelines MUST execute 'biome ci' with '--error-on-warnings' or deterministic branch-delta inspection using 'biome check --changed --since=origin/main'.

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

Enforces strict Biome 1.9 configuration standards across single-repository and monorepo architectures by requiring explicit Git VCS synchronization and deterministic configuration inheritance. Mandates machine-checkable, documented rationale for every lint rule suppression comment while eliminating redundant Prettier and ESLint legacy directives. 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 lint suppression without rationale, unlinked Git VCS ignore boundaries, and fragmented monolithic Biome configurations.) 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