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-standard

Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression

Enforces architectural standardization for Biome 1.9, mandating VCS-driven ignore synchronization, monorepo configuration inheritance via extends, and deterministic inline suppressions requiring explicit explanatory rationale. Prevents configuration drift, unignored vendor artifacts, and silent quality regressions.

Prohibited Anti-Pattern: Fragmented lint configurations with silent inline bypasses and desynchronized VCS ignore rules.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression - Enforces architectural standardization for Biome 1.9, mandating VCS-driven ignore synchronization, monorepo configuration inheritance via extends, and deterministic inline suppressions requiring explicit explanatory rationale. Prevents configuration drift, unignored vendor artifacts, and silent quality regressions.
globs: biome.json, biome.jsonc, apps/**/biome.json, packages/**/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-configuration-vcs-suppression-standard"
---

# Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented lint configurations with silent inline bypasses and desynchronized VCS ignore rules.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards across enterprise codebases. You must strictly enforce configuration inheritance through the extends field, absolute VCS integration parity via native gitignore ingestion, and deterministic suppression syntax where any rule bypass requires a canonical rule name followed by an explicit rationale.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `vcs` block in the root `biome.json` with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent ignore-rule drift between Git and Biome.
- Engineers MUST ALWAYS provide an explanatory justification in inline rule suppressions using the exact syntax `// biome-ignore <group>/<rule>: <explanation>`.
- Engineers MUST NOT emit generic rule group suppressions (e.g., `// biome-ignore lint`), file-wide unanchored suppressions, or legacy ESLint/Prettier suppression directives.
- Package-level configurations in monorepos MUST use `extends: ["../biome.json"]` or shared workspace packages instead of duplicating root-level rule, linter, or formatter settings.
- Workspaces MUST NEVER duplicate `.gitignore` paths into `files.ignore`; custom ignore patterns in `files.ignore` are reserved exclusively for non-VCS-tracked generated artifacts.

## Bad vs Good Implementations
### Inline Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses legacy ESLint directive ignored by Biome and provides a Biome suppression that lacks the mandatory colon and explanatory rationale, failing Biome 1.9 suppression integrity checks.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function parseDynamicWebhook(rawPayload: unknown): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const temp = rawPayload as any;
  return temp.data;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres to Biome 1.9 suppression syntax with full rule path (lint/suspicious/noExplicitAny) and an explicit explanatory rationale describing why the suppression is necessary.
```typescript
export function parseDynamicWebhook(rawPayload: unknown): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Dynamic untyped webhook payload requires cast prior to runtime schema validation
  const temp = rawPayload as any;
  return temp.data;
}
```

### Biome Root & Monorepo Sub-Package Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually replicates `.gitignore` entries in `files.ignore` without configuring native VCS integration, leading to drift when repository ignores change, and fails to enable client-aware git tracking.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", ".turbo", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enables native VCS integration to automatically inherit `.gitignore` rules, anchors default branch comparison for pre-commit checks, and establishes root formatting constraints.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/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
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git MCP Server
Validates VCS status, branches, and staged files aligned with Biome VCS configuration.
Recommended Agent Skills (askills.dev)

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

Biome CLI Orchestrator
Executes biome check, format, and lint commands with --staged and --changed flags for rapid verification.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression

Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces architectural standardization for Biome 1.9, mandating VCS-driven ignore synchronization, monorepo configuration inheritance via extends, and deterministic inline suppressions requiring explicit explanatory rationale. Prevents configuration drift, unignored vendor artifacts, and silent quality regressions. 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 lint configurations with silent inline bypasses and desynchronized VCS ignore rules. 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 DriftFragmented lint configurations with silent inline bypasses and desynchronized VCS ignore rules.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 configure the `vcs` block in the root `biome.json` with `enabled

Engineers MUST ALWAYS configure the `vcs` block in the root `biome.json` with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent ignore-rule drift between Git and 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 ALWAYS provide an explanatory justification in inline rule suppressions using the exact syntax `// biome-ignore <group>/<rule>

Engineers MUST ALWAYS provide an explanatory justification in inline rule suppressions using the exact syntax `// 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 emit generic rule group suppressions (e.g., `// biome-ignore lint`), file-wide unanchored suppressions, or legacy ESLint/Prettier suppression directives.

Engineers MUST NOT emit generic rule group suppressions (e.g., `// biome-ignore lint`), file-wide unanchored suppressions, or legacy ESLint/Prettier suppression 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

Package-level configurations in monorepos MUST use `extends

Package-level configurations in monorepos MUST use `extends: ["../biome.json"]` or shared workspace packages instead of duplicating root-level rule, linter, or formatter settings.

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 NEVER duplicate `.gitignore` paths into `files.ignore`

Workspaces MUST NEVER duplicate `.gitignore` paths into `files.ignore`; custom ignore patterns in `files.ignore` are reserved exclusively for non-VCS-tracked generated artifacts.

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 Unified Toolchain: Configuration Inheritance, VCS Synchronization, and Deterministic Suppression critical for AI coding assistants?

Enforces architectural standardization for Biome 1.9, mandating VCS-driven ignore synchronization, monorepo configuration inheritance via extends, and deterministic inline suppressions requiring explicit explanatory rationale. Prevents configuration drift, unignored vendor artifacts, and silent quality regressions. 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 (Fragmented lint configurations with silent inline bypasses and desynchronized VCS ignore rules.) 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