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

Biome 1.9 Invariants: Configuration Inheritance, VCS Sync, and Deterministic Suppressions

Enforces deterministic linting and formatting invariants for Biome 1.9 across monorepos and frontend packages. Requires explicit VCS integration with Git ignore parity, validated configuration inheritance graphs, and strictly reasoned inline suppression syntax adhering to the 'biome-ignore <category>/<rule>: <rationale>' standard.

Prohibited Anti-Pattern: Unchecked artifact parsing from unlinked VCS ignores and unstructured, unreasoned inline suppressions.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Invariants: Configuration Inheritance, VCS Sync, and Deterministic Suppressions - Enforces deterministic linting and formatting invariants for Biome 1.9 across monorepos and frontend packages. Requires explicit VCS integration with Git ignore parity, validated configuration inheritance graphs, and strictly reasoned inline suppression syntax adhering to the 'biome-ignore <category>/<rule>: <rationale>' standard.
globs: biome.json, biome.jsonc, src/**/*.{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-vcs-inheritance-suppression-guardrails"
---

# Biome 1.9 Invariants: Configuration Inheritance, VCS Sync, and Deterministic Suppressions

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unchecked artifact parsing from unlinked VCS ignores and unstructured, unreasoned inline suppressions.

## System Constraints
You are a Principal Software Architect enforcing strict Biome 1.9 single-binary linter and formatter invariants. You must prevent configurations that bypass VCS ignore boundary checks, prevent ambiguous inheritance loops, and reject any code suppression that lacks a validated rule path and explicit engineering justification.

## Strict Guidelines
- Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json'/'biome.jsonc' to prevent parsing generated artifacts.
- Engineers MUST ALWAYS provide an explicit explanatory justification following a colon in suppression directives: '// biome-ignore <category>/<rule>: <reason>'.
- Engineers MUST NOT use legacy ESLint/Prettier suppression comments ('// eslint-disable', '/* prettier-ignore */') under any circumstances.
- Subpackages in monorepos MUST inherit root configuration via the 'extends' array using deterministic relative paths ('extends': ["../../biome.json"]).
- Code MUST NEVER suppress entire categories or file-level scopes using wildcard syntax when targeted single-rule suppressions suffice.
- Configurations SHOULD explicitly declare '$schema': 'https://biomejs.dev/schemas/1.9.4/schema.json' to ensure deterministic schema validation in IDE tooling.

## Bad vs Good Implementations
### Biome 1.9 Root Configuration and VCS Sync

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits schema validation, does not inherit .gitignore rules via the VCS engine (causing node_modules/dist/build scans), and fails to establish deterministic baseline configurations.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly declares the 1.9 schema, leverages native Git ignore integration to prevent phantom linting of build artifacts, and sets deterministic baseline rules.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Inline Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses incompatible legacy ESLint suppression comments and includes a Biome suppression that lacks the mandatory colon and descriptive engineering rationale.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(payload: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(payload) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres to the strict Biome 1.9 directive standard: specifies exact rule namespace ('lint/suspicious/noExplicitAny') followed by a colon and a defensible architectural explanation.
```typescript
export function deserializePayload(payload: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Dynamic untyped WebSocket payload requiring runtime Zod validation
  return JSON.parse(payload) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Model Context Protocol Filesystem Server
Enables direct workspace inspection and validation of nested biome.json and .gitignore configurations across monorepo packages.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --write --diagnostic-level=error' directly against staged changes to ensure local and CI formatting/linting parity.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Invariants: Configuration Inheritance, VCS Sync, and Deterministic Suppressions

Biome 1.9 Invariants: Configuration Inheritance, VCS Sync, and Deterministic Suppressions defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic linting and formatting invariants for Biome 1.9 across monorepos and frontend packages. Requires explicit VCS integration with Git ignore parity, validated configuration inheritance graphs, and strictly reasoned inline suppression syntax adhering to the 'biome-ignore <category>/<rule>: <rationale>' standard. 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: Unchecked artifact parsing from unlinked VCS ignores and unstructured, unreasoned inline suppressions. 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 DriftUnchecked artifact parsing from unlinked VCS ignores and unstructured, unreasoned inline suppressions.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.enabled

Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json'/'biome.jsonc' to prevent parsing generated 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 provide an explicit explanatory justification following a colon in suppression directives

Engineers MUST ALWAYS provide an explicit explanatory justification following a colon in suppression directives: '// biome-ignore <category>/<rule>: <reason>'.

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/Prettier suppression comments ('// eslint-disable', '/* prettier-ignore */') under any circumstances.

Engineers MUST NOT use legacy ESLint/Prettier suppression comments ('// eslint-disable', '/* prettier-ignore */') under any circumstances.

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

Subpackages in monorepos MUST inherit root configuration via the 'extends' array using deterministic relative paths ('extends'

Subpackages in monorepos MUST inherit root configuration via the 'extends' array using deterministic relative paths ('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

Code MUST NEVER suppress entire categories or file-level scopes using wildcard syntax when targeted single-rule suppressions suffice.

Code MUST NEVER suppress entire categories or file-level scopes using wildcard syntax when targeted single-rule suppressions suffice.

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

Configurations SHOULD explicitly declare '$schema'

Configurations SHOULD explicitly declare '$schema': 'https://biomejs.dev/schemas/1.9.4/schema.json' to ensure deterministic schema validation in IDE tooling.

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

Enforces deterministic linting and formatting invariants for Biome 1.9 across monorepos and frontend packages. Requires explicit VCS integration with Git ignore parity, validated configuration inheritance graphs, and strictly reasoned inline suppression syntax adhering to the 'biome-ignore <category>/<rule>: <rationale>' standard. 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 (Unchecked artifact parsing from unlinked VCS ignores and unstructured, unreasoned inline suppressions.) 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