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-inheritance-suppression-guardrails

Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Protocol

Mandates deterministic single-binary linting and formatting via Biome 1.9 configuration standards. Enforces native VCS ignore file inheritance, strict JSON schema validation, and structured inline suppression syntax with mandatory explanations to eliminate configuration drift and unvetted rule bypasses.

Prohibited Anti-Pattern: Unanchored Biome Configuration, Redundant Ignore Lists, and Unexplained Suppression Comments

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 Protocol - Mandates deterministic single-binary linting and formatting via Biome 1.9 configuration standards. Enforces native VCS ignore file inheritance, strict JSON schema validation, and structured inline suppression syntax with mandatory explanations to eliminate configuration drift and unvetted rule bypasses.
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-vcs-inheritance-suppression-guardrails"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored Biome Configuration, Redundant Ignore Lists, and Unexplained Suppression Comments

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate invariant configuration inheritance, automated VCS ignore resolution, and deterministic rule suppression syntax across all workspace configurations and source files.

## Strict Guidelines
- Engineers MUST ALWAYS pin the `$schema` property in `biome.json` or `biome.jsonc` to the exact matching minor/patch release (e.g., `https://biomejs.dev/schemas/1.9.4/schema.json`) to guarantee schema validation and parity between local CLI and CI.
- Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` instead of duplicating `.gitignore` patterns inside `files.ignore`.
- Engineers MUST ALWAYS provide a mandatory, verifiable reason string when suppressing lint rules using the standard syntax `// biome-ignore lint/<group>/<rule>: <explanation>`. Suppressions without a colon and reasoning MUST NOT be introduced.
- Engineers MUST NOT use legacy ESLint comments (`// eslint-disable`, `/* eslint-disable */`) or Prettier ignore comments (`// prettier-ignore`) in codebases governed by Biome.
- Monorepo packages MUST use configuration inheritance via the `extends` property referencing shared config packages or root relative paths (e.g., `"extends": ["@company/biome-config"]` or `"extends": ["../../biome.json"]`), avoiding duplicate rule overrides.
- Teams MUST invoke `biome check` with `--error-on-warnings` in CI pipelines to prevent lint warning accumulation from degrading into technical debt.

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

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing $schema leads to unvalidated configurations. Explicitly re-specifying files already ignored by Git leads to ignore-drift; VCS integration is missing.
```json
{
  "files": {
    "ignore": ["node_modules", "dist", ".next", "coverage"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins exact Biome 1.9.4 schema, extends shared base configuration, and utilizes Git ignore integration natively without redundant duplicate lists.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["@acme/biome-config"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: ESLint directive is ignored by Biome, causing lint errors. The subsequent Biome suppression lacks an explanation, violating strict audit requirements and triggering suppression warnings.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(raw: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(raw) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Uses the canonical Biome 1.9 inline suppression format `// biome-ignore lint/<group>/<rule>: <explanation>` with a descriptive rationale.
```typescript
export function deserializePayload(raw: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: External legacy webhook schema is dynamic and validated downstream by Zod
  return JSON.parse(raw) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git Context Provider
Validates git status, changed files, and tracked ignores against Biome VCS configuration.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes single-binary checks, auto-formatting, and import sorting via `biome check --write`.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Deterministic Configuration, VCS Integration, and Suppression Protocol defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic single-binary linting and formatting via Biome 1.9 configuration standards. Enforces native VCS ignore file inheritance, strict JSON schema validation, and structured inline suppression syntax with mandatory explanations to eliminate configuration drift and unvetted rule bypasses. 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 Biome Configuration, Redundant Ignore Lists, and Unexplained Suppression Comments 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 Biome Configuration, Redundant Ignore Lists, and Unexplained Suppression CommentsCritical
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 pin the `$schema` property in `biome.json` or `biome.jsonc` to the exact matching minor/patch release (e.g., `https

Engineers MUST ALWAYS pin the `$schema` property in `biome.json` or `biome.jsonc` to the exact matching minor/patch release (e.g., `https://biomejs.dev/schemas/1.9.4/schema.json`) to guarantee schema validation and parity between local CLI and CI.

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 enable VCS integration via `vcs.enabled

Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` instead of duplicating `.gitignore` patterns inside `files.ignore`.

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 a mandatory, verifiable reason string when suppressing lint rules using the standard syntax `// biome-ignore lint/<group>/<rule>

Engineers MUST ALWAYS provide a mandatory, verifiable reason string when suppressing lint rules using the standard syntax `// biome-ignore lint/<group>/<rule>: <explanation>`. Suppressions without a colon and reasoning MUST NOT be introduced.

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 ESLint comments (`// eslint-disable`, `/* eslint-disable */`) or Prettier ignore comments (`// prettier-ignore`) in codebases governed by Biome.

Engineers MUST NOT use legacy ESLint comments (`// eslint-disable`, `/* eslint-disable */`) or Prettier ignore comments (`// prettier-ignore`) in codebases governed by 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.
5

Monorepo packages MUST use configuration inheritance via the `extends` property referencing shared config packages or root relative paths (e.g., `"extends"

Monorepo packages MUST use configuration inheritance via the `extends` property referencing shared config packages or root relative paths (e.g., `"extends": ["@company/biome-config"]` or `"extends": ["../../biome.json"]`), avoiding duplicate rule 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

Teams MUST invoke `biome check` with `--error-on-warnings` in CI pipelines to prevent lint warning accumulation from degrading into technical debt.

Teams MUST invoke `biome check` with `--error-on-warnings` in CI pipelines to prevent lint warning accumulation from degrading into technical debt.

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

Mandates deterministic single-binary linting and formatting via Biome 1.9 configuration standards. Enforces native VCS ignore file inheritance, strict JSON schema validation, and structured inline suppression syntax with mandatory explanations to eliminate configuration drift and unvetted rule bypasses. 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 Biome Configuration, Redundant Ignore Lists, and Unexplained Suppression Comments) 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