Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Suppression Syntax | AgentRules.org

Rules Stacks Clients Auditor Pruner Self-Heal RFCs Benchmark CLI CI/CD Authors Submit

This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →

frontendcritical PriorityID: biome-v1-9-config-inheritance-vcs-suppression

Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Suppression Syntax

Enforces architectural standards for Biome 1.9 configurations across workspaces. Mandates native VCS ignore synchronization, deterministic monorepo configuration inheritance, and strictly attributed suppression syntax with mandatory rationale.

Prohibited Anti-Pattern: Fragmented root configurations with redundant ignore lists, missing VCS links, and unattributed inline suppressions.

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 Suppression Syntax - Enforces architectural standards for Biome 1.9 configurations across workspaces. Mandates native VCS ignore synchronization, deterministic monorepo configuration inheritance, and strictly attributed suppression syntax with mandatory rationale.
globs: biome.json, biome.jsonc, packages/**/biome.json, apps/**/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-v1-9-config-inheritance-vcs-suppression"
---

# Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Suppression Syntax

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented root configurations with redundant ignore lists, missing VCS links, and unattributed inline suppressions.

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Enforce deterministic configuration inheritance, native Git VCS integration without redundant ignore duplicates, and strict, rationale-anchored rule suppression syntax (`// biome-ignore <group>/<rule>: <explanation>`). Reject ESLint/Prettier legacy overlaps and malformed suppressions.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in root `biome.json` to leverage native `.gitignore` resolution.
- Engineers MUST ALWAYS include a mandatory explanatory rationale after a colon in inline suppressions: `// biome-ignore <group>/<rule>: <explanation>`.
- Engineers MUST NOT commit bare suppressions (`// biome-ignore` or `// biome-ignore <group>/<rule>` without an explanatory colon clause).
- Engineers MUST NOT duplicate file ignore glob patterns in `files.ignore` if they are already present in `.gitignore` when `vcs.useIgnoreFile` is active.
- Workspace packages MUST extend the root configuration using relative paths in `extends` (e.g., `"extends": ["../../biome.json"]`) and override only package-specific constraints.
- CI pipelines MUST execute `biome check --changed --since=origin/main` for pull requests to exploit Biome's VCS-aware delta computation.
- Generated files and build outputs MUST be excluded via `$schema`-validated ignore arrays or top-level `files.includes`/`files.ignore` directives.

## Bad vs Good Implementations
### Biome Configuration: Redundant Ignores vs VCS Integration & Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure `vcs` integration, resulting in manual, brittle duplication of `.gitignore` paths inside `files.ignore` and preventing delta-checking in CI.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages Biome 1.9 native Git VCS integration to automatically respect `.gitignore`, activates `ignoreUnknown`, and sets the default branch for change detection.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Suppression lacks the mandatory explanatory reason following a colon, violating deterministic code audit standards.
```typescript
// biome-ignore lint/suspicious/noExplicitAny
export function deserializePayload(raw: string): any {
  return JSON.parse(raw);
}
```

#### Production Standard (Correct)
> **Standard**: Complies with Biome 1.9 suppression syntax by explicitly specifying the rule category, rule name, and a mandatory colon-delimited architectural justification.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External webhook payload schema is dynamic and validated downstream via Zod safeParse
export function deserializePayload(raw: string): any {
  return JSON.parse(raw);
}
```

Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Context Server

Executes Biome 1.9 diagnostics, format passes, and VCS delta checks directly within IDE workflows.

Recommended Agent Skills (askills.dev)

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

Biome CLI Runner

Runs high-performance linting, formatting, and import sorting via single-binary native commands.

Architectural Specification & Invariant Rationale

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

Biome 1.9 Monorepo Inheritance, VCS Integration, and Strict Suppression Syntax defines an industrial-grade behavioral standard for frontend engineering. Enforces architectural standards for Biome 1.9 configurations across workspaces. Mandates native VCS ignore synchronization, deterministic monorepo configuration inheritance, and strictly attributed suppression syntax with mandatory rationale. 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 root configurations with redundant ignore lists, missing VCS links, and unattributed inline suppressions. 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Fragmented root configurations with redundant ignore lists, missing VCS links, and unattributed inline suppressions.	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 Inconsistency	AI 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 root `biome.json` to leverage native `.gitignore` resolution.

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 include a mandatory explanatory rationale after a colon in inline suppressions

Engineers MUST ALWAYS include a mandatory explanatory rationale after a colon in inline suppressions: `// biome-ignore <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 commit bare suppressions (`// biome-ignore` or `// biome-ignore <group>/<rule>` without an explanatory colon clause).

Engineers MUST NOT commit bare suppressions (`// biome-ignore` or `// biome-ignore <group>/<rule>` without an explanatory colon clause).

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 duplicate file ignore glob patterns in `files.ignore` if they are already present in `.gitignore` when `vcs.useIgnoreFile` is active.

Engineers MUST NOT duplicate file ignore glob patterns in `files.ignore` if they are already present in `.gitignore` when `vcs.useIgnoreFile` is active.

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

Workspace packages MUST extend the root configuration using relative paths in `extends` (e.g., `"extends"

Workspace packages MUST extend the root configuration using relative paths in `extends` (e.g., `"extends": ["../../biome.json"]`) and override only package-specific constraints.

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 check --changed --since=origin/main` for pull requests to exploit Biome's VCS-aware delta computation.

CI pipelines MUST execute `biome check --changed --since=origin/main` for pull requests to exploit Biome's VCS-aware delta computation.

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

Generated files and build outputs MUST be excluded via `$schema`-validated ignore arrays or top-level `files.includes`/`files.ignore` directives.

Generated files and build outputs MUST be excluded via `$schema`-validated ignore arrays or top-level `files.includes`/`files.ignore` directives.

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

Enforces architectural standards for Biome 1.9 configurations across workspaces. Mandates native VCS ignore synchronization, deterministic monorepo configuration inheritance, and strictly attributed suppression syntax with mandatory rationale. 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 root configurations with redundant ignore lists, missing VCS links, and unattributed inline suppressions.) 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 →

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.

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.

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