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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance

Enforces strict Biome 1.9 toolchain architectural standards across enterprise repositories and monorepos. Mandates automated Git VCS ignore synchronization, centralized configuration inheritance with overrides, and deterministic inline suppression syntax that requires explicit human justification.

Prohibited Anti-Pattern: Fragmented tooling configs, unanchored ESLint-style disable pragmas, and missing VCS ignore integration that cause CI drift and non-deterministic formatting failures.

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 strict Biome 1.9 toolchain architectural standards across enterprise repositories and monorepos. Mandates automated Git VCS ignore synchronization, centralized configuration inheritance with overrides, and deterministic inline suppression syntax that requires explicit human justification.
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-inheritance-suppression-guardrail"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented tooling configs, unanchored ESLint-style disable pragmas, and missing VCS ignore integration that cause CI drift and non-deterministic formatting failures.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards. Mandate single-binary toolchain consistency across frontend applications. Ensure that all package-level configs inherit from root configurations, VCS ignore integration is strictly enabled to prevent diverging git/linter boundaries, and any rule suppression adheres to the strict Biome 1.9 deterministic format with a mandatory explanatory justification string.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent duplicated ignore rules across Git and Biome.
- Workspace packages MUST extend the root configuration using `extends: ['../../biome.json']` rather than redefining global formatting or linting rules.
- Engineers MUST NOT use legacy comments like `eslint-disable`, `@ts-ignore`, or reason-free suppression comments to bypass Biome checks.
- Inline suppressions MUST strictly use the format `// biome-ignore <group>/<rule>: <explanation>` where `<explanation>` is a non-empty, audited rationale.
- Suppression scopes MUST be limited to the immediate single statement or token target; engineers MUST NEVER apply bulk suppression without explicit architect sign-off.
- Repository CI pipelines MUST run `biome check --staged` or `biome ci --changed` against the default branch rather than rescanning ignored external artifacts.

## Bad vs Good Implementations
### Biome Monorepo Inheritance and VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure VCS integration (forcing error-prone manual duplicate ignore lists) and lacks inheritance mechanisms for sub-packages.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enables native Git VCS integration honoring .gitignore automatically, pins schema to exact patch version, and acts as the single source of truth for workspaces extending it via `extends`.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": false
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses incompatible ESLint pragmas and omits the mandatory explanation clause on the Biome suppression comment, violating deterministic auditability.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const raw: any = JSON.parse(input);
  return raw;
}
```

#### Production Standard (Correct)
> **Standard**: Uses Biome 1.9 compliant `// biome-ignore <group>/<rule>: <explanation>` with a concrete contextual explanation.
```typescript
/**
 * Deserializes an unvalidated external webhook payload.
 */
// biome-ignore lint/suspicious/noExplicitAny: Raw untrusted payload requires runtime schema validation downstream
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny: Upstream wire protocol transmits dynamic polymorphic structures
  const raw: any = JSON.parse(input);
  return raw;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git Context Provider
Inspects git staging status and changed files to optimize Biome check runs via VCS parameters.
Recommended Agent Skills (askills.dev)

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

Biome CLI Orchestrator
Executes optimized biome check, format, and lint commands leveraging single-binary execution and VCS diff flags.
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 strict Biome 1.9 toolchain architectural standards across enterprise repositories and monorepos. Mandates automated Git VCS ignore synchronization, centralized configuration inheritance with overrides, and deterministic inline suppression syntax that requires explicit human justification. 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: Fragmented tooling configs, unanchored ESLint-style disable pragmas, and missing VCS ignore integration that cause CI drift and non-deterministic formatting failures. 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 DriftFragmented tooling configs, unanchored ESLint-style disable pragmas, and missing VCS ignore integration that cause CI drift and non-deterministic formatting failures.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 `vcs.enabled

Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent duplicated ignore rules across 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

Workspace packages MUST extend the root configuration using `extends

Workspace packages MUST extend the root configuration using `extends: ['../../biome.json']` rather than redefining global formatting or linting 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.
3

Engineers MUST NOT use legacy comments like `eslint-disable`, `@ts-ignore`, or reason-free suppression comments to bypass Biome checks.

Engineers MUST NOT use legacy comments like `eslint-disable`, `@ts-ignore`, or reason-free suppression comments to bypass Biome checks.

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

Inline suppressions MUST strictly use the format `// biome-ignore <group>/<rule>

Inline suppressions MUST strictly use the format `// biome-ignore <group>/<rule>: <explanation>` where `<explanation>` is a non-empty, audited rationale.

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

Suppression scopes MUST be limited to the immediate single statement or token target

Suppression scopes MUST be limited to the immediate single statement or token target; engineers MUST NEVER apply bulk suppression without explicit architect sign-off.

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

Repository CI pipelines MUST run `biome check --staged` or `biome ci --changed` against the default branch rather than rescanning ignored external artifacts.

Repository CI pipelines MUST run `biome check --staged` or `biome ci --changed` against the default branch rather than rescanning ignored external 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.
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 strict Biome 1.9 toolchain architectural standards across enterprise repositories and monorepos. Mandates automated Git VCS ignore synchronization, centralized configuration inheritance with overrides, and deterministic inline suppression syntax that requires explicit human justification. 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 (Fragmented tooling configs, unanchored ESLint-style disable pragmas, and missing VCS ignore integration that cause CI drift and non-deterministic formatting failures.) 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