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-configuration-inheritance-and-deterministic-suppression

Biome 1.9 Invariant Configuration Inheritance, VCS Synchronization, and Deterministic Rule Suppression

Enforces strict configuration inheritance across monorepo boundaries using Biome 1.9 extends mechanisms, ensures native Git ignore synchronization via VCS settings, and mandates deterministic, explanation-backed suppression comment syntax. Prevents configuration drift, unformatted vendor leaks, and silent lint exemptions across TypeScript and React codebases.

Prohibited Anti-Pattern: Fragmented Rootless Configurations, Ignored VCS Boundaries, and Naked ESLint-Style Rule Disables

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Invariant Configuration Inheritance, VCS Synchronization, and Deterministic Rule Suppression - Enforces strict configuration inheritance across monorepo boundaries using Biome 1.9 extends mechanisms, ensures native Git ignore synchronization via VCS settings, and mandates deterministic, explanation-backed suppression comment syntax. Prevents configuration drift, unformatted vendor leaks, and silent lint exemptions across TypeScript and React codebases.
globs: biome.json, biome.jsonc, apps/**/*.{ts,tsx,json}, packages/**/*.{ts,tsx,json}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-configuration-inheritance-and-deterministic-suppression"
---

# Biome 1.9 Invariant Configuration Inheritance, VCS Synchronization, and Deterministic Rule Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented Rootless Configurations, Ignored VCS Boundaries, and Naked ESLint-Style Rule Disables

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 single-binary toolchain standards. Mandate invariant configuration inheritance via extends across monorepo packages, enforce VCS ignore synchronization (vcs.clientKind = 'git' and useIgnoreFile = true), and mandate deterministic suppression syntax (`// biome-ignore <group>/<rule>: <explanation>`). Disallow legacy ESLint/Prettier suppressions and unexplained rule bypasses.

## Strict Guidelines
- Engineers MUST configure package-level `biome.json` files to extend root configuration via `"extends": ["../../biome.json"]` rather than redefining rules in isolated package silos.
- Engineers MUST ALWAYS enable VCS integration in root `biome.json` with `"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }` to guarantee `.gitignore` parity.
- Engineers MUST NOT use legacy `// eslint-disable` or `// prettier-ignore` comment directives; all inline suppressions MUST follow the exact Biome format `// biome-ignore <group>/<rule>: <deterministic rationale>`.
- Suppression comments MUST ALWAYS include a trailing explanation token separated by a colon (`: <reason>`); empty or unexplained suppressions are prohibited.
- Root configurations MUST lock `$schema` to the exact Biome 1.9 schema URL (`https://biomejs.dev/schemas/1.9.4/schema.json`) to prevent structural degradation during agent-driven refactors.

## Bad vs Good Implementations
### Biome Configuration Inheritance & VCS Setup

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure VCS integration (forcing manual duplication of `.gitignore` paths), uses an outdated schema, and omits root inheritance structures required for monorepos.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Leverages Biome 1.9 native git ignore synchronization (`vcs.useIgnoreFile`), pins the 1.9.4 schema, and defines a robust base configuration ready for package-level extension.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Contains invalid ESLint directives that Biome ignores, and uses a Biome suppression missing the mandatory deterministic explanation token.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function processData(payload: any): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const raw: any = payload;
  return raw;
}
```

#### Production Standard (Correct)
> **Standard**: Uses canonical Biome suppression syntax with mandatory justification colons and clear explanations for why the invariant is temporarily bypassed.
```typescript
/**
 * Process untrusted boundary payloads before schema validation.
 */
// biome-ignore lint/suspicious/noExplicitAny: Raw webhook inputs lack compile-time schema before validation step
export function processData(payload: any): Record<string, unknown> {
  // biome-ignore lint/suspicious/noExplicitAny: Internal casting required to interface with third-party legacy SDK response
  const raw = payload as any;
  return typeof raw === "object" && raw !== null ? { ...raw } : {};
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server MCP
Provides language server protocol integration for real-time Biome diagnostics, format triggers, and code actions.
Recommended Agent Skills (askills.dev)

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

Biome CLI Task Runner
Executes biome check, format, and lint commands with --staged and --changed flags for rapid verification.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Invariant Configuration Inheritance, VCS Synchronization, and Deterministic Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration inheritance across monorepo boundaries using Biome 1.9 extends mechanisms, ensures native Git ignore synchronization via VCS settings, and mandates deterministic, explanation-backed suppression comment syntax. Prevents configuration drift, unformatted vendor leaks, and silent lint exemptions across TypeScript and React codebases. 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 Configurations, Ignored VCS Boundaries, and Naked ESLint-Style Rule Disables 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 Configurations, Ignored VCS Boundaries, and Naked ESLint-Style Rule DisablesCritical
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 configure package-level `biome.json` files to extend root configuration via `"extends"

Engineers MUST configure package-level `biome.json` files to extend root configuration via `"extends": ["../../biome.json"]` rather than redefining rules in isolated package silos.

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 enable VCS integration in root `biome.json` with `"vcs"

Engineers MUST ALWAYS enable VCS integration in root `biome.json` with `"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }` to guarantee `.gitignore` parity.

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 `// eslint-disable` or `// prettier-ignore` comment directives

Engineers MUST NOT use legacy `// eslint-disable` or `// prettier-ignore` comment directives; all inline suppressions MUST follow the exact Biome format `// biome-ignore <group>/<rule>: <deterministic 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

Suppression comments MUST ALWAYS include a trailing explanation token separated by a colon (`

Suppression comments MUST ALWAYS include a trailing explanation token separated by a colon (`: <reason>`); empty or unexplained suppressions are prohibited.

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 lock `$schema` to the exact Biome 1.9 schema URL (`https

Root configurations MUST lock `$schema` to the exact Biome 1.9 schema URL (`https://biomejs.dev/schemas/1.9.4/schema.json`) to prevent structural degradation during agent-driven refactors.

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 Invariant Configuration Inheritance, VCS Synchronization, and Deterministic Rule Suppression critical for AI coding assistants?

Enforces strict configuration inheritance across monorepo boundaries using Biome 1.9 extends mechanisms, ensures native Git ignore synchronization via VCS settings, and mandates deterministic, explanation-backed suppression comment syntax. Prevents configuration drift, unformatted vendor leaks, and silent lint exemptions across TypeScript and React codebases. 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 Configurations, Ignored VCS Boundaries, and Naked ESLint-Style Rule Disables) 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