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

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

Enforces strict Biome 1.9 configuration architecture across monorepos and standalone repositories. Mandates native VCS ignore file synchronization, explicit configuration inheritance hierarchies via extends, and deterministic, fully-qualified suppression comments with mandatory explanatory text.

Prohibited Anti-Pattern: Unannotated inline bypasses, orphaned .gitignore parity drift, and legacy ESLint/Prettier directive bleed-through.

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 Suppressions - Enforces strict Biome 1.9 configuration architecture across monorepos and standalone repositories. Mandates native VCS ignore file synchronization, explicit configuration inheritance hierarchies via extends, and deterministic, fully-qualified suppression comments with mandatory explanatory text.
globs: biome.json, biome.jsonc, **/*.ts, **/*.tsx, **/*.js, **/*.jsx, **/*.json
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-configuration-inheritance-and-deterministic-suppressions"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unannotated inline bypasses, orphaned .gitignore parity drift, and legacy ESLint/Prettier directive bleed-through.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 tooling standards across frontend codebases. Enforce deterministic configuration inheritance, ensure Biome relies on VCS ignore integration rather than duplicated ignore arrays, and prohibit vague, malformed, or legacy ESLint/Prettier suppression comments.

## Strict Guidelines
- Engineers MUST ALWAYS reference the exact Biome schema URL matching the engine version ($schema: 'https://biomejs.dev/schemas/1.9.4/schema.json') in all biome.json or biome.jsonc files.
- Engineers MUST configure the 'vcs' block with 'enabled: true', 'clientKind: "git"', and 'useIgnoreFile: true' to prevent configuration drift between Git and Biome.
- Engineers MUST NOT duplicate filesystem ignore patterns in 'files.ignore' when those files are already tracked in '.gitignore'.
- Monorepo package configurations MUST extend root configurations via deterministic relative paths using the 'extends' array (e.g., 'extends': ["../../biome.json"]).
- Inline suppressions MUST strictly use the format '// biome-ignore <category>/<group>/<rule>: <explanation>' or '// biome-ignore-all <category>/<group>/<rule>: <explanation>' with a non-empty, actionable explanation.
- Engineers MUST NEVER use legacy directives such as '// eslint-disable', '// eslint-disable-next-line', or '@ts-ignore' without Biome parity.
- CI validation MUST run 'biome check --error-on-warnings' to prevent suppression abuse and ensure zero unhandled lint deviations.

## Bad vs Good Implementations
### Deterministic Biome 1.9 Configuration with VCS Sync and Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Outdated schema, lacks VCS integration (causing ignore drift with git), manually duplicates standard gitignore targets, and lacks configuration inheritance setup for monorepos.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.0.0/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Uses the modern 1.9.4 schema, inherits base workspace rules via extends, and delegates ignore tracking to git via the native vcs engine configuration.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.json"],
  "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 Inline Lint Rule Suppression

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Employs an ignored legacy ESLint directive that Biome skips, followed by a Biome suppression missing the mandatory explanation string.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const raw: any = JSON.parse(input);
  return raw;
}
```

#### Production Standard (Correct)
> **Standard**: Replaces inert ESLint comments with fully qualified Biome suppression syntax containing clear, auditable explanations.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Required for polymorphic boundary payload before Zod validation
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny: Intermediary deserialization variable matches unverified external contract
  const raw: any = JSON.parse(input);
  return raw;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Bridge
Language server MCP integration providing deterministic linting, formatting, and quick-fix diagnostics directly to coding agents.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --apply-unsafe' and 'biome check --error-on-warnings' for deterministic repository auditing.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppressions defines an industrial-grade behavioral standard for frontend engineering. Enforces strict Biome 1.9 configuration architecture across monorepos and standalone repositories. Mandates native VCS ignore file synchronization, explicit configuration inheritance hierarchies via extends, and deterministic, fully-qualified suppression comments with mandatory explanatory text. 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: Unannotated inline bypasses, orphaned .gitignore parity drift, and legacy ESLint/Prettier directive bleed-through. 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 DriftUnannotated inline bypasses, orphaned .gitignore parity drift, and legacy ESLint/Prettier directive bleed-through.Critical
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 reference the exact Biome schema URL matching the engine version ($schema

Engineers MUST ALWAYS reference the exact Biome schema URL matching the engine version ($schema: 'https://biomejs.dev/schemas/1.9.4/schema.json') in all biome.json or biome.jsonc files.

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 configure the 'vcs' block with 'enabled

Engineers MUST configure the 'vcs' block with 'enabled: true', 'clientKind: "git"', and 'useIgnoreFile: true' to prevent configuration drift between Git and 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.
3

Engineers MUST NOT duplicate filesystem ignore patterns in 'files.ignore' when those files are already tracked in '.gitignore'.

Engineers MUST NOT duplicate filesystem ignore patterns in 'files.ignore' when those files are already tracked in '.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.
4

Monorepo package configurations MUST extend root configurations via deterministic relative paths using the 'extends' array (e.g., 'extends'

Monorepo package configurations MUST extend root configurations via deterministic relative paths using the 'extends' array (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.
5

Inline suppressions MUST strictly use the format '// biome-ignore <category>/<group>/<rule>

Inline suppressions MUST strictly use the format '// biome-ignore <category>/<group>/<rule>: <explanation>' or '// biome-ignore-all <category>/<group>/<rule>: <explanation>' with 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.
6

Engineers MUST NEVER use legacy directives such as '// eslint-disable', '// eslint-disable-next-line', or '@ts-ignore' without Biome parity.

Engineers MUST NEVER use legacy directives such as '// eslint-disable', '// eslint-disable-next-line', or '@ts-ignore' without Biome 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.
7

CI validation MUST run 'biome check --error-on-warnings' to prevent suppression abuse and ensure zero unhandled lint deviations.

CI validation MUST run 'biome check --error-on-warnings' to prevent suppression abuse and ensure zero unhandled lint deviations.

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 Suppressions critical for AI coding assistants?

Enforces strict Biome 1.9 configuration architecture across monorepos and standalone repositories. Mandates native VCS ignore file synchronization, explicit configuration inheritance hierarchies via extends, and deterministic, fully-qualified suppression comments with mandatory explanatory text. 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 (Unannotated inline bypasses, orphaned .gitignore parity drift, and legacy ESLint/Prettier directive bleed-through.) 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