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-config-and-suppression-guardrails

Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions

Enforces strict configuration inheritance across monorepo boundaries in Biome 1.9, mandating Git-backed VCS integration for incremental CI passes and strict inline suppression syntax with mandatory human-readable justification. Prevents silent drift between formatting and linting engines while eliminating unverified blanket suppression comments.

Prohibited Anti-Pattern: Fragmented multi-tool configuration drift with undocumented blanket lint suppressions and non-VCS aware CI runs

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions - Enforces strict configuration inheritance across monorepo boundaries in Biome 1.9, mandating Git-backed VCS integration for incremental CI passes and strict inline suppression syntax with mandatory human-readable justification. Prevents silent drift between formatting and linting engines while eliminating unverified blanket suppression comments.
globs: biome.json, biome.jsonc, apps/**/*.{ts,tsx,js,jsx,json}, packages/**/*.{ts,tsx,js,jsx,json}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-monorepo-config-and-suppression-guardrails"
---

# Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented multi-tool configuration drift with undocumented blanket lint suppressions and non-VCS aware CI runs

## System Constraints
You are a Principal Engineer enforcing strict adherence to Biome 1.9 single-binary toolchain standards. Mandate monorepo configuration inheritance via `extends`, enforce VCS integration with Git ignore support, ensure deterministic configuration overrides per package boundary, and enforce the standard Biome suppression comment format (`// biome-ignore <category>/<rule>: <explanation>`) without exception.

## Strict Guidelines
- Monorepo packages MUST inherit root configuration via deterministic relative paths using the `extends` property in `biome.json` (e.g., `"extends": ["../../biome.json"]`).
- Engineers MUST enable native VCS integration (`vcs: { enabled: true, clientKind: "git", useIgnoreFile: true }`) to align Biome ignore behavior with `.gitignore` and enable `biome check --changed` in CI pipelines.
- Inline rule suppressions MUST follow the exact format `// biome-ignore <group>/<rule>: <explanation>` and MUST include a non-empty, actionable explanation.
- Engineers MUST NOT use legacy ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) within codebases managed by Biome.
- Root configurations MUST declare explicit schema validations via `$schema: "https://biomejs.dev/schemas/1.9.4/schema.json"` to ensure deterministic parsing and flag deprecated keys.
- Overrides for generated, third-party, or artifact paths MUST be configured via the top-level `files.ignore` array rather than ad-hoc nested exclusions.

## Bad vs Good Implementations
### Root and Child Biome Configuration with VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` pin, missing `vcs` integration block, and missing root configuration inheritance structure. Biome will traverse files ignored by Git and miss incremental changed-file CI optimizations.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space"
  }
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly declares schema version 1.9.4, activates Git VCS-aware file resolution respecting `.gitignore`, sets global formatting invariants, and enables recommended lint rules.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true,
    "includes": ["apps/**", "packages/**"]
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineEnding": "lf",
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```

### Deterministic Rule Suppression Syntax with Mandatory Justification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The first example uses dead ESLint syntax ignored by Biome. The second example uses Biome suppression without the mandatory colon and rationale statement.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const payload: any = JSON.parse(rawPayload);

// biome-ignore lint/suspicious/noExplicitAny
let metadata: any = null;
```

#### Production Standard (Correct)
> **Standard**: Adheres strictly to the Biome 1.9 suppression specification: specifies rule group and name followed by a mandatory explanation describing the technical constraint.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Upstream third-party webhook payload schema is unversioned and dynamic
const payload: any = JSON.parse(rawPayload);

// Prefer strongly typed unknown over any where possible
let metadata: unknown = null;
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Protocol MCP
Exposes Biome diagnostic checks, AST inspection, and deterministic auto-formatting to coding agents.
Recommended Agent Skills (askills.dev)

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

Biome 1.9 CLI Tool
Runs `biome check --write --changed` and `biome lint --error-on-warnings` inside local workspaces and CI workflows.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions

Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance across monorepo boundaries in Biome 1.9, mandating Git-backed VCS integration for incremental CI passes and strict inline suppression syntax with mandatory human-readable justification. Prevents silent drift between formatting and linting engines while eliminating unverified blanket suppression comments. 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 configuration drift with undocumented blanket lint suppressions and non-VCS aware CI runs 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 configuration drift with undocumented blanket lint suppressions and non-VCS aware CI runsCritical
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 packages MUST inherit root configuration via deterministic relative paths using the `extends` property in `biome.json` (e.g., `"extends"

Monorepo packages MUST inherit root configuration via deterministic relative paths using the `extends` property in `biome.json` (e.g., `"extends": ["../../biome.json"]`).

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 enable native VCS integration (`vcs

Engineers MUST enable native VCS integration (`vcs: { enabled: true, clientKind: "git", useIgnoreFile: true }`) to align Biome ignore behavior with `.gitignore` and enable `biome check --changed` in CI 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.
3

Inline rule suppressions MUST follow the exact format `// biome-ignore <group>/<rule>

Inline rule suppressions MUST follow the exact format `// biome-ignore <group>/<rule>: <explanation>` and MUST include a non-empty, actionable 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

Engineers MUST NOT use legacy ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) within codebases managed by Biome.

Engineers MUST NOT use legacy ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) within codebases managed by Biome.

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

Root configurations MUST declare explicit schema validations via `$schema

Root configurations MUST declare explicit schema validations via `$schema: "https://biomejs.dev/schemas/1.9.4/schema.json"` to ensure deterministic parsing and flag deprecated keys.

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

Overrides for generated, third-party, or artifact paths MUST be configured via the top-level `files.ignore` array rather than ad-hoc nested exclusions.

Overrides for generated, third-party, or artifact paths MUST be configured via the top-level `files.ignore` array rather than ad-hoc nested exclusions.

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 Deterministic Biome 1.9 Inheritance, VCS-Aware Formatting, and Rule Suppressions critical for AI coding assistants?

Enforces strict configuration inheritance across monorepo boundaries in Biome 1.9, mandating Git-backed VCS integration for incremental CI passes and strict inline suppression syntax with mandatory human-readable justification. Prevents silent drift between formatting and linting engines while eliminating unverified blanket suppression comments. 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 configuration drift with undocumented blanket lint suppressions and non-VCS aware CI runs) 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

Deterministic