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

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards

Enforces deterministic Biome 1.9 configuration standards across monorepos and standalone repositories. Mandates centralized configuration inheritance, direct VCS gitignore binding to prevent split-brain ignore states, and strictly documented suppression comments requiring rule-specific rationale.

Prohibited Anti-Pattern: Fragmented Per-Package Configurations, Unsynchronized Git Ignores, and Bare Unjustified Suppressions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards - Enforces deterministic Biome 1.9 configuration standards across monorepos and standalone repositories. Mandates centralized configuration inheritance, direct VCS gitignore binding to prevent split-brain ignore states, and strictly documented suppression comments requiring rule-specific rationale.
globs: biome.json, biome.jsonc, package.json, src/**/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-config-vcs-suppression-standards"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented Per-Package Configurations, Unsynchronized Git Ignores, and Bare Unjustified Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 toolchain standards. Ensure all projects utilize single-binary configuration inheritance via 'extends', activate native VCS gitignore resolution, and enforce strict, justified suppression syntax for lint diagnostics.

## Strict Guidelines
- Projects MUST configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json' to maintain a single source of truth for file exclusion.
- Workspace packages in a monorepo MUST inherit shared settings using the 'extends' array referencing root or shared package configurations (e.g., 'extends': ["//biome.json"]).
- Engineers MUST NOT introduce obsolete ESLint or Prettier suppression comments (e.g., '// eslint-disable-next-line'); all suppressions MUST use the Biome suppression format.
- Engineers MUST ALWAYS append an explicit explanation after a colon when suppressing rules: '// biome-ignore <group>/<rule>: <explanation>'. Bare suppression tokens without explanation are strictly forbidden.
- CI/CD workflows and pre-commit hooks MUST utilize 'biome check --write --vcs-client-kind=git --staged' or '--changed' to guarantee high-performance, deterministic differential verification.
- The 'biome.json' configuration MUST explicitly define JSON schema versioning matching the installed binary (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json').

## Bad vs Good Implementations
### Biome 1.9 Root Configuration with VCS and Monorepo Extends

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually duplicates .gitignore entries in 'files.ignore' instead of delegating to Biome's native VCS engine. Lacks strict lint rule grouping and overrides.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Correctly integrates Git VCS ignore synchronization to eliminate redundant file exclusion lists, enforces non-negotiable linter rules, and provides deterministic formatting.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```

### Deterministic Rule Suppression with Mandatory Rationale

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an unparsed legacy ESLint comment that Biome ignores, followed by a bare Biome suppression lacking a mandatory rationale explanation.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(input) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres to Biome 1.9 suppression format '// biome-ignore <group>/<rule>: <rationale>', ensuring the suppression is deterministic, actionable, and auditable in review.
```typescript
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: External legacy payload format is unvalidated at runtime
  return JSON.parse(input) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Code Analysis Server
Provides instant project diagnostics, automated AST-aware fixes, and configuration validation via the Biome daemon.
Recommended Agent Skills (askills.dev)

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

Biome CLI Diagnostics Runner
Executes 'biome check' with VCS-aware differential flags for sub-millisecond linting and formatting verification.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards

Biome 1.9 Configuration Inheritance, VCS Integration, and Explicit Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configuration standards across monorepos and standalone repositories. Mandates centralized configuration inheritance, direct VCS gitignore binding to prevent split-brain ignore states, and strictly documented suppression comments requiring rule-specific rationale. 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 Per-Package Configurations, Unsynchronized Git Ignores, and Bare Unjustified 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 DriftFragmented Per-Package Configurations, Unsynchronized Git Ignores, and Bare Unjustified SuppressionsCritical
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

Projects MUST configure 'vcs.enabled

Projects MUST configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json' to maintain a single source of truth for file exclusion.

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

Workspace packages in a monorepo MUST inherit shared settings using the 'extends' array referencing root or shared package configurations (e.g., 'extends'

Workspace packages in a monorepo MUST inherit shared settings using the 'extends' array referencing root or shared package configurations (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.
3

Engineers MUST NOT introduce obsolete ESLint or Prettier suppression comments (e.g., '// eslint-disable-next-line')

Engineers MUST NOT introduce obsolete ESLint or Prettier suppression comments (e.g., '// eslint-disable-next-line'); all suppressions MUST use the Biome suppression format.

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 ALWAYS append an explicit explanation after a colon when suppressing rules

Engineers MUST ALWAYS append an explicit explanation after a colon when suppressing rules: '// biome-ignore <group>/<rule>: <explanation>'. Bare suppression tokens without explanation are strictly forbidden.

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/CD workflows and pre-commit hooks MUST utilize 'biome check --write --vcs-client-kind=git --staged' or '--changed' to guarantee high-performance, deterministic differential verification.

CI/CD workflows and pre-commit hooks MUST utilize 'biome check --write --vcs-client-kind=git --staged' or '--changed' to guarantee high-performance, deterministic differential verification.

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

The 'biome.json' configuration MUST explicitly define JSON schema versioning matching the installed binary (e.g., 'https

The 'biome.json' configuration MUST explicitly define JSON schema versioning matching the installed binary (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.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.
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 Explicit Suppression Standards critical for AI coding assistants?

Enforces deterministic Biome 1.9 configuration standards across monorepos and standalone repositories. Mandates centralized configuration inheritance, direct VCS gitignore binding to prevent split-brain ignore states, and strictly documented suppression comments requiring rule-specific rationale. 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 Per-Package Configurations, Unsynchronized Git Ignores, and Bare Unjustified 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