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

Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions

Enforces strict configuration inheritance via the 'extends' resolution schema, mandatory Git VCS integration with ignorefile honoring, and deterministic inline suppression comment syntax in Biome 1.9. Disallows deprecated ESLint-style suppressions and unanchored root-level overrides in monorepo workspaces.

Prohibited Anti-Pattern: Unpinned Configuration Drift, ESLint Suppression Remnants, and Untracked File Linter Failures

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions - Enforces strict configuration inheritance via the 'extends' resolution schema, mandatory Git VCS integration with ignorefile honoring, and deterministic inline suppression comment syntax in Biome 1.9. Disallows deprecated ESLint-style suppressions and unanchored root-level overrides in monorepo workspaces.
globs: biome.json, biome.jsonc, **/*.biome.json, **/*.biome.jsonc, src/**/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-v1-9-monorepo-config-and-suppression-guardrail"
---

# Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unpinned Configuration Drift, ESLint Suppression Remnants, and Untracked File Linter Failures

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 Single-Binary Linter & Formatter invariants across the codebase. You must enforce explicit configuration hierarchy across monorepo boundaries using 'extends', activate native VCS Git integration to honor '.gitignore', and reject non-Biome suppression directives (such as eslint-disable or prettier-ignore). Every code suppression MUST adhere strictly to the format: `// biome-ignore <category>/<ruleName>: <mandatory explanatory reason>`.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent parsing untracked or binary artifacts.
- Engineers MUST ALWAYS use the structured suppression format `// biome-ignore <group>/<rule>: <explanation>` or `/* biome-ignore <group>/<rule>: <explanation> */` with a mandatory technical justification.
- Engineers MUST NOT use legacy comments like `// eslint-disable`, `// eslint-disable-next-line`, or `// @ts-ignore` as substitutions for Biome diagnostics.
- Monorepo packages MUST use relative path `extends` in package-level `biome.json` configurations instead of duplicating top-level rule sets.
- Engineers MUST explicitly set `$schema` to a version-pinned Biome 1.9 URI (`https://biomejs.dev/schemas/1.9.4/schema.json`) in all `biome.json` files for IDE schema enforcement.

## Bad vs Good Implementations
### Root Configuration: VCS Integration and Schema Declaration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` locks developers into ambiguous versions. Missing `vcs` block causes Biome to ignore `.gitignore`, resulting in accidental linting of `dist/`, build caches, and node_modules.
```json
{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly binds the 1.9.4 schema and utilizes native Git VCS integration to honor workspace ignore lists deterministically.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  }
}
```

### Inline Rule Suppression: Syntax and Mandatory Reason

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: ESLint directive is ignored by Biome. The Biome ignore comment lacks a colon and mandatory technical justification, failing Biome 1.9 suppression format checks.
```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**: Applies standard `// biome-ignore <group>/<rule>: <explanation>` syntax with an explicit architectural explanation, satisfying Biome parser validation.
```typescript
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Required for legacy untyped gateway payload compatibility
  return JSON.parse(input) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Git Context Server
Inspects git staging, untracked files, and working tree diffs to validate Biome VCS integration.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --write' and 'biome ci' across target packages via single-binary native speeds.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions

Biome 1.9 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance via the 'extends' resolution schema, mandatory Git VCS integration with ignorefile honoring, and deterministic inline suppression comment syntax in Biome 1.9. Disallows deprecated ESLint-style suppressions and unanchored root-level overrides in monorepo workspaces. 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 Configuration Drift, ESLint Suppression Remnants, and Untracked File Linter Failures 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 Configuration Drift, ESLint Suppression Remnants, and Untracked File Linter FailuresCritical
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 the root `biome.json` to prevent parsing untracked or binary artifacts.

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 use the structured suppression format `// biome-ignore <group>/<rule>

Engineers MUST ALWAYS use the structured suppression format `// biome-ignore <group>/<rule>: <explanation>` or `/* biome-ignore <group>/<rule>: <explanation> */` with a mandatory technical justification.

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 legacy comments like `// eslint-disable`, `// eslint-disable-next-line`, or `// @ts-ignore` as substitutions for Biome diagnostics.

Engineers MUST NOT use legacy comments like `// eslint-disable`, `// eslint-disable-next-line`, or `// @ts-ignore` as substitutions for Biome diagnostics.

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

Monorepo packages MUST use relative path `extends` in package-level `biome.json` configurations instead of duplicating top-level rule sets.

Monorepo packages MUST use relative path `extends` in package-level `biome.json` configurations instead of duplicating top-level rule sets.

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 explicitly set `$schema` to a version-pinned Biome 1.9 URI (`https

Engineers MUST explicitly set `$schema` to a version-pinned Biome 1.9 URI (`https://biomejs.dev/schemas/1.9.4/schema.json`) in all `biome.json` files for IDE schema enforcement.

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 Deterministic Configuration Inheritance, VCS Integration, and Structured Suppressions critical for AI coding assistants?

Enforces strict configuration inheritance via the 'extends' resolution schema, mandatory Git VCS integration with ignorefile honoring, and deterministic inline suppression comment syntax in Biome 1.9. Disallows deprecated ESLint-style suppressions and unanchored root-level overrides in monorepo workspaces. 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 Configuration Drift, ESLint Suppression Remnants, and Untracked File Linter Failures) 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