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

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

Enforces strict configuration inheritance patterns, Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Disallows legacy ESLint/Prettier suppression comments and untyped Biome ignores without explicit justification, ensuring reproducibility across local and CI environments.

Prohibited Anti-Pattern: Ad-Hoc Suppressions, Leaked Ignored Files, and Broken Monorepo Configuration Overrides

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 strict configuration inheritance patterns, Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Disallows legacy ESLint/Prettier suppression comments and untyped Biome ignores without explicit justification, ensuring reproducibility across local and CI environments.
globs: biome.json, biome.jsonc, apps/**/biome.json, packages/**/biome.json, src/**/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-vcs-deterministic-suppression-standard"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-Hoc Suppressions, Leaked Ignored Files, and Broken Monorepo Configuration Overrides

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate strict monorepo configuration inheritance via `extends`, explicit VCS integration using `vcs.clientKind: 'git'`, and deterministic suppression syntax using `biome-ignore lint/<group>/<rule>: <explanation>`. Reject any legacy ESLint/Prettier suppression comments or untyped Biome suppressions.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true` and `vcs.clientKind: "git"` in root `biome.json` so Biome honors `.gitignore` and enables `biome check --changed` workflows.
- Engineers MUST ALWAYS provide an explicit, non-empty reason when suppressing diagnostics using `biome-ignore lint/<group>/<rule>: <explanation>`.
- Engineers MUST NOT use legacy comments such as `// eslint-disable-next-line` or `// prettier-ignore` for Biome-managed files.
- Engineers MUST NOT use blanket `biome-ignore` without specifying the exact rule domain (e.g., `biome-ignore lint/suspicious/noExplicitAny: reason`).
- Monorepo packages MUST inherit root configuration using `extends: ["../../biome.json"]` rather than duplicating linter and formatter rule sets.
- CI pipelines MUST execute `biome ci` instead of `biome check` to guarantee deterministic, non-mutating validation.
- Engineers MUST set `formatter.lineEnding: "lf"` and `formatter.formatWithErrors: false` to prevent malformed code propagation during syntax errors.

## Bad vs Good Implementations
### Root Biome 1.9 Configuration with VCS and Monorepo Extensibility

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to define VCS client integration, leaving untracked files subject to formatting drift and breaking `--changed` flags in CI. Omits schema pinning, LF normalization, and overrides structure.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins the exact 1.9 schema, enables VCS-driven gitignore resolution, enforces deterministic LF line endings, disables formatting broken ASTs, and activates strict rule sets.
```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,
    "lineEnding": "lf",
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses legacy ESLint directive ignored by Biome, alongside an unspecific `biome-ignore lint` suppression lacking both the rule path and a required rationale.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint
  return JSON.parse(input);
}
```

#### Production Standard (Correct)
> **Standard**: Uses the fully qualified Biome 1.9 suppression format (`biome-ignore <category>/<group>/<rule>: <explanation>`) detailing the precise violation and production justification.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Legacy boundary payload requires loose typing pending schema migration
export function deserializePayload(input: string): any {
  return JSON.parse(input);
}
```

### Monorepo Package Configuration Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Packages that duplicate the root config break global style synchronization and drift over time without centralized maintenance.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Inherits baseline formatter, linter, and VCS rules from root while isolating package-specific JSX runtime extensions cleanly.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.json"],
  "javascript": {
    "jsxRuntime": "reactCompiler"
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP
Enables inspection and modification of `biome.json` configurations and source code files.
Git MCP
Inspects git diff status and branch heads to validate changed-file targeting with Biome.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Command-line tool to run `biome check --changed` and `biome ci` for deterministic checks.
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 strict configuration inheritance patterns, Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Disallows legacy ESLint/Prettier suppression comments and untyped Biome ignores without explicit justification, ensuring reproducibility across local and CI environments. 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: Ad-Hoc Suppressions, Leaked Ignored Files, and Broken Monorepo Configuration Overrides 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 DriftAd-Hoc Suppressions, Leaked Ignored Files, and Broken Monorepo Configuration OverridesCritical
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` and `vcs.clientKind: "git"` in root `biome.json` so Biome honors `.gitignore` and enables `biome check --changed` workflows.

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, non-empty reason when suppressing diagnostics using `biome-ignore lint/<group>/<rule>

Engineers MUST ALWAYS provide an explicit, non-empty reason when suppressing diagnostics using `biome-ignore lint/<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.
3

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

Engineers MUST NOT use legacy comments such as `// 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.
4

Engineers MUST NOT use blanket `biome-ignore` without specifying the exact rule domain (e.g., `biome-ignore lint/suspicious/noExplicitAny

Engineers MUST NOT use blanket `biome-ignore` without specifying the exact rule domain (e.g., `biome-ignore lint/suspicious/noExplicitAny: 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.
5

Monorepo packages MUST inherit root configuration using `extends

Monorepo packages MUST inherit root configuration using `extends: ["../../biome.json"]` rather than duplicating linter and formatter rule sets.

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` instead of `biome check` to guarantee deterministic, non-mutating validation.

CI pipelines MUST execute `biome ci` instead of `biome check` to guarantee deterministic, non-mutating validation.

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.
7

Engineers MUST set `formatter.lineEnding

Engineers MUST set `formatter.lineEnding: "lf"` and `formatter.formatWithErrors: false` to prevent malformed code propagation during syntax errors.

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 strict configuration inheritance patterns, Git VCS integration, and deterministic rule suppression syntax under Biome 1.9. Disallows legacy ESLint/Prettier suppression comments and untyped Biome ignores without explicit justification, ensuring reproducibility across local and CI environments. 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 (Ad-Hoc Suppressions, Leaked Ignored Files, and Broken Monorepo Configuration Overrides) 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