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-config-vcs-suppression-governance

Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard

Enforces deterministic Biome 1.9 configuration architecture across monorepos using strict extends inheritance, native Git VCS integration to prevent dirty state drift, and mandatory contextual explanation syntax for inline lint suppressions. Eliminates CI cache invalidation, processing of untracked assets, and unreviewed quality bypasses.

Prohibited Anti-Pattern: Unanchored Biome configuration omitting VCS integration and using justification-free rule suppressions or obsolete ESLint directives.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard - Enforces deterministic Biome 1.9 configuration architecture across monorepos using strict extends inheritance, native Git VCS integration to prevent dirty state drift, and mandatory contextual explanation syntax for inline lint suppressions. Eliminates CI cache invalidation, processing of untracked assets, and unreviewed quality bypasses.
globs: biome.json, biome.jsonc, packages/**/biome.json, src/**/*.{ts,tsx,js,jsx,json,css}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-config-vcs-suppression-governance"
---

# Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored Biome configuration omitting VCS integration and using justification-free rule suppressions or obsolete ESLint directives.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards. Mandate explicit VCS integration in root configurations, structured workspace inheritance via `extends`, and strictly require reasoned explanations for all inline suppression directives (`// biome-ignore <group>/<rule>: <rationale>`). Reject legacy ESLint/Prettier directives, missing explanations, and global rule-category disabling.

## Strict Guidelines
- Engineers MUST configure `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in root configuration files to prevent processing ignored artifacts and untracked files.
- Engineers MUST ALWAYS provide an actionable rationale matching the pattern `// biome-ignore <group>/<rule>: <explanation>` whenever suppressing a Biome lint rule.
- Engineers MUST NOT use legacy ESLint comments (e.g., `// eslint-disable-next-line`) or Prettier suppression comments (`// prettier-ignore`); these are ignored by Biome and pollute code reviews.
- Child packages within a monorepo MUST inherit from the root workspace configuration using `extends: ["../../biome.json"]` or workspace-relative syntax rather than copying rule declarations.
- Engineers MUST NOT disable entire rule groups (e.g., `"recommended": false` or `"all": false`) in `biome.json`; individual rule overrides MUST be granularly scoped to `"warn"`, `"error"`, or `"off"` with documented justifications.
- CLI workflows in CI and pre-commit hooks SHOULD execute `biome check --write --staged` or `biome ci --changed` to maximize single-binary performance and leverage the configured VCS engine.

## Bad vs Good Implementations
### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The first example uses obsolete ESLint comments that Biome ignores, leaving the underlying violation unhandled. The second example uses Biome suppression but omits the mandatory colon and explanatory rationale required by deterministic Biome standards.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const legacyPayload: any = JSON.parse(rawIncomingData);

// biome-ignore lint/suspicious/noExplicitAny
function processUntyped(payload: any): void {
  console.log(payload);
}
```

#### Production Standard (Correct)
> **Standard**: Suppression directives use the canonical `// biome-ignore <group>/<rule>: <explanation>` format, providing auditability and preventing arbitrary lint rule circumvention.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External legacy webhook schema is undefined; sanitized via runtime parseSchema()
const legacyPayload: any = JSON.parse(rawIncomingData);

// biome-ignore lint/suspicious/noExplicitAny: Third-party generic callback payload contract requires dynamic introspection
function processUntyped(payload: any): void {
  console.log(payload);
}
```

### Biome Monorepo Configuration and VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to declare `vcs` integration (causing Biome to ignore `.gitignore` and re-scan untracked files), manually reinvents ignore lists, and disables entire recommended rule suites instead of granularly scoping overrides.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": false
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Configures native Git integration to automatically respect `.gitignore`, activates recommended rule sets by default, and enforces explicit lint rule strictness with schema-backed validation.
```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,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git MCP Server
Validates working tree state, dirty files, and staged changes for precise `biome check --staged` execution.
Recommended Agent Skills (askills.dev)

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

Biome Single-Binary CLI Runner
Executes high-throughput Biome checks, formatting, and auto-fixes deterministically against staged and changed files.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard

Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configuration architecture across monorepos using strict extends inheritance, native Git VCS integration to prevent dirty state drift, and mandatory contextual explanation syntax for inline lint suppressions. Eliminates CI cache invalidation, processing of untracked assets, and unreviewed quality 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 omitting VCS integration and using justification-free rule suppressions or obsolete ESLint directives. 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 omitting VCS integration and using justification-free rule suppressions or obsolete ESLint directives.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 configure `vcs.enabled

Engineers MUST configure `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in root configuration files to prevent processing ignored artifacts and untracked 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.
2

Engineers MUST ALWAYS provide an actionable rationale matching the pattern `// biome-ignore <group>/<rule>

Engineers MUST ALWAYS provide an actionable rationale matching the pattern `// biome-ignore <group>/<rule>: <explanation>` whenever suppressing a Biome lint rule.

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 comments (e.g., `// eslint-disable-next-line`) or Prettier suppression comments (`// prettier-ignore`)

Engineers MUST NOT use legacy ESLint comments (e.g., `// eslint-disable-next-line`) or Prettier suppression comments (`// prettier-ignore`); these are ignored by Biome and pollute code reviews.

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

Child packages within a monorepo MUST inherit from the root workspace configuration using `extends

Child packages within a monorepo MUST inherit from the root workspace configuration using `extends: ["../../biome.json"]` or workspace-relative syntax rather than copying rule declarations.

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

Engineers MUST NOT disable entire rule groups (e.g., `"recommended"

Engineers MUST NOT disable entire rule groups (e.g., `"recommended": false` or `"all": false`) in `biome.json`; individual rule overrides MUST be granularly scoped to `"warn"`, `"error"`, or `"off"` with documented justifications.

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

CLI workflows in CI and pre-commit hooks SHOULD execute `biome check --write --staged` or `biome ci --changed` to maximize single-binary performance and leverage the configured VCS engine.

CLI workflows in CI and pre-commit hooks SHOULD execute `biome check --write --staged` or `biome ci --changed` to maximize single-binary performance and leverage the configured VCS engine.

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 Monorepo Inheritance, VCS Integration, and Strict Rule Suppression Standard critical for AI coding assistants?

Enforces deterministic Biome 1.9 configuration architecture across monorepos using strict extends inheritance, native Git VCS integration to prevent dirty state drift, and mandatory contextual explanation syntax for inline lint suppressions. Eliminates CI cache invalidation, processing of untracked assets, and unreviewed quality 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 omitting VCS integration and using justification-free rule suppressions or obsolete ESLint directives.) 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