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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression Guardrail

Enforces deterministic configuration patterns in Biome 1.9+, mandating native VCS integration via git ignore files, explicit configuration inheritance overrides, and strictly reasoned inline rule suppressions. Prevents CI/CD drift caused by unversioned ignore lists, unreasoned disable comments, and fragmented toolchain execution.

Prohibited Anti-Pattern: Unanchored ignores, fragmented linter configurations, and unreasoned inline rule suppressions bypassing CI deterministic checks.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression Guardrail - Enforces deterministic configuration patterns in Biome 1.9+, mandating native VCS integration via git ignore files, explicit configuration inheritance overrides, and strictly reasoned inline rule suppressions. Prevents CI/CD drift caused by unversioned ignore lists, unreasoned disable comments, and fragmented toolchain execution.
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-vcs-config-deterministic-suppression-standard"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored ignores, fragmented linter configurations, and unreasoned inline rule suppressions bypassing CI deterministic checks.

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate strict adherence to single-binary orchestration, ensuring `vcs` git integration is enabled with `useIgnoreFile: true`, package-level configurations use deterministic `extends`, and all inline suppressions follow the canonical `// biome-ignore <group>/<rule>: <justification>` syntax. Reject legacy ESLint/Prettier comments, unreasoned suppressions, and duplicate ignore patterns across tools.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `vcs` block in the root `biome.json` with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent ignore-drift between git and Biome.
- Engineers MUST NOT maintain duplicate file exclusions across `.gitignore` and `biome.json` `files.ignore`; delegate general source-tree exclusions to `.gitignore` and reserve `files.ignore` strictly for toolchain-specific overrides.
- Engineers MUST ALWAYS provide an explicit, technical justification when using inline suppression comments, formatted strictly as `// biome-ignore <group>/<rule>: <explanation>`.
- Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `// @prettier-ignore`; Biome does not respect these by default and they clutter the codebase.
- Child packages in monorepos MUST explicitly extend the workspace base configuration using relative paths in the `extends` array (e.g., `"extends": ["../../biome.json"]`) and override only package-specific lint rules.
- CI pipelines MUST execute `biome ci` with `--diagnostic-level=error` to guarantee deterministic evaluation and zero tolerance for syntax, formatting, or lint failures.

## Bad vs Good Implementations
### Biome Configuration with VCS Integration and Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Redundantly duplicates standard git-ignored paths in `files.ignore` and lacks the `vcs` block, causing CI and local runs to diverge when handling untracked or ignored files.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enables native Git VCS integration so Biome natively respects `.gitignore`, uses the latest stable 1.9 schema, and ensures unknown file types are ignored safely.
```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,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Inline Rule Suppression vs Legacy Bypass

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: First suppression uses dead ESLint syntax which Biome ignores, generating a CI error. Second suppression lacks mandatory technical explanation, violating architectural auditability.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const untypedLegacyPayload: any = fetchPayload();

// biome-ignore lint/suspicious/noExplicitAny
const anotherPayload: any = fetchPayload();
```

#### Production Standard (Correct)
> **Standard**: Uses the canonical Biome 1.9 inline suppression syntax targeting the exact lint group and rule name, accompanied by a mandatory technical justification.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Downstream third-party SDK v1 schema is untyped; sanitized via parseSafePayload downstream
const untypedLegacyPayload: any = fetchPayload();
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Code Intelligence MCP
Executes real-time Biome AST linting, formatting checks, and rule documentation queries directly from agent contexts.
Recommended Agent Skills (askills.dev)

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

Biome 1.9 Single-Binary CLI Runner
Runs `biome check --write --diagnostic-level=error` for ultra-fast, deterministic multi-file linting, formatting, and import sorting.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Rule Suppression Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic configuration patterns in Biome 1.9+, mandating native VCS integration via git ignore files, explicit configuration inheritance overrides, and strictly reasoned inline rule suppressions. Prevents CI/CD drift caused by unversioned ignore lists, unreasoned disable comments, and fragmented toolchain execution. 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 ignores, fragmented linter configurations, and unreasoned inline rule suppressions bypassing CI deterministic checks. 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 ignores, fragmented linter configurations, and unreasoned inline rule suppressions bypassing CI deterministic checks.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 the `vcs` block in the root `biome.json` with `enabled

Engineers MUST ALWAYS configure the `vcs` block in the root `biome.json` with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent ignore-drift between git and 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.
2

Engineers MUST NOT maintain duplicate file exclusions across `.gitignore` and `biome.json` `files.ignore`

Engineers MUST NOT maintain duplicate file exclusions across `.gitignore` and `biome.json` `files.ignore`; delegate general source-tree exclusions to `.gitignore` and reserve `files.ignore` strictly for toolchain-specific 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.
3

Engineers MUST ALWAYS provide an explicit, technical justification when using inline suppression comments, formatted strictly as `// biome-ignore <group>/<rule>

Engineers MUST ALWAYS provide an explicit, technical justification when using inline suppression comments, formatted strictly as `// biome-ignore <group>/<rule>: <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 legacy comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `// @prettier-ignore`

Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// eslint-disable-next-line`, or `// @prettier-ignore`; Biome does not respect these by default and they clutter the codebase.

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

Child packages in monorepos MUST explicitly extend the workspace base configuration using relative paths in the `extends` array (e.g., `"extends"

Child packages in monorepos MUST explicitly extend the workspace base configuration using relative paths in the `extends` array (e.g., `"extends": ["../../biome.json"]`) and override only package-specific lint rules.

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 ci` with `--diagnostic-level=error` to guarantee deterministic evaluation and zero tolerance for syntax, formatting, or lint failures.

CI pipelines MUST execute `biome ci` with `--diagnostic-level=error` to guarantee deterministic evaluation and zero tolerance for syntax, formatting, or lint failures.

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

Enforces deterministic configuration patterns in Biome 1.9+, mandating native VCS integration via git ignore files, explicit configuration inheritance overrides, and strictly reasoned inline rule suppressions. Prevents CI/CD drift caused by unversioned ignore lists, unreasoned disable comments, and fragmented toolchain execution. 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 ignores, fragmented linter configurations, and unreasoned inline rule suppressions bypassing CI deterministic checks.) 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