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

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression

Enforces strict configuration schema inheritance via `extends`, deterministic Git-backed ignore semantics, and canonical Biome 1.9 suppression comment syntax. Eliminates silent linter bypassing, conflicting nested formatting rules, and redundant CI parsing passes across modern TypeScript monorepos.

Prohibited Anti-Pattern: Ad-Hoc Suppressions, Unanchored Root Configs, and Git-Ignored File Drift

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression - Enforces strict configuration schema inheritance via `extends`, deterministic Git-backed ignore semantics, and canonical Biome 1.9 suppression comment syntax. Eliminates silent linter bypassing, conflicting nested formatting rules, and redundant CI parsing passes across modern TypeScript monorepos.
globs: biome.json, biome.jsonc, apps/**/*.{ts,tsx}, packages/**/*.{ts,tsx}, src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-monorepo-vcs-suppression-guardrails"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-Hoc Suppressions, Unanchored Root Configs, and Git-Ignored File Drift

## System Constraints
You are a Principal Platform Engineer enforcing Biome 1.9 as the singular toolchain for linting and formatting. You must ensure all configurations leverage typed extends semantics, VCS-backed file tree discovery, and formal suppression comments with explicit reasoning, preventing runtime lint drift across package workspaces.

## Strict Guidelines
- Engineers MUST ALWAYS declare `vcs.enabled: true` and `vcs.clientKind: "git"` in root `biome.json` to enforce deterministic discovery honoring `.gitignore`.
- Engineers MUST NEVER use ESLint-style suppression comments (`// eslint-disable-next-line`); only official Biome suppression syntax `// biome-ignore <group>/<rule>: <explanation>` is permitted.
- Suppression comments MUST ALWAYS include a trailing explanation reason; bare `// biome-ignore <rule>` without colon and reason is rejected.
- Workspace packages MUST extend shared base configurations using relative paths (`extends: ["../../biome.base.json"]`) or package exports, never redefining global formatting rules in package leaves.
- Engineers MUST configure `files.ignoreUnknown: true` to prevent Biome from halting on unsupported binary or vendor asset extensions in mixed repositories.
- CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` with `--staged` or `--changed` on pull requests to leverage the Rust graph diffing engine.

## Bad vs Good Implementations
### Deterministic Suppression Syntax with Explicit Architectural Justification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: ESLint suppressions are ignored by Biome, causing CI failures. Bare biome-ignore comments without an explicit explanation rationale violate maintainability standards and prevent auditability.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const untypedLegacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny
const anotherPayload: any = JSON.parse(rawInput);
```

#### Production Standard (Correct)
> **Standard**: Uses the canonical Biome 1.9 suppression syntax with rule group, rule name, and a mandatory colon-delimited architectural reason explaining why the invariant is bypassed.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Legacy CDC webhook payload without schema guarantees
const untypedLegacyPayload: any = JSON.parse(rawInput);
```

### Biome Monorepo Root Configuration with VCS Integration and Schema Validation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing $schema validation, no VCS integration (leading to processing git-ignored files), and no base extension semantics for sub-packages.
```json
{
  "formatter": {
    "enabled": true,
    "indentStyle": "space"
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Provides schema validation, binds discovery directly to Git-tracked trees, avoids indexing binary files, and standardizes workspace-level lint invariants.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true,
    "includes": ["src/**", "packages/**", "apps/**"]
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Platform Diagnostics MCP
Executes fast AST-level diagnostics, formatting runs, and schema checks directly via the Biome daemon.
Recommended Agent Skills (askills.dev)

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

Biome Staged Check Skill
Runs targeted Biome 1.9 check commands restricted to staged or branch-changed files in high-velocity PR pipelines.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration schema inheritance via `extends`, deterministic Git-backed ignore semantics, and canonical Biome 1.9 suppression comment syntax. Eliminates silent linter bypassing, conflicting nested formatting rules, and redundant CI parsing passes across modern TypeScript 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: Ad-Hoc Suppressions, Unanchored Root Configs, and Git-Ignored File Drift 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 DriftAd-Hoc Suppressions, Unanchored Root Configs, and Git-Ignored File DriftCritical
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 declare `vcs.enabled

Engineers MUST ALWAYS declare `vcs.enabled: true` and `vcs.clientKind: "git"` in root `biome.json` to enforce deterministic discovery honoring `.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.
2

Engineers MUST NEVER use ESLint-style suppression comments (`// eslint-disable-next-line`)

Engineers MUST NEVER use ESLint-style suppression comments (`// eslint-disable-next-line`); only official Biome suppression syntax `// biome-ignore <group>/<rule>: <explanation>` is permitted.

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

Suppression comments MUST ALWAYS include a trailing explanation reason

Suppression comments MUST ALWAYS include a trailing explanation reason; bare `// biome-ignore <rule>` without colon and reason is rejected.

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

Workspace packages MUST extend shared base configurations using relative paths (`extends

Workspace packages MUST extend shared base configurations using relative paths (`extends: ["../../biome.base.json"]`) or package exports, never redefining global formatting rules in package leaves.

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 configure `files.ignoreUnknown

Engineers MUST configure `files.ignoreUnknown: true` to prevent Biome from halting on unsupported binary or vendor asset extensions in mixed 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

CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` with `--staged` or `--changed` on pull requests to leverage the Rust graph diffing engine.

CI pipelines MUST execute `biome check --diagnostic-level=error --error-on-warnings` with `--staged` or `--changed` on pull requests to leverage the Rust graph diffing engine.

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

Enforces strict configuration schema inheritance via `extends`, deterministic Git-backed ignore semantics, and canonical Biome 1.9 suppression comment syntax. Eliminates silent linter bypassing, conflicting nested formatting rules, and redundant CI parsing passes across modern TypeScript 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 (Ad-Hoc Suppressions, Unanchored Root Configs, and Git-Ignored File Drift) 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