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-monorepo-vcs-suppression-guardrail

Biome 1.9 Monorepo Configuration Inheritance, VCS Integration, and Suppression Standards

Enforces strict configuration inheritance via the 'extends' array, deterministic Git VCS integration for dirty-file parsing, and mandatory machine-readable suppression comments with explicit reasoning in Biome 1.9+. Prevents CI/CD drift, phantom formatting conflicts, and unreviewed lint bypasses across monorepo architectures.

Prohibited Anti-Pattern: Fragmented Prettier/ESLint Legacy Overlaps, Broken Monorepo Extends, and Arbitrary Lint Suppression

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Monorepo Configuration Inheritance, VCS Integration, and Suppression Standards - Enforces strict configuration inheritance via the 'extends' array, deterministic Git VCS integration for dirty-file parsing, and mandatory machine-readable suppression comments with explicit reasoning in Biome 1.9+. Prevents CI/CD drift, phantom formatting conflicts, and unreviewed lint bypasses across monorepo architectures.
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-1-9-monorepo-vcs-suppression-guardrail"
---

# Biome 1.9 Monorepo Configuration Inheritance, VCS Integration, and Suppression Standards

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented Prettier/ESLint Legacy Overlaps, Broken Monorepo Extends, and Arbitrary Lint Suppression

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards across distributed monorepo codebases. You must mandate strict configuration inheritance, Git integration via 'vcs.clientKind' to avoid processing ignored files, and reject any suppression comment lacking explicit rule identification and machine-readable explanation tokens.

## Strict Guidelines
- Engineers MUST configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root biome.json to align formatting scope with Git status.
- Engineers MUST structure workspace-level configs to inherit via 'extends: ["../../biome.json"]' rather than duplicating lint/formatter configuration blocks.
- Engineers MUST NEVER use bare suppression comments; all inline bypasses must follow '// biome-ignore lint/group/ruleName: <explanation>' or '// biome-ignore-all lint/group/ruleName: <explanation>'.
- Services MUST execute 'biome check --write --vcs-client-kind=git' in local commit hooks and strictly execute 'biome ci' within remote integration pipelines.
- Engineers MUST NOT run Prettier or ESLint concurrently on paths covered by Biome 1.9; duplicate formatting orchestrators must be stripped to eliminate AST race conditions.

## Bad vs Good Implementations
### Biome Configuration Root vs Package Inheritance with VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits 'vcs' configuration forcing manual file ignoring, duplicates root rules across packages instead of using 'extends', and relies on manually synchronized blacklist arrays.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".turbo"]
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Enables native VCS integration inheriting from .gitignore and defines global baseline formatting invariants to be consumed down the dependency tree.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```

### Deterministic Lint Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses deprecated ESLint comments that Biome ignores, invalid bare biome-ignore comments without a rule name, or omits mandatory explanations for rule bypasses.
```typescript
// eslint-disable-next-line
const legacyToken = eval("window.__SECRET_PAYLOAD");

// biome-ignore: need this
const userQuery = (req.body as any).query;

// biome-ignore lint/suspicious/noExplicitAny
let unvalidatedContext: any;
```

#### Production Standard (Correct)
> **Standard**: Adheres strictly to the Biome 1.9 suppression specification: specifies exact rule namespace and requires a trailing explanation explaining why the bypass is safe.
```typescript
// biome-ignore lint/security/noGlobalEval: Legacy runtime payload requires direct eval until SDK v3 migration
const legacyToken = eval("window.__SECRET_PAYLOAD");

// biome-ignore lint/suspicious/noExplicitAny: External webhook payload is non-deterministic; validated by Zod parser below
const userQuery = (req.body as any).query;

// biome-ignore lint/suspicious/noExplicitAny: Third-party integration SDK lacks typed definitions for context
let unvalidatedContext: any;
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git Context MCP
Provides VCS status and gitignore tree validation to verify Biome's target working set.
Recommended Agent Skills (askills.dev)

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

Biome CLI Diagnostics
Runs ultra-fast linting, formatting, and AST imports organization across dirty Git trees using single-binary CLI commands.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Monorepo Configuration Inheritance, VCS Integration, and Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance via the 'extends' array, deterministic Git VCS integration for dirty-file parsing, and mandatory machine-readable suppression comments with explicit reasoning in Biome 1.9+. Prevents CI/CD drift, phantom formatting conflicts, and unreviewed lint bypasses across monorepo architectures. 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 Prettier/ESLint Legacy Overlaps, Broken Monorepo Extends, and Arbitrary Lint Suppression 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 Prettier/ESLint Legacy Overlaps, Broken Monorepo Extends, and Arbitrary Lint SuppressionCritical
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 biome.json to align formatting scope with Git status.

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 structure workspace-level configs to inherit via 'extends

Engineers MUST structure workspace-level configs to inherit via 'extends: ["../../biome.json"]' rather than duplicating lint/formatter configuration blocks.

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 NEVER use bare suppression comments

Engineers MUST NEVER use bare suppression comments; all inline bypasses must follow '// biome-ignore lint/group/ruleName: <explanation>' or '// biome-ignore-all lint/group/ruleName: <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.
4

Services MUST execute 'biome check --write --vcs-client-kind=git' in local commit hooks and strictly execute 'biome ci' within remote integration pipelines.

Services MUST execute 'biome check --write --vcs-client-kind=git' in local commit hooks and strictly execute 'biome ci' within remote integration pipelines.

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 run Prettier or ESLint concurrently on paths covered by Biome 1.9

Engineers MUST NOT run Prettier or ESLint concurrently on paths covered by Biome 1.9; duplicate formatting orchestrators must be stripped to eliminate AST race conditions.

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 Configuration Inheritance, VCS Integration, and Suppression Standards critical for AI coding assistants?

Enforces strict configuration inheritance via the 'extends' array, deterministic Git VCS integration for dirty-file parsing, and mandatory machine-readable suppression comments with explicit reasoning in Biome 1.9+. Prevents CI/CD drift, phantom formatting conflicts, and unreviewed lint bypasses across monorepo architectures. 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 Prettier/ESLint Legacy Overlaps, Broken Monorepo Extends, and Arbitrary Lint Suppression) 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