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-inheritance-vcs-suppression

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

Enforces strict configuration architecture in Biome 1.9+, establishing centralized workspace inheritance, automated Git-driven VCS ignore synchronization, and validated deterministic inline suppression syntax. Prevents toolchain fragmentation, divergent ignore sets, and silent lint-rule circumvention across monorepos.

Prohibited Anti-Pattern: Fragmented multi-tool ignore drift, orphaned nested configurations, and opaque rule suppressions without explicit justification.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Monorepo Configuration, VCS Integration, and Deterministic Suppression Standards - Enforces strict configuration architecture in Biome 1.9+, establishing centralized workspace inheritance, automated Git-driven VCS ignore synchronization, and validated deterministic inline suppression syntax. Prevents toolchain fragmentation, divergent ignore sets, and silent lint-rule circumvention across monorepos.
globs: biome.json, biome.jsonc, **/biome.json, **/biome.jsonc, **/*.{ts,tsx,js,jsx,json}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-config-inheritance-vcs-suppression"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented multi-tool ignore drift, orphaned nested configurations, and opaque rule suppressions without explicit justification.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9+ standards. In all generated code, configs, and file edits, mandate centralized configuration inheritance via 'extends', automated VCS synchronization via 'vcs.useIgnoreFile', and strictly structured inline suppression comments matching '// biome-ignore <group>/<rule>: <explanation>'. Never emit bare suppression comments, never duplicate .gitignore entries in files.ignore, and reject legacy ESLint/Prettier directive comments.

## Strict Guidelines
- Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root biome.json to derive file inclusion automatically from Git.
- Engineers MUST NOT maintain duplicate glob exclusion lists across .gitignore and biome.json 'files.ignore'; reserve 'files.ignore' exclusively for non-gitified linter bypasses.
- Workspace packages MUST extend shared base configs using relative or package-based paths via the 'extends' array rather than copy-pasting monolithic configurations.
- Code MUST strictly use the canonical inline suppression syntax: '// biome-ignore <group>/<rule>: <reason>' with an explicit, non-empty justification string.
- Engineers MUST NEVER use bare suppressions (e.g., '// biome-ignore'), legacy comment directives (e.g., '// eslint-disable-next-line', '// @ts-ignore' without justification), or file-wide blanket rule suppressions.
- All configuration files SHOULD use 'biome.json' or 'biome.jsonc' and pin the official JSON schema path to '$schema': 'https://biomejs.dev/schemas/1.9.4/schema.json' matching the installed binary.

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

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually maintains duplicate ignore patterns already handled by Git, omits VCS client integration, and does not establish an extendable base architecture for monorepo packages.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next", "coverage"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Delegates file exclusion to the Git subsystem natively via VCS settings, sets explicit formatting invariants, and binds to the verified 1.9.4 schema release.
```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
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses incompatible legacy ESLint suppression syntax and unannotated Biome suppression missing the mandatory reason delimiter and explanation.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const legacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny
function processData(input: any) {
  return input;
}
```

#### Production Standard (Correct)
> **Standard**: Prefers type-safe alternatives where possible and uses the canonical Biome 1.9 suppression syntax with an explicit rule name and mandatory explanation string.
```typescript
const legacyPayload: unknown = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny: Required during phase 1 migration of untyped upstream webhook schema
function processData(input: any): any {
  return input;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git MCP Server
Enables inspection of tracked files and git status to verify Biome VCS ignore compatibility.
Filesystem MCP Server
Reads and modifies biome.json, biome.jsonc, and source files across nested monorepo packages.
Recommended Agent Skills (askills.dev)

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

Biome Check Runner
Executes 'biome check --write' and 'biome ci' to validate formatting, linting, and imports deterministically.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Monorepo Configuration, VCS Integration, and Deterministic Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration architecture in Biome 1.9+, establishing centralized workspace inheritance, automated Git-driven VCS ignore synchronization, and validated deterministic inline suppression syntax. Prevents toolchain fragmentation, divergent ignore sets, and silent lint-rule circumvention across monorepos. 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 multi-tool ignore drift, orphaned nested configurations, and opaque rule suppressions without explicit justification. 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 multi-tool ignore drift, orphaned nested configurations, and opaque rule suppressions without explicit justification.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 root biome.json to derive file inclusion automatically from Git.

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 NOT maintain duplicate glob exclusion lists across .gitignore and biome.json 'files.ignore'

Engineers MUST NOT maintain duplicate glob exclusion lists across .gitignore and biome.json 'files.ignore'; reserve 'files.ignore' exclusively for non-gitified linter bypasses.

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

Workspace packages MUST extend shared base configs using relative or package-based paths via the 'extends' array rather than copy-pasting monolithic configurations.

Workspace packages MUST extend shared base configs using relative or package-based paths via the 'extends' array rather than copy-pasting monolithic configurations.

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

Code MUST strictly use the canonical inline suppression syntax

Code MUST strictly use the canonical inline suppression syntax: '// biome-ignore <group>/<rule>: <reason>' with an explicit, non-empty justification string.

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 NEVER use bare suppressions (e.g., '// biome-ignore'), legacy comment directives (e.g., '// eslint-disable-next-line', '// @ts-ignore' without justification), or file-wide blanket rule suppressions.

Engineers MUST NEVER use bare suppressions (e.g., '// biome-ignore'), legacy comment directives (e.g., '// eslint-disable-next-line', '// @ts-ignore' without justification), or file-wide blanket rule suppressions.

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

All configuration files SHOULD use 'biome.json' or 'biome.jsonc' and pin the official JSON schema path to '$schema'

All configuration files SHOULD use 'biome.json' or 'biome.jsonc' and pin the official JSON schema path to '$schema': 'https://biomejs.dev/schemas/1.9.4/schema.json' matching the installed binary.

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

Enforces strict configuration architecture in Biome 1.9+, establishing centralized workspace inheritance, automated Git-driven VCS ignore synchronization, and validated deterministic inline suppression syntax. Prevents toolchain fragmentation, divergent ignore sets, and silent lint-rule circumvention across monorepos. 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 multi-tool ignore drift, orphaned nested configurations, and opaque rule suppressions without explicit justification.) 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