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

Biome 1.9 Config Inheritance, VCS Integration, and Strict Suppression Syntax

Enforces deterministic Biome 1.9 configuration standards across repositories. Mandates explicit schema declarations, unified VCS ignore sync via `vcs.clientKind`, modular configuration inheritance, and structurally justified inline rule suppressions.

Prohibited Anti-Pattern: Unjustified inline suppressions, legacy ESLint directives, and desynced ignore files causing CI/local divergence

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Config Inheritance, VCS Integration, and Strict Suppression Syntax - Enforces deterministic Biome 1.9 configuration standards across repositories. Mandates explicit schema declarations, unified VCS ignore sync via `vcs.clientKind`, modular configuration inheritance, and structurally justified inline rule suppressions.
globs: biome.json, biome.jsonc, **/*.ts, **/*.tsx, **/*.js, **/*.jsx
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-configuration-vcs-suppression-standards"
---

# Biome 1.9 Config Inheritance, VCS Integration, and Strict Suppression Syntax

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unjustified inline suppressions, legacy ESLint directives, and desynced ignore files causing CI/local divergence

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 single-binary linter and formatter architecture. Mandate exact schema matching, native VCS integration, predictable configuration inheritance, and strictly explained suppression syntax.

## Strict Guidelines
- Engineers MUST ALWAYS specify `$schema` targeting `https://biomejs.dev/schemas/1.9.4/schema.json` in root and inherited `biome.json` files.
- Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` instead of duplicating paths into `files.ignore`.
- Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// prettier-ignore`, or `/* tslint:disable */` to bypass Biome checks.
- Code MUST strictly supply an explanation when suppressing rules using the `// biome-ignore <group>/<rule>: <explanation>` or `// biome-ignore lint/<group>/<rule>(<category>): <explanation>` format.
- Mono-repo packages MUST inherit shared configurations using the `extends` array rather than copy-pasting duplicated rulesets.
- Teams NEVER permit suppression comments without specifying the exact rule name (blanket `// biome-ignore` is strictly prohibited).

## Bad vs Good Implementations
### Root Configuration: VCS Integration and Schema Validation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` breaks IDE auto-completion and validation. Manually duplicating `.gitignore` patterns into `files.ignore` causes configuration drift and unintended scanning of build artifacts.
```json
{
  "linter": {
    "enabled": true
  },
  "files": {
    "ignore": ["dist/**", "node_modules/**", ".turbo/**", "coverage/**"]
  }
}
```

#### Production Standard (Correct)
> **Standard**: Includes exact schema validation for 1.9.4 and relies on native Git ignore resolution via the `vcs` object, ensuring single-source-of-truth file exclusion.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "includes": ["src/**/*.ts", "src/**/*.tsx"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: ESLint directives are ignored by Biome, allowing lint failures to persist in CI. A bare `// biome-ignore` lacks the mandatory rule target and justification explanation, failing strict Biome parsing.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(input: string): any {
  // biome-ignore
  return JSON.parse(input);
}
```

#### Production Standard (Correct)
> **Standard**: Suppression explicitly targets the full rule path (`lint/<category>/<ruleName>`) followed by a colon and concrete justification, satisfying deterministic audit requirements.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Raw JSON parse must return any prior to schema validation
export function deserializePayload(input: string): any {
  // biome-ignore lint/security/noGlobalEval: Required for legacy macro execution sandbox
  return eval(`(${input})`);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Execution Server
Provides headless execution of Biome CLI formatting, linting, and check commands directly through MCP.
Recommended Agent Skills (askills.dev)

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

Biome CI Checker
Runs `biome check --write --no-errors-on-unmatched` to enforce determinism and validate lint rules.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Config Inheritance, VCS Integration, and Strict Suppression Syntax

Biome 1.9 Config Inheritance, VCS Integration, and Strict Suppression Syntax defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9 configuration standards across repositories. Mandates explicit schema declarations, unified VCS ignore sync via `vcs.clientKind`, modular configuration inheritance, and structurally justified inline rule suppressions. 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: Unjustified inline suppressions, legacy ESLint directives, and desynced ignore files causing CI/local divergence 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 DriftUnjustified inline suppressions, legacy ESLint directives, and desynced ignore files causing CI/local divergenceCritical
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 specify `$schema` targeting `https

Engineers MUST ALWAYS specify `$schema` targeting `https://biomejs.dev/schemas/1.9.4/schema.json` in root and inherited `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.
2

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` instead of duplicating paths into `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.
3

Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// prettier-ignore`, or `/* tslint

Engineers MUST NOT use legacy comments such as `// eslint-disable`, `// prettier-ignore`, or `/* tslint:disable */` to bypass Biome checks.

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

Code MUST strictly supply an explanation when suppressing rules using the `// biome-ignore <group>/<rule>

Code MUST strictly supply an explanation when suppressing rules using the `// biome-ignore <group>/<rule>: <explanation>` or `// biome-ignore lint/<group>/<rule>(<category>): <explanation>` 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.
5

Mono-repo packages MUST inherit shared configurations using the `extends` array rather than copy-pasting duplicated rulesets.

Mono-repo packages MUST inherit shared configurations using the `extends` array rather than copy-pasting duplicated rulesets.

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

Teams NEVER permit suppression comments without specifying the exact rule name (blanket `// biome-ignore` is strictly prohibited).

Teams NEVER permit suppression comments without specifying the exact rule name (blanket `// biome-ignore` is strictly prohibited).

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 Config Inheritance, VCS Integration, and Strict Suppression Syntax critical for AI coding assistants?

Enforces deterministic Biome 1.9 configuration standards across repositories. Mandates explicit schema declarations, unified VCS ignore sync via `vcs.clientKind`, modular configuration inheritance, and structurally justified inline rule suppressions. 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 (Unjustified inline suppressions, legacy ESLint directives, and desynced ignore files causing CI/local divergence) 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