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-config-inheritance-vcs-suppression

Biome 1.9 Configuration Inheritance, VCS Synchronization, and Deterministic Suppression Standards

Enforces strict architecture for Biome 1.9 across monorepos and frontend packages. Mandates clean configuration inheritance via 'extends', native Git VCS integration to eliminate redundant ignore files, and deterministic, fully justified inline suppression syntax.

Prohibited Anti-Pattern: Mixing legacy ESLint/Prettier suppression comments, duplicate file ignore lists, and unanchored Biome rule suppressions without justification.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Synchronization, and Deterministic Suppression Standards - Enforces strict architecture for Biome 1.9 across monorepos and frontend packages. Mandates clean configuration inheritance via 'extends', native Git VCS integration to eliminate redundant ignore files, and deterministic, fully justified inline suppression syntax.
globs: biome.json, biome.jsonc, **/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-config-inheritance-vcs-suppression"
---

# Biome 1.9 Configuration Inheritance, VCS Synchronization, and Deterministic Suppression Standards

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Mixing legacy ESLint/Prettier suppression comments, duplicate file ignore lists, and unanchored Biome rule suppressions without justification.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 toolchain standards. Invalidate legacy ESLint/Prettier suppressions, verify deterministic monorepo configuration inheritance, mandate native Git VCS ignore parsing, and reject any biome-ignore directive lacking an explicit rule identifier or descriptive justification.

## Strict Guidelines
- Engineers MUST ALWAYS configure VCS integration in the root 'biome.json' using '"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }' instead of duplicating patterns in 'files.ignore'.
- Engineers MUST ALWAYS extend shared configs deterministically using relative file paths in workspace packages via '"extends": ["../../biome.json"]'.
- Engineers MUST NOT use legacy comments such as '// eslint-disable', '// eslint-disable-next-line', or '// prettier-ignore' in codebases managed by Biome.
- Engineers MUST format all suppressions strictly with the canonical format: '// biome-ignore <group>/<rule>: <detailed justification why this cannot be resolved>'.
- Code SHOULD leverage the Biome 1.9 JSON schema '$schema' URL pointing to 'https://biomejs.dev/schemas/1.9.4/schema.json' to ensure IDE validation and strict config typing.
- Services MUST enable 'linter.enabled: true' and 'formatter.enabled: true' at the root and override only package-specific rule levels or overrides in leaf 'biome.json' files.
- Components NEVER suppress entire categories (e.g., '// biome-ignore lint: reason') or use bare suppression '// biome-ignore' without specifying rule name and reasoning.

## Bad vs Good Implementations
### Biome 1.9 Configuration: Monorepo Inheritance & VCS Binding

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Outdated schema version, missing VCS block causing duplicate tracking between .gitignore and files.ignore, and duplicate rule definitions in leaf package instead of inheriting from workspace root.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.8.0/schema.json",
  "files": {
    "ignore": ["node_modules/**", "dist/**", ".turbo/**", "coverage/**", ".next/**"]
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space"
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Uses Biome 1.9 schema, delegates file exclusion to git via 'vcs' block, and inherits baseline rules from root 'biome.json'.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.json"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "single",
      "semicolons": "always"
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses legacy ESLint directive ignored by Biome, and uses a Biome suppression lacking the required colon-separated explanation.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  const temp: any = JSON.parse(input);
  return temp;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres to Biome 1.9 suppression syntax '// biome-ignore <group>/<rule>: <explanation>' providing clear auditability and type narrowing.
```typescript
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Legacy schema ingress; payload validated downstream via Zod schema safeParse
  const rawData: any = JSON.parse(input);
  return rawData;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Runner
Executes Biome checks, formatting, and linting passes natively within the AI agent runtime.
Recommended Agent Skills (askills.dev)

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

Biome Staged Check
Runs 'biome check --write --staged --vcs-client-kind=git' to format, lint, and check imports deterministically before commit.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Synchronization, and Deterministic Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces strict architecture for Biome 1.9 across monorepos and frontend packages. Mandates clean configuration inheritance via 'extends', native Git VCS integration to eliminate redundant ignore files, and deterministic, fully justified inline suppression syntax. 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: Mixing legacy ESLint/Prettier suppression comments, duplicate file ignore lists, and unanchored Biome rule suppressions without justification. 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 DriftMixing legacy ESLint/Prettier suppression comments, duplicate file ignore lists, and unanchored Biome rule suppressions without justification.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 configure VCS integration in the root 'biome.json' using '"vcs"

Engineers MUST ALWAYS configure VCS integration in the root 'biome.json' using '"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }' instead of duplicating patterns in 'files.ignore'.

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 extend shared configs deterministically using relative file paths in workspace packages via '"extends"

Engineers MUST ALWAYS extend shared configs deterministically using relative file paths in workspace packages via '"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.
3

Engineers MUST NOT use legacy comments such as '// eslint-disable', '// eslint-disable-next-line', or '// prettier-ignore' in codebases managed by Biome.

Engineers MUST NOT use legacy comments such as '// eslint-disable', '// eslint-disable-next-line', or '// prettier-ignore' in 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.
4

Engineers MUST format all suppressions strictly with the canonical format

Engineers MUST format all suppressions strictly with the canonical format: '// biome-ignore <group>/<rule>: <detailed justification why this cannot be resolved>'.

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

Code SHOULD leverage the Biome 1.9 JSON schema '$schema' URL pointing to 'https

Code SHOULD leverage the Biome 1.9 JSON schema '$schema' URL pointing to 'https://biomejs.dev/schemas/1.9.4/schema.json' to ensure IDE validation and strict config typing.

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

Services MUST enable 'linter.enabled

Services MUST enable 'linter.enabled: true' and 'formatter.enabled: true' at the root and override only package-specific rule levels or overrides in leaf 'biome.json' 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.
7

Components NEVER suppress entire categories (e.g., '// biome-ignore lint

Components NEVER suppress entire categories (e.g., '// biome-ignore lint: reason') or use bare suppression '// biome-ignore' without specifying rule name and reasoning.

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 Synchronization, and Deterministic Suppression Standards critical for AI coding assistants?

Enforces strict architecture for Biome 1.9 across monorepos and frontend packages. Mandates clean configuration inheritance via 'extends', native Git VCS integration to eliminate redundant ignore files, and deterministic, fully justified inline suppression syntax. 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 (Mixing legacy ESLint/Prettier suppression comments, duplicate file ignore lists, and unanchored Biome rule suppressions without justification.) 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