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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Governance

Enforces strict configuration inheritance, Git-aware VCS boundary enforcement, and deterministic suppression syntax using Biome 1.9+. Prevents lint regressions across monorepos, invalid suppression comments, and untracked code formatting drifts by enforcing exact schema pinning and mandatory explanation keys in lint suppressions.

Prohibited Anti-Pattern: Unpinned Biome Configurations, Missing VCS Boundaries, and Undocumented Global Comment Suppressions

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 configuration inheritance, Git-aware VCS boundary enforcement, and deterministic suppression syntax using Biome 1.9+. Prevents lint regressions across monorepos, invalid suppression comments, and untracked code formatting drifts by enforcing exact schema pinning and mandatory explanation keys in lint suppressions.
globs: biome.json, biome.jsonc, **/biome.json, **/biome.jsonc, **/*.{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-standard"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unpinned Biome Configurations, Missing VCS Boundaries, and Undocumented Global Comment Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 Single-Binary Linter and Formatter standards. You must mandate exact schema versioning, strict configuration inheritance (via 'extends'), VCS integration with client-side git hooks, and deterministic inline rule suppression formats that include non-negotiable architectural rationales.

## Strict Guidelines
- Engineers MUST ALWAYS pin '$schema' in biome.json to the exact patch version URL (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to avoid parser drift.
- Engineers MUST ALWAYS configure 'vcs' integration in the root biome.json with 'enabled: true', 'clientKind: "git"', and 'useIgnoreFile: true' to respect .gitignore boundaries deterministically.
- Engineers MUST NOT use unanchored or unexplained suppression comments; all inline suppressions MUST follow the strict Biome 1.9 format: '// biome-ignore lint/<group>/<rule>: <deterministic architectural rationale>'.
- Subpackages in a monorepo MUST inherit root settings using '"extends": ["//biome.json"]' or relative workspace paths rather than duplicating core formatting and lint rule configurations.
- Engineers MUST NEVER use legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line', '/* prettier-ignore */') in Biome-managed repositories.
- Automated CI pipelines MUST run 'biome ci --changed' or 'biome check --diagnostic-level=error' ensuring zero unformatted files and zero lint errors before merge.

## Bad vs Good Implementations
### Biome Configuration: Root Config with VCS and Inherited Monorepo Setup

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses 'latest' schema URL which causes non-deterministic drift when Biome updates, omits Git VCS integration which forces Biome to traverse ignored directories like node_modules or dist, and does not configure suppression limits.
```jsonc
{
  "$schema": "https://biomejs.dev/schemas/latest/schema.json",
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins exact 1.9.4 schema, explicitly integrates git VCS for boundary discovery, enables ignore-file resolution, and sets deterministic formatting rules.
```jsonc
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Suppression Syntax: Undocumented vs Documented Rule Exemption

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses obsolete ESLint directive that Biome ignores, followed by a Biome suppression that lacks a required architectural justification colon separator and description.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(input);
}
```

#### Production Standard (Correct)
> **Standard**: Uses official Biome 1.9 suppression syntax '// biome-ignore lint/<group>/<rule>: <explanation>' providing concrete context for static analyzers and reviewers.
```typescript
/**
 * Deserializes an untyped dynamic external payload.
 * Requires raw 'any' before downstream schema boundary validation.
 */
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Input is dynamic and validated via Zod at the application boundary
  return JSON.parse(input) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Protocol MCP
Direct MCP interface to run Biome single-binary diagnostics, autofixes, and deterministic formatting across the workspace.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Standard CLI toolkit for running 'biome check --write', 'biome ci', and configuration verification.
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 configuration inheritance, Git-aware VCS boundary enforcement, and deterministic suppression syntax using Biome 1.9+. Prevents lint regressions across monorepos, invalid suppression comments, and untracked code formatting drifts by enforcing exact schema pinning and mandatory explanation keys in lint suppressions. 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: Unpinned Biome Configurations, Missing VCS Boundaries, and Undocumented Global Comment 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnpinned Biome Configurations, Missing VCS Boundaries, and Undocumented Global Comment SuppressionsCritical
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 pin '$schema' in biome.json to the exact patch version URL (e.g., 'https

Engineers MUST ALWAYS pin '$schema' in biome.json to the exact patch version URL (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to avoid parser drift.

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 configure 'vcs' integration in the root biome.json with 'enabled

Engineers MUST ALWAYS configure 'vcs' integration in the root biome.json with 'enabled: true', 'clientKind: "git"', and 'useIgnoreFile: true' to respect .gitignore boundaries deterministically.

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 unanchored or unexplained suppression comments

Engineers MUST NOT use unanchored or unexplained suppression comments; all inline suppressions MUST follow the strict Biome 1.9 format: '// biome-ignore lint/<group>/<rule>: <deterministic architectural 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.
4

Subpackages in a monorepo MUST inherit root settings using '"extends"

Subpackages in a monorepo MUST inherit root settings using '"extends": ["//biome.json"]' or relative workspace paths rather than duplicating core formatting and lint rule 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.
5

Engineers MUST NEVER use legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line', '/* prettier-ignore */') in Biome-managed repositories.

Engineers MUST NEVER use legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line', '/* prettier-ignore */') in Biome-managed repositories.

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

Automated CI pipelines MUST run 'biome ci --changed' or 'biome check --diagnostic-level=error' ensuring zero unformatted files and zero lint errors before merge.

Automated CI pipelines MUST run 'biome ci --changed' or 'biome check --diagnostic-level=error' ensuring zero unformatted files and zero lint errors before merge.

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 configuration inheritance, Git-aware VCS boundary enforcement, and deterministic suppression syntax using Biome 1.9+. Prevents lint regressions across monorepos, invalid suppression comments, and untracked code formatting drifts by enforcing exact schema pinning and mandatory explanation keys in lint suppressions. 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 (Unpinned Biome Configurations, Missing VCS Boundaries, and Undocumented Global Comment 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 →
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