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-v1-9-config-vcs-deterministic-suppression

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression

Enforces deterministic configuration inheritance, native Git VCS boundary synchronization, and strictly justified inline suppressions in Biome 1.9. Prevents CI pipeline failures, configuration drift in monorepos, and silent suppression rot caused by legacy ESLint comment patterns.

Prohibited Anti-Pattern: Applying Unjustified Legacy ESLint Suppressions and Misconfiguring Monorepo Biome VCS Inheritance

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression - Enforces deterministic configuration inheritance, native Git VCS boundary synchronization, and strictly justified inline suppressions in Biome 1.9. Prevents CI pipeline failures, configuration drift in monorepos, and silent suppression rot caused by legacy ESLint comment patterns.
globs: biome.json, biome.jsonc, src/**/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-v1-9-config-vcs-deterministic-suppression"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Applying Unjustified Legacy ESLint Suppressions and Misconfiguring Monorepo Biome VCS Inheritance

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 operational and architectural standards. You must strictly mandate Biome 1.9 configuration inheritance rules, ensure active VCS ignore propagation, and enforce deterministic, documented inline suppression syntax. Never emit or accept ESLint/Prettier suppression pragmas.

## Strict Guidelines
- Engineers MUST ALWAYS format inline suppressions using the exact Biome 1.9 deterministic syntax: `// biome-ignore <group>/<rule>: <mandatory explanatory reason>`.
- Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `/* prettier-ignore */` for Biome-managed files.
- Engineers MUST NOT provide empty, uninformative, or trivial suppression justifications; explanations must document why the exception is structurally safe.
- Configurations MUST explicitly enable the `vcs` object with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent formatting gitignored build artifacts.
- Monorepo packages MUST inherit root configuration deterministically using `"extends": ["//biome.json"]` or relative paths, overriding only package-scoped invariants via `overrides`.
- Biome rules SHOULD be configured with deterministic severity levels (`"error"` or `"warn"`) and NEVER rely on implicit defaults across inherited workspaces.

## Bad vs Good Implementations
### Deterministic Rule Suppression vs Legacy ESLint Comments

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Legacy ESLint suppression directives are completely ignored by Biome 1.9, causing lint failure. The bare biome-ignore without an explanation is rejected by standard `--suppressions-require-explanation` verification gates.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const legacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noImplicitAnyLet:
let uninitializedVar;

```

#### Production Standard (Correct)
> **Standard**: Explicit Biome 1.9 suppression syntax specifies the full group/rule identifier along with a mandatory, verifiable technical justification for bypassing the check.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External webhook payload schema is non-deterministic prior to Zod validation
const legacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noImplicitAnyLet: Variable is assigned via side-effect in legacy third-party loader callback below
let uninitializedVar;

```

### Biome 1.9 Monorepo Root Configuration with VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually duplicating .gitignore entries inside files.ignore leads to synchronization drift, and omitting VCS integration causes Biome to crawl ignored subtrees, drastically reducing CLI performance.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", "coverage"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages Biome 1.9 native VCS git client integration to automatically respect .gitignore definitions, avoiding duplicate ignore lists and ensuring fast, deterministic passes.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server MCP
Exposes real-time diagnostic AST inspections and formatting checks directly from the Biome 1.9 daemon.
Recommended Agent Skills (askills.dev)

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

Biome CLI Safe Check Runner
Executes `biome check --write --suppressions-require-explanation` across staged Git files for atomic pre-commit validation.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic configuration inheritance, native Git VCS boundary synchronization, and strictly justified inline suppressions in Biome 1.9. Prevents CI pipeline failures, configuration drift in monorepos, and silent suppression rot caused by legacy ESLint comment patterns. 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: Applying Unjustified Legacy ESLint Suppressions and Misconfiguring Monorepo Biome VCS Inheritance 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 DriftApplying Unjustified Legacy ESLint Suppressions and Misconfiguring Monorepo Biome VCS InheritanceCritical
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 format inline suppressions using the exact Biome 1.9 deterministic syntax

Engineers MUST ALWAYS format inline suppressions using the exact Biome 1.9 deterministic syntax: `// biome-ignore <group>/<rule>: <mandatory explanatory reason>`.

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 comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `/* prettier-ignore */` for Biome-managed files.

Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `/* prettier-ignore */` for Biome-managed files.

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 provide empty, uninformative, or trivial suppression justifications

Engineers MUST NOT provide empty, uninformative, or trivial suppression justifications; explanations must document why the exception is structurally safe.

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

Configurations MUST explicitly enable the `vcs` object with `enabled

Configurations MUST explicitly enable the `vcs` object with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent formatting gitignored build 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.
5

Monorepo packages MUST inherit root configuration deterministically using `"extends"

Monorepo packages MUST inherit root configuration deterministically using `"extends": ["//biome.json"]` or relative paths, overriding only package-scoped invariants via `overrides`.

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

Biome rules SHOULD be configured with deterministic severity levels (`"error"` or `"warn"`) and NEVER rely on implicit defaults across inherited workspaces.

Biome rules SHOULD be configured with deterministic severity levels (`"error"` or `"warn"`) and NEVER rely on implicit defaults across inherited workspaces.

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

Enforces deterministic configuration inheritance, native Git VCS boundary synchronization, and strictly justified inline suppressions in Biome 1.9. Prevents CI pipeline failures, configuration drift in monorepos, and silent suppression rot caused by legacy ESLint comment patterns. 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 (Applying Unjustified Legacy ESLint Suppressions and Misconfiguring Monorepo Biome VCS Inheritance) 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