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

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

Enforces strict configuration inheritance across monorepo packages, enables Git VCS integration to prevent format checking untracked/ignored assets, and mandates explicit deterministic inline suppression syntax with explanatory justifications. Prevents CI drift and broken linting passes in production repositories utilizing Biome 1.9+.

Prohibited Anti-Pattern: Fragmented rootless configs, missing VCS ignore integration, and justification-less ESLint-style rule 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 across monorepo packages, enables Git VCS integration to prevent format checking untracked/ignored assets, and mandates explicit deterministic inline suppression syntax with explanatory justifications. Prevents CI drift and broken linting passes in production repositories utilizing Biome 1.9+.
globs: **/biome.json, **/biome.jsonc, src/**/*.{ts,tsx,js,jsx,json,css}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-v1-9-monorepo-vcs-suppression-guardrail"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented rootless configs, missing VCS ignore integration, and justification-less ESLint-style rule suppression

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 Single-Binary Linter & Formatter. Mandate invariant configuration inheritance patterns via extends/root, strict VCS Git awareness, and deterministic suppression comments containing structured justification syntax.

## Strict Guidelines
- Monorepo package configurations MUST extend the root configuration via `"extends": ["//biome.json"]` or relative resolution paths.
- Root Biome configurations MUST declare `"root": true` and explicitly configure `vcs` with `"enabled": true`, `"clientKind": "git"`, and `"useIgnoreFile": true` to ensure parity with `.gitignore`.
- Engineers MUST NEVER use legacy ESLint suppression comments (e.g., `// eslint-disable-next-line`); they MUST use Biome 1.9 suppression syntax `// biome-ignore <group>/<rule>: <explanation>`.
- All Biome suppressions MUST provide a mandatory technical justification after the colon delimiter explaining why the rule violation cannot be resolved structurally.
- CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` to ensure deterministic non-zero exit codes on lint/format violations.

## Bad vs Good Implementations
### Root Configuration with VCS Integration vs Bare Disconnected Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to declare `root: true`, fails to integrate with Git VCS (leading to accidental checks on vendor files, build outputs, and untracked artifacts), and lacks deterministic workspace defaults.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Configures `root: true`, activates Git VCS ignore synchronization, and declares unified lint and format rules across the repository.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "root": true,
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  }
}
```

### Deterministic Biome Inline Suppression vs ESLint Legacy or Unjustified Suppression

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses incompatible legacy ESLint suppression comments, followed by an unjustified Biome suppression that lacks the mandatory explanation delimiter.
```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) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Uses Biome 1.9 suppression format `lint/group/rule` with a concrete, mandatory architectural justification following the colon delimiter.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External legacy webhook schema is polymorphic and validated dynamically downstream
export function deserializePayload(input: string): any {
  return JSON.parse(input) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Runner
Executes Biome 1.9 single-binary linting, formatting, and diagnostics directly within AI Agent environments.
Recommended Agent Skills (askills.dev)

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

Biome Format & Lint Check Skill
Automated CLI workflow invocation for `biome check --write` and suppression syntax verification.
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 across monorepo packages, enables Git VCS integration to prevent format checking untracked/ignored assets, and mandates explicit deterministic inline suppression syntax with explanatory justifications. Prevents CI drift and broken linting passes in production repositories utilizing Biome 1.9+. 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 rootless configs, missing VCS ignore integration, and justification-less ESLint-style rule 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 rootless configs, missing VCS ignore integration, and justification-less ESLint-style rule 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

Monorepo package configurations MUST extend the root configuration via `"extends"

Monorepo package configurations MUST extend the root configuration via `"extends": ["//biome.json"]` or relative resolution paths.

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

Root Biome configurations MUST declare `"root"

Root Biome configurations MUST declare `"root": true` and explicitly configure `vcs` with `"enabled": true`, `"clientKind": "git"`, and `"useIgnoreFile": true` to ensure parity with `.gitignore`.

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 legacy ESLint suppression comments (e.g., `// eslint-disable-next-line`)

Engineers MUST NEVER use legacy ESLint suppression comments (e.g., `// eslint-disable-next-line`); they MUST use Biome 1.9 suppression syntax `// 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.
4

All Biome suppressions MUST provide a mandatory technical justification after the colon delimiter explaining why the rule violation cannot be resolved structurally.

All Biome suppressions MUST provide a mandatory technical justification after the colon delimiter explaining why the rule violation cannot be resolved structurally.

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

CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` to ensure deterministic non-zero exit codes on lint/format violations.

CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` to ensure deterministic non-zero exit codes on lint/format violations.

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 across monorepo packages, enables Git VCS integration to prevent format checking untracked/ignored assets, and mandates explicit deterministic inline suppression syntax with explanatory justifications. Prevents CI drift and broken linting passes in production repositories utilizing Biome 1.9+. 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 rootless configs, missing VCS ignore integration, and justification-less ESLint-style rule 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