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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance

Enforces deterministic Biome 1.9 configuration architecture utilizing native Git VCS ignore integration, monorepo config inheritance, and mandatory reasoned comment suppressions. Prevents untracked file pollution, rogue ignores, and configuration drift between local developer environments and CI pipelines.

Prohibited Anti-Pattern: Unpinned Biome configurations omitting VCS ignore synchronization, legacy ESLint directives, and unreasoned rule 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 Suppression Governance - Enforces deterministic Biome 1.9 configuration architecture utilizing native Git VCS ignore integration, monorepo config inheritance, and mandatory reasoned comment suppressions. Prevents untracked file pollution, rogue ignores, and configuration drift between local developer environments and CI pipelines.
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-config-vcs-suppression-standards"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unpinned Biome configurations omitting VCS ignore synchronization, legacy ESLint directives, and unreasoned rule suppressions.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 toolchain standards across the repository. Mandate strict schema validation, deterministic VCS-backed ignore policies, and standardized rule suppressions containing mandatory human rationale.

## Strict Guidelines
- Engineers MUST ALWAYS enable VCS integration in `biome.json` (`vcs.enabled: true`, `vcs.clientKind: "git"`, `vcs.useIgnoreFile: true`) to prevent formatting generated assets or binary artifacts.
- Engineers MUST ALWAYS provide an explicit, audit-compliant justification matching `// biome-ignore lint/<group>/<rule>: <rationale>` when suppressing diagnostics.
- Engineers MUST NOT use legacy ESLint (`/* eslint-disable */`) or Prettier (`// prettier-ignore`) comments, as Biome will not honor them and flags them as uninspected dead directives.
- Engineers MUST declare monorepo inheritance using the `extends` property pointing to explicit workspace configurations rather than duplicating linter and formatter rule objects across packages.
- CI pipelines MUST execute `biome ci --error-on-warnings` to ensure deterministic validation passes before merging.

## Bad vs Good Implementations
### Biome In-Source Rule Suppression with Mandatory Rationale

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Legacy ESLint comments are ignored by Biome 1.9, causing runtime lint failures. The Biome ignore directive lacks the mandatory colon and explanatory rationale, violating clean suppression standards.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializeData(payload: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const temp: any = JSON.parse(payload);
  return temp;
}
```

#### Production Standard (Correct)
> **Standard**: Uses the compliant Biome 1.9 suppression format specifying the category, rule name, and an explicit, verifiable explanation string after a colon delimiter.
```typescript
export function deserializeData(payload: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Third-party payload schema is dynamic and validated downstream via Zod safeParse
  const temp: any = JSON.parse(payload);
  return temp;
}
```

### Deterministic Biome 1.9 Root Configuration (`biome.json`)

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Relies on manual file ignores without VCS binding, causing discrepancy with .gitignore, omitting strict linting levels and schema pins.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "coverage"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages Biome's native VCS engine to inherit .gitignore rules deterministically, suppresses unknown file parsing errors, and explicitly configures core formatting invariants.
```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,
      "suspicious": {
        "noExplicitAny": "warn"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP Server
Enables direct inspection of biome.json and workspace root config files for structural verification.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Command-line integration executing `biome check --write` and `biome ci` for deterministic formatting and linting validation.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configuration architecture utilizing native Git VCS ignore integration, monorepo config inheritance, and mandatory reasoned comment suppressions. Prevents untracked file pollution, rogue ignores, and configuration drift between local developer environments and CI pipelines. 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: Unpinned Biome configurations omitting VCS ignore synchronization, legacy ESLint directives, and unreasoned rule 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 DriftUnpinned Biome configurations omitting VCS ignore synchronization, legacy ESLint directives, and unreasoned rule 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 enable VCS integration in `biome.json` (`vcs.enabled

Engineers MUST ALWAYS enable VCS integration in `biome.json` (`vcs.enabled: true`, `vcs.clientKind: "git"`, `vcs.useIgnoreFile: true`) to prevent formatting generated assets or binary 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.
2

Engineers MUST ALWAYS provide an explicit, audit-compliant justification matching `// biome-ignore lint/<group>/<rule>

Engineers MUST ALWAYS provide an explicit, audit-compliant justification matching `// biome-ignore lint/<group>/<rule>: <rationale>` when suppressing diagnostics.

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 legacy ESLint (`/* eslint-disable */`) or Prettier (`// prettier-ignore`) comments, as Biome will not honor them and flags them as uninspected dead directives.

Engineers MUST NOT use legacy ESLint (`/* eslint-disable */`) or Prettier (`// prettier-ignore`) comments, as Biome will not honor them and flags them as uninspected dead directives.

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 declare monorepo inheritance using the `extends` property pointing to explicit workspace configurations rather than duplicating linter and formatter rule objects across packages.

Engineers MUST declare monorepo inheritance using the `extends` property pointing to explicit workspace configurations rather than duplicating linter and formatter rule objects across packages.

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 MUST execute `biome ci --error-on-warnings` to ensure deterministic validation passes before merging.

CI pipelines MUST execute `biome ci --error-on-warnings` to ensure deterministic validation passes before merging.

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

Enforces deterministic Biome 1.9 configuration architecture utilizing native Git VCS ignore integration, monorepo config inheritance, and mandatory reasoned comment suppressions. Prevents untracked file pollution, rogue ignores, and configuration drift between local developer environments and CI pipelines. 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 (Unpinned Biome configurations omitting VCS ignore synchronization, legacy ESLint directives, and unreasoned rule 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