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-config-inheritance-suppression-standard

Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Standards

Enforces strict configuration inheritance, native Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Eliminates file-tree desynchronization between gitignore and Biome formatters while preventing undocumented or legacy ESLint suppressions.

Prohibited Anti-Pattern: Unanchored ESLint Suppressions, Missing Suppression Reasons, and Desynchronized Git Ignore Trees

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Standards - Enforces strict configuration inheritance, native Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Eliminates file-tree desynchronization between gitignore and Biome formatters while preventing undocumented or legacy ESLint suppressions.
globs: biome.json, biome.jsonc, **/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-config-inheritance-suppression-standard"
---

# Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Standards

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored ESLint Suppressions, Missing Suppression Reasons, and Desynchronized Git Ignore Trees

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 standards across enterprise TypeScript projects. You reject legacy ESLint/Prettier suppression pragmas, require explicit root and monorepo configuration inheritance with native VCS integration, and mandate rigorous, justification-backed Biome suppression directives.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in root `biome.json` to prevent divergence between Git tracking and formatting checks.
- Engineers MUST NOT use legacy ESLint (`// eslint-disable-next-line`) or Prettier (`// prettier-ignore`) suppression comments; all suppressions MUST utilize `// biome-ignore <group>/<rule>: <justification>` syntax.
- Suppression directives MUST ALWAYS provide an explanatory justification following the rule name and colon delimiter; bare `// biome-ignore <group>/<rule>` declarations are prohibited.
- Monorepo packages MUST use the `extends` array in sub-package `biome.json` to inherit from the root workspace or shared design tokens, overriding only path-specific needs via `overrides` arrays.
- CI pipelines and git hooks MUST utilize the `--changed` or `--since` VCS flags with Biome CLI commands (`biome check --write --changed`) to prevent full-repository scan latency while preserving formatting determinism.

## Bad vs Good Implementations
### Biome Configuration: VCS Integration and Schema Anchoring

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to declare VCS integration, manually duplicates .gitignore entries in files.ignore leading to drift, and omits the root extends contract and default branch specifications.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".next"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages native VCS resolution using .gitignore, establishes inherited monorepo presets via extends, and declares deterministic formatting invariants.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "extends": ["@acme/biome-config/base"],
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an ignored legacy ESLint comment that Biome will not honor, paired with an unjustified bare biome-ignore comment lacking the required rationale delimiter.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const raw: any = JSON.parse(input);
  return raw;
}
```

#### Production Standard (Correct)
> **Standard**: Employs valid Biome 1.9 suppression syntax adhering to the deterministic `// biome-ignore <group>/<rule>: <explanation>` specification with architectural justification.
```typescript
/**
 * Deserializes an untyped transport wire payload before runtime Zod validation.
 */
// biome-ignore lint/suspicious/noExplicitAny: Network boundary input requires top-level any prior to safeParse validation
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny: Internal parse intermediate awaiting boundary contract enforcement
  const raw: any = JSON.parse(input);
  return raw;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Diagnostics MCP
Executes high-throughput single-binary validation, config auditing, and formatting diagnostics across active project files.
Recommended Agent Skills (askills.dev)

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

Biome Single-Binary CLI Runner
Runs targeted Biome CI checks utilizing VCS delta flags (--changed, --since) and strict suppression validation.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance, native Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Eliminates file-tree desynchronization between gitignore and Biome formatters while preventing undocumented or legacy ESLint suppressions. 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 ESLint Suppressions, Missing Suppression Reasons, and Desynchronized Git Ignore Trees 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 ESLint Suppressions, Missing Suppression Reasons, and Desynchronized Git Ignore TreesCritical
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 divergence between Git tracking and formatting checks.

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 use legacy ESLint (`// eslint-disable-next-line`) or Prettier (`// prettier-ignore`) suppression comments

Engineers MUST NOT use legacy ESLint (`// eslint-disable-next-line`) or Prettier (`// prettier-ignore`) suppression comments; all suppressions MUST utilize `// biome-ignore <group>/<rule>: <justification>` syntax.

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

Suppression directives MUST ALWAYS provide an explanatory justification following the rule name and colon delimiter

Suppression directives MUST ALWAYS provide an explanatory justification following the rule name and colon delimiter; bare `// biome-ignore <group>/<rule>` declarations are prohibited.

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 use the `extends` array in sub-package `biome.json` to inherit from the root workspace or shared design tokens, overriding only path-specific needs via `overrides` arrays.

Monorepo packages MUST use the `extends` array in sub-package `biome.json` to inherit from the root workspace or shared design tokens, overriding only path-specific needs via `overrides` arrays.

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

CI pipelines and git hooks MUST utilize the `--changed` or `--since` VCS flags with Biome CLI commands (`biome check --write --changed`) to prevent full-repository scan latency while preserving formatting determinism.

CI pipelines and git hooks MUST utilize the `--changed` or `--since` VCS flags with Biome CLI commands (`biome check --write --changed`) to prevent full-repository scan latency while preserving formatting determinism.

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

Enforces strict configuration inheritance, native Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Eliminates file-tree desynchronization between gitignore and Biome formatters while preventing undocumented or legacy ESLint suppressions. 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 ESLint Suppressions, Missing Suppression Reasons, and Desynchronized Git Ignore Trees) 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