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-config-inheritance-vcs-suppression-guardrails

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

Enforces deterministic formatting and linting architecture using Biome 1.9 single-binary capabilities. Mandates explicit configuration inheritance, native Git VCS ignore binding to eliminate duplicate ignore lists, and strictly formatted rule suppression syntax with mandatory contextual justification.

Prohibited Anti-Pattern: Fragmented Toolchain Configuration, Ignored VCS Boundaries, and Naked Rule Suppressions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Integration, and Deterministic Suppression - Enforces deterministic formatting and linting architecture using Biome 1.9 single-binary capabilities. Mandates explicit configuration inheritance, native Git VCS ignore binding to eliminate duplicate ignore lists, and strictly formatted rule suppression syntax with mandatory contextual justification.
globs: biome.json, biome.jsonc, **/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-config-inheritance-vcs-suppression-guardrails"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented Toolchain Configuration, Ignored VCS Boundaries, and Naked Rule Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards across enterprise TypeScript/JavaScript repositories. Mandate single-source-of-truth configuration via 'extends', native Git VCS integration to prevent ignore drift, and deterministic suppression syntax containing explicit reasons. Disallow legacy ESLint/Prettier suppressions and untyped lint suppressions.

## Strict Guidelines
- Engineers MUST ALWAYS configure Biome's VCS block ('vcs.enabled: true', 'vcs.clientKind: "git"', 'vcs.useIgnoreFile: true') in 'biome.json' rather than manually duplicating '.gitignore' globs into 'files.ignore'.
- Engineers MUST ALWAYS use valid Biome suppression syntax: '// biome-ignore <group>/<rule>: <explanation>' directly preceding the offending AST node.
- Engineers MUST NOT use legacy comments like '// eslint-disable-next-line', '// @ts-ignore', or bare '// biome-ignore' without specifying the exact rule name and a non-empty human rationale.
- Root configurations MUST declare explicitly bounded 'extends' paths for monorepo workspaces and shared preset packages.
- Workspaces MUST configure 'organizeImports.enabled: true' and 'formatter.enabled: true' to ensure single-pass deterministic processing without external AST transforms.
- CI pipelines MUST execute 'biome check --changed --since=origin/main' for rapid delta analysis using Biome's native VCS engine.

## Bad vs Good Implementations
### Biome Configuration: Monorepo Inheritance and Native VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually defines redundant file ignore lists that desynchronize from '.gitignore' and omits VCS integration and configuration inheritance standards.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", ".next", "coverage", "build"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Inherits baseline configuration from a shared preset, hooks directly into Git to read '.gitignore', and guarantees unified multi-file AST passes.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "extends": ["@company/biome-config/base"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "organizeImports": {
    "enabled": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Rule Suppression Syntax: Deterministic vs Deprecated Suppressions

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an unparsed legacy ESLint comment that Biome ignores, alongside a naked Biome suppression missing the mandatory human explanation.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(raw: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const temp: any = JSON.parse(raw);
  return temp;
}
```

#### Production Standard (Correct)
> **Standard**: Employs strictly formatted Biome suppression syntax with rule identifier and mandatory rationale, scoped immediately above the target node.
```typescript
/**
 * Deserializes raw vendor response before schema validation.
 */
export function deserializePayload(raw: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Third-party payload schema is dynamic prior to Zod parse step
  const temp: any = JSON.parse(raw);
  return temp;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Diagnostics MCP
Exposes Biome LSP diagnostics, formatting triggers, and safe auto-fix command integration directly to AI agents.
Recommended Agent Skills (askills.dev)

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

Biome CLI Execution
Invokes 'biome check --write' and 'biome ci' against staged and modified repository files.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Unified Toolchain: Configuration Inheritance, VCS Integration, and Deterministic Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic formatting and linting architecture using Biome 1.9 single-binary capabilities. Mandates explicit configuration inheritance, native Git VCS ignore binding to eliminate duplicate ignore lists, and strictly formatted rule suppression syntax with mandatory contextual justification. 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 Toolchain Configuration, Ignored VCS Boundaries, and Naked 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 DriftFragmented Toolchain Configuration, Ignored VCS Boundaries, and Naked 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 Biome's VCS block ('vcs.enabled

Engineers MUST ALWAYS configure Biome's VCS block ('vcs.enabled: true', 'vcs.clientKind: "git"', 'vcs.useIgnoreFile: true') in 'biome.json' rather than manually duplicating '.gitignore' globs 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 use valid Biome suppression syntax

Engineers MUST ALWAYS use valid Biome suppression syntax: '// biome-ignore <group>/<rule>: <explanation>' directly preceding the offending AST node.

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 legacy comments like '// eslint-disable-next-line', '// @ts-ignore', or bare '// biome-ignore' without specifying the exact rule name and a non-empty human rationale.

Engineers MUST NOT use legacy comments like '// eslint-disable-next-line', '// @ts-ignore', or bare '// biome-ignore' without specifying the exact rule name and a non-empty human rationale.

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

Root configurations MUST declare explicitly bounded 'extends' paths for monorepo workspaces and shared preset packages.

Root configurations MUST declare explicitly bounded 'extends' paths for monorepo workspaces and shared preset packages.

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 configure 'organizeImports.enabled

Workspaces MUST configure 'organizeImports.enabled: true' and 'formatter.enabled: true' to ensure single-pass deterministic processing without external AST transforms.

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 check --changed --since=origin/main' for rapid delta analysis using Biome's native VCS engine.

CI pipelines MUST execute 'biome check --changed --since=origin/main' for rapid delta analysis using Biome's native VCS engine.

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

Enforces deterministic formatting and linting architecture using Biome 1.9 single-binary capabilities. Mandates explicit configuration inheritance, native Git VCS ignore binding to eliminate duplicate ignore lists, and strictly formatted rule suppression syntax with mandatory contextual justification. 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 Toolchain Configuration, Ignored VCS Boundaries, and Naked 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