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-vcs-inheritance-deterministic-suppression-standard

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression Standard

Enforces deterministic formatting and linting architecture via Biome 1.9 single-binary tooling across enterprise monorepos. Mandates standardized VCS ignore synchronization, centralized configuration inheritance, and fully qualified, documented suppression comments. Eliminates configuration drift, unignored build artifact pollution, and undocumented lint bypasses in CI/CD pipelines.

Prohibited Anti-Pattern: Ad-hoc ESLint-style suppressions, detached .gitignore parsing, and fragmented monorepo Biome configurations.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression Standard - Enforces deterministic formatting and linting architecture via Biome 1.9 single-binary tooling across enterprise monorepos. Mandates standardized VCS ignore synchronization, centralized configuration inheritance, and fully qualified, documented suppression comments. Eliminates configuration drift, unignored build artifact pollution, and undocumented lint bypasses in CI/CD pipelines.
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-vcs-inheritance-deterministic-suppression-standard"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-hoc ESLint-style suppressions, detached .gitignore parsing, and fragmented monorepo Biome configurations.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 invariants across frontend projects. All linting and formatting MUST use Biome's unified single-binary toolchain. You must reject legacy ESLint/Prettier suppressions, require mandatory explanations for Biome suppressions, enforce VCS integration (`useIgnoreFile: true`), and ensure deterministic configuration inheritance across monorepo packages.

## Strict Guidelines
- Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to mirror `.gitignore` semantics natively.
- Engineers MUST ALWAYS provide a mandatory, human-readable justification when using suppression comments: `// biome-ignore <category>/<rule>: <explanation>`.
- Engineers MUST NOT use unanchored, legacy, or bare suppression directives such as `// eslint-disable-next-line` or bare `// biome-ignore <rule>` without a colon and justification.
- Monorepo packages MUST inherit root standards using `extends: ["../../biome.json"]` or shared preset packages, overriding only package-specific path overrides.
- CI pipelines MUST execute `biome ci --error-on-warnings` to prevent drift and treat lint warnings as blocking gates on touched pull request files.

## Bad vs Good Implementations
### Root Biome Configuration: VCS Integration & Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure native VCS integration, requiring manual duplicate maintenance of ignored paths alongside .gitignore, leading to accidental indexing of build artifacts and divergent CI behavior.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".next"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Natively integrates Git VCS resolution, automatically honoring .gitignore patterns while establishing deterministic root defaults for workspace inheritance.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": false
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses legacy ESLint directive ignored by Biome, followed by a bare Biome suppression lacking the mandatory colon separator and explanatory justification required by Biome 1.9.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const payload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny
const fallback: any = {};
```

#### Production Standard (Correct)
> **Standard**: Adheres strictly to the Biome 1.9 suppression format `// biome-ignore <group>/<rule>: <rationale>`, preserving auditability and enabling programmatic rule verification.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External webhook payload schema is dynamic and validated downstream via Zod
const payload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny: Third-party SDK returns an un-narrowed dictionary type
const fallback: any = {};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem Server
Access and parse root biome.json and workspace package configs to ensure inheritance integrity.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes single-binary biome check, biome ci, and deterministic formatting diagnostics directly within the agent workspace.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression Standard

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic formatting and linting architecture via Biome 1.9 single-binary tooling across enterprise monorepos. Mandates standardized VCS ignore synchronization, centralized configuration inheritance, and fully qualified, documented suppression comments. Eliminates configuration drift, unignored build artifact pollution, and undocumented lint bypasses in CI/CD pipelines. 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: Ad-hoc ESLint-style suppressions, detached .gitignore parsing, and fragmented monorepo Biome configurations. 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 DriftAd-hoc ESLint-style suppressions, detached .gitignore parsing, and fragmented monorepo Biome configurations.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 enable VCS integration via `vcs.enabled

Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to mirror `.gitignore` semantics natively.

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 a mandatory, human-readable justification when using suppression comments

Engineers MUST ALWAYS provide a mandatory, human-readable justification when using suppression comments: `// biome-ignore <category>/<rule>: <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.
3

Engineers MUST NOT use unanchored, legacy, or bare suppression directives such as `// eslint-disable-next-line` or bare `// biome-ignore <rule>` without a colon and justification.

Engineers MUST NOT use unanchored, legacy, or bare suppression directives such as `// eslint-disable-next-line` or bare `// biome-ignore <rule>` without a colon and 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.
4

Monorepo packages MUST inherit root standards using `extends

Monorepo packages MUST inherit root standards using `extends: ["../../biome.json"]` or shared preset packages, overriding only package-specific path overrides.

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

CI pipelines MUST execute `biome ci --error-on-warnings` to prevent drift and treat lint warnings as blocking gates on touched pull request files.

CI pipelines MUST execute `biome ci --error-on-warnings` to prevent drift and treat lint warnings as blocking gates on touched pull request 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.
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 Strict Rule Suppression Standard critical for AI coding assistants?

Enforces deterministic formatting and linting architecture via Biome 1.9 single-binary tooling across enterprise monorepos. Mandates standardized VCS ignore synchronization, centralized configuration inheritance, and fully qualified, documented suppression comments. Eliminates configuration drift, unignored build artifact pollution, and undocumented lint bypasses in CI/CD pipelines. 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 (Ad-hoc ESLint-style suppressions, detached .gitignore parsing, and fragmented monorepo Biome configurations.) 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