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

Biome 1.9 Deterministic Configuration, VCS Sync, and Rule Suppression Guardrail

Enforces strict configuration inheritance across monorepo boundaries, automated Git VCS ignore synchronization, and fully-qualified rule suppression syntax in Biome 1.9. Prevents silent lint drifts, duplicated ignore rule maintenance, and unanchored comment suppressions that mask security vulnerabilities and regressions.

Prohibited Anti-Pattern: Unanchored Suppressions, Desynchronized Git Ignores, and Fractured Biome Configurations

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration, VCS Sync, and Rule Suppression Guardrail - Enforces strict configuration inheritance across monorepo boundaries, automated Git VCS ignore synchronization, and fully-qualified rule suppression syntax in Biome 1.9. Prevents silent lint drifts, duplicated ignore rule maintenance, and unanchored comment suppressions that mask security vulnerabilities and regressions.
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-guardrail"
---

# Biome 1.9 Deterministic Configuration, VCS Sync, and Rule Suppression Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored Suppressions, Desynchronized Git Ignores, and Fractured Biome Configurations

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 linting, formatting, and configuration standards. Reject legacy ESLint/Prettier suppression comments, unscoped Biome suppressions without justifications, fractured multi-root configurations lacking extends hierarchy, and manual ignore duplication where Biome VCS integration should be active.

## Strict Guidelines
- Engineers MUST ALWAYS configure VCS integration in root biome.jsonc using 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' to ensure .gitignore parity.
- Engineers MUST ALWAYS inherit package-level configurations from the monorepo root using the 'extends' array (e.g., 'extends': ["../../biome.jsonc"]).
- Engineers MUST ALWAYS format inline suppressions with fully-qualified rule names and mandatory human-readable justifications: '// biome-ignore <group>/<rule>: <mandatory explanation>'.
- Engineers MUST NOT use bare, unanchored suppressions (e.g., '// biome-ignore' or '// biome-ignore lint') lacking specific rule selectors and explanations.
- Engineers MUST NOT retain legacy lint directives ('// eslint-disable', '// tslint:disable', '// @prettier-ignore') in Biome-governed source trees.
- Overrides for specific file patterns MUST be strictly isolated within the 'overrides' array in biome.jsonc rather than distributed across fragmented ad-hoc configs.

## Bad vs Good Implementations
### Deterministic Biome Configuration Inheritance and VCS Binding

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually replicates ignore lists instead of integrating with Git VCS ignores, creating drift between repository tracking and linter execution while omitting strict schema inheritance.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", "coverage", ".next"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Extends the monorepo root configuration deterministically and leverages Biome 1.9 native VCS integration to automatically respect .gitignore rules without duplication.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.jsonc"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```

### Inline Rule Suppression with Mandatory Scoping and Explanation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses obsolete ESLint directives ignored by Biome and employs an unanchored '// biome-ignore lint' without specifying the exact rule path or actionable architectural justification.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(payload: string): any {
  // biome-ignore lint: need raw parsing here
  return JSON.parse(payload);
}
```

#### Production Standard (Correct)
> **Standard**: Uses fully-qualified Biome 1.9 suppression syntax ('lint/suspicious/noExplicitAny') paired with an explicit, traceable justification for the escape hatch.
```typescript
export function deserializePayload(payload: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Payload boundary schema validation occurs via Zod downstream (JIRA-892)
  return JSON.parse(payload) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Protocol MCP
Executes real-time Biome 1.9 diagnostics, format passes, and config schema validation directly inside AI agent contexts.
Recommended Agent Skills (askills.dev)

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

Biome CLI Standard Runner
Runs 'biome check --write' and 'biome ci' with native VCS change-tracking flags ('--changed', '--since').
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Deterministic Configuration, VCS Sync, and Rule Suppression Guardrail

Biome 1.9 Deterministic Configuration, VCS Sync, and Rule Suppression Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance across monorepo boundaries, automated Git VCS ignore synchronization, and fully-qualified rule suppression syntax in Biome 1.9. Prevents silent lint drifts, duplicated ignore rule maintenance, and unanchored comment suppressions that mask security vulnerabilities and 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: Unanchored Suppressions, Desynchronized Git Ignores, and Fractured 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 DriftUnanchored Suppressions, Desynchronized Git Ignores, and Fractured Biome ConfigurationsCritical
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 integration in root biome.jsonc using 'vcs.enabled

Engineers MUST ALWAYS configure VCS integration in root biome.jsonc using 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' to ensure .gitignore parity.

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 inherit package-level configurations from the monorepo root using the 'extends' array (e.g., 'extends'

Engineers MUST ALWAYS inherit package-level configurations from the monorepo root using the 'extends' array (e.g., 'extends': ["../../biome.jsonc"]).

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 ALWAYS format inline suppressions with fully-qualified rule names and mandatory human-readable justifications

Engineers MUST ALWAYS format inline suppressions with fully-qualified rule names and mandatory human-readable justifications: '// biome-ignore <group>/<rule>: <mandatory 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.
4

Engineers MUST NOT use bare, unanchored suppressions (e.g., '// biome-ignore' or '// biome-ignore lint') lacking specific rule selectors and explanations.

Engineers MUST NOT use bare, unanchored suppressions (e.g., '// biome-ignore' or '// biome-ignore lint') lacking specific rule selectors and explanations.

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

Engineers MUST NOT retain legacy lint directives ('// eslint-disable', '// tslint

Engineers MUST NOT retain legacy lint directives ('// eslint-disable', '// tslint:disable', '// @prettier-ignore') in Biome-governed source trees.

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

Overrides for specific file patterns MUST be strictly isolated within the 'overrides' array in biome.jsonc rather than distributed across fragmented ad-hoc configs.

Overrides for specific file patterns MUST be strictly isolated within the 'overrides' array in biome.jsonc rather than distributed across fragmented ad-hoc configs.

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, VCS Sync, and Rule Suppression Guardrail critical for AI coding assistants?

Enforces strict configuration inheritance across monorepo boundaries, automated Git VCS ignore synchronization, and fully-qualified rule suppression syntax in Biome 1.9. Prevents silent lint drifts, duplicated ignore rule maintenance, and unanchored comment suppressions that mask security vulnerabilities and 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 (Unanchored Suppressions, Desynchronized Git Ignores, and Fractured 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