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

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

Enforces deterministic standards for Biome 1.9+ setups across modern frontend codebases and monorepos. Mandates active Git VCS integration with ignorefile synchronization, schema-validated config inheritance via 'extends', and strictly documented inline suppressions requiring explicit rule names and actionable explanations.

Prohibited Anti-Pattern: Unsynchronized Git ignores, duplicated monorepo configurations, and unanchored or reasonless inline 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 Strict Suppression Governance - Enforces deterministic standards for Biome 1.9+ setups across modern frontend codebases and monorepos. Mandates active Git VCS integration with ignorefile synchronization, schema-validated config inheritance via 'extends', and strictly documented inline suppressions requiring explicit rule names and actionable explanations.
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-1-9-vcs-inheritance-suppression-standards"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unsynchronized Git ignores, duplicated monorepo configurations, and unanchored or reasonless inline suppressions.

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate strict schema validation, VCS-aware traversal via vcs.useIgnoreFile, deterministic monorepo configuration inheritance, and zero-tolerance for unanchored or reasonless inline rule suppressions.

## Strict Guidelines
- Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root biome.json to prevent parsing binaries, build outputs, and Git-ignored paths.
- Engineers MUST ALWAYS provide an explicit rule name and reason when silencing diagnostics using the exact syntax '// biome-ignore <group>/<rule>: <technical justification>'.
- Engineers MUST NOT use unanchored suppressions ('// biome-ignore' without rule name) or empty reasons.
- Monorepo packages MUST inherit shared configurations using the 'extends' array (e.g., '"extends": ["//biome.json"]' or relative paths) rather than duplicating root rule dictionaries.
- Configurations MUST pin '$schema' to the matching 1.9.x release (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to guarantee deterministic agent and IDE validation.
- Engineers MUST eliminate obsolete ESLint, Prettier, or TSLint suppression comments ('/* eslint-disable */', '// prettier-ignore') across files managed by Biome.

## Bad vs Good Implementations
### Root and Workspace Configuration with VCS Integration and Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing $schema declaration, no VCS awareness (causes Biome to traverse node_modules, build directories, or generated files unless manually duplicated in files.ignore), and no deterministic configuration inheritance pattern.
```json
{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space"
  }
}
```

#### Production Standard (Correct)
> **Standard**: Includes pinned $schema, activates Git-aware file resolution to honor .gitignore automatically, ignores unknown file types, and configures explicit linter and formatter boundaries.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Mixes legacy ESLint directives with an unanchored '// biome-ignore' lacking both the targeted rule identity and a mandatory explanatory reason.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(payload: string): any {
  // biome-ignore
  return JSON.parse(payload);
}
```

#### Production Standard (Correct)
> **Standard**: Eliminates legacy directives and implements compliant Biome 1.9 suppression specifying the exact rule domain and a mandatory technical justification.
```typescript
export function deserializePayload(payload: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: External boundary requires untyped dynamic JSON deserialization before Zod validation
  return JSON.parse(payload) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP
Inspects and manages biome.json, biome.jsonc, and .gitignore structures directly in project workspaces.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --write' and 'biome ci' to enforce formatting, linting, and import sorting deterministically.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Suppression Governance defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic standards for Biome 1.9+ setups across modern frontend codebases and monorepos. Mandates active Git VCS integration with ignorefile synchronization, schema-validated config inheritance via 'extends', and strictly documented inline suppressions requiring explicit rule names and actionable explanations. 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: Unsynchronized Git ignores, duplicated monorepo configurations, and unanchored or reasonless inline 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 DriftUnsynchronized Git ignores, duplicated monorepo configurations, and unanchored or reasonless inline suppressions.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 'vcs.enabled

Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root biome.json to prevent parsing binaries, build outputs, and Git-ignored paths.

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 explicit rule name and reason when silencing diagnostics using the exact syntax '// biome-ignore <group>/<rule>

Engineers MUST ALWAYS provide an explicit rule name and reason when silencing diagnostics using the exact syntax '// biome-ignore <group>/<rule>: <technical justification>'.

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 suppressions ('// biome-ignore' without rule name) or empty reasons.

Engineers MUST NOT use unanchored suppressions ('// biome-ignore' without rule name) or empty reasons.

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

Monorepo packages MUST inherit shared configurations using the 'extends' array (e.g., '"extends"

Monorepo packages MUST inherit shared configurations using the 'extends' array (e.g., '"extends": ["//biome.json"]' or relative paths) rather than duplicating root rule dictionaries.

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 pin '$schema' to the matching 1.9.x release (e.g., 'https

Configurations MUST pin '$schema' to the matching 1.9.x release (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to guarantee deterministic agent and IDE validation.

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 eliminate obsolete ESLint, Prettier, or TSLint suppression comments ('/* eslint-disable */', '// prettier-ignore') across files managed by Biome.

Engineers MUST eliminate obsolete ESLint, Prettier, or TSLint suppression comments ('/* eslint-disable */', '// prettier-ignore') across files managed 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.
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 Strict Suppression Governance critical for AI coding assistants?

Enforces deterministic standards for Biome 1.9+ setups across modern frontend codebases and monorepos. Mandates active Git VCS integration with ignorefile synchronization, schema-validated config inheritance via 'extends', and strictly documented inline suppressions requiring explicit rule names and actionable explanations. 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 (Unsynchronized Git ignores, duplicated monorepo configurations, and unanchored or reasonless inline 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