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

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

Enforces deterministic configuration inheritance, native Git VCS integration, and structured suppression syntax for Biome 1.9+. Prevents silent linter desynchronization, unverified rule overrides, and CI divergence caused by unanchored configurations or legacy ignore strategies.

Prohibited Anti-Pattern: Unexplained suppressions, decoupled gitignores, and fractured monorepo inheritance trees in Biome 1.9

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 Suppression Standard - Enforces deterministic configuration inheritance, native Git VCS integration, and structured suppression syntax for Biome 1.9+. Prevents silent linter desynchronization, unverified rule overrides, and CI divergence caused by unanchored configurations or legacy ignore strategies.
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-vcs-suppression-standard"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unexplained suppressions, decoupled gitignores, and fractured monorepo inheritance trees in Biome 1.9

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 standards. Enforce exact schema-pinned configurations, native VCS-backed ignore discovery, valid monorepo extends chains, and deterministic suppression comments containing mandatory explanatory justifications.

## Strict Guidelines
- Engineers MUST ALWAYS pin Biome configuration to the exact versioned schema URL (e.g., https://biomejs.dev/schemas/1.9.4/schema.json) in biome.json/biome.jsonc.
- Engineers MUST ALWAYS enable VCS integration via `vcs.enabled: true`, `vcs.clientKind: "git"`, and `vcs.useIgnoreFile: true` in the root configuration to inherit root `.gitignore` rules deterministically.
- Engineers MUST ALWAYS format inline rule suppressions with explicit category, rule name, and mandatory justification: `// biome-ignore <group>/<rule>: <explanation>`. Bare suppressions without explanation are strictly forbidden.
- Engineers MUST NOT maintain separate manual file exclusion lists in `files.ignore` when files are already covered by `.gitignore` unless targeting non-Git-ignored transient outputs.
- Monorepo packages MUST inherit root configuration via the `extends` array in child `biome.json` files using explicit relative paths (e.g., `"extends": ["../../biome.json"]`), overriding only package-specific rule deltas.
- Engineers MUST NOT mix ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line`) into codebases standardized on Biome 1.9.
- CI pipelines MUST execute `biome ci --vcs-client-kind=git --vcs-use-ignore-file=true` to guarantee parity with local developer VCS evaluation.

## Bad vs Good Implementations
### Biome Configuration: Root Config with VCS and Nested Monorepo Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an unpinned 'latest' schema URL that breaks across major/minor bumps, manually duplicates standard .gitignore entries instead of leveraging native VCS integration, and lacks VCS root configuration.
```json
{
  "$schema": "https://biomejs.dev/schemas/latest/schema.json",
  "files": {
    "ignore": ["node_modules", "dist", "build", "coverage"]
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins configuration schema to Biome 1.9.4, delegates file exclusions natively to .gitignore through the VCS block, and establishes unambiguous formatting and linting baselines.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": false
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Suppression Syntax with Explanation Guardrail

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The first suppression is bare without rule target or explanation. The second targets the rule but omits the colon and explanatory rationale, which degrades code review auditing and violates Biome 1.9 best practices.
```typescript
// biome-ignore
const legacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny
function processData(input: any): void {
  console.log(input);
}
```

#### Production Standard (Correct)
> **Standard**: Follows the deterministic Biome 1.9 suppression pattern: category, rule name, colon separator, and an auditable architectural justification explaining why suppression is required.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Upstream RPC payload types are unversioned; validated by Zod schema below
const legacyPayload: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny: Generic event bridge receives third-party untyped webhooks
function processData(input: any): void {
  console.log(input);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server MCP
Provides real-time AST linting, formatting, and suppression validation via Biome 1.9 single-binary integration.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes biome check, format, and lint commands with Git VCS flags and deterministic exit-code validation.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Suppression Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic configuration inheritance, native Git VCS integration, and structured suppression syntax for Biome 1.9+. Prevents silent linter desynchronization, unverified rule overrides, and CI divergence caused by unanchored configurations or legacy ignore strategies. 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: Unexplained suppressions, decoupled gitignores, and fractured monorepo inheritance trees in Biome 1.9 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 DriftUnexplained suppressions, decoupled gitignores, and fractured monorepo inheritance trees in Biome 1.9Critical
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 pin Biome configuration to the exact versioned schema URL (e.g., https

Engineers MUST ALWAYS pin Biome configuration to the exact versioned schema URL (e.g., https://biomejs.dev/schemas/1.9.4/schema.json) in biome.json/biome.jsonc.

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` in the root configuration to inherit root `.gitignore` rules deterministically.

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 ALWAYS format inline rule suppressions with explicit category, rule name, and mandatory justification

Engineers MUST ALWAYS format inline rule suppressions with explicit category, rule name, and mandatory justification: `// biome-ignore <group>/<rule>: <explanation>`. Bare suppressions 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.
4

Engineers MUST NOT maintain separate manual file exclusion lists in `files.ignore` when files are already covered by `.gitignore` unless targeting non-Git-ignored transient outputs.

Engineers MUST NOT maintain separate manual file exclusion lists in `files.ignore` when files are already covered by `.gitignore` unless targeting non-Git-ignored transient outputs.

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

Monorepo packages MUST inherit root configuration via the `extends` array in child `biome.json` files using explicit relative paths (e.g., `"extends"

Monorepo packages MUST inherit root configuration via the `extends` array in child `biome.json` files using explicit relative paths (e.g., `"extends": ["../../biome.json"]`), overriding only package-specific rule deltas.

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

Engineers MUST NOT mix ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line`) into codebases standardized on Biome 1.9.

Engineers MUST NOT mix ESLint/Prettier suppression directives (e.g., `// eslint-disable-next-line`) into codebases standardized on Biome 1.9.

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

CI pipelines MUST execute `biome ci --vcs-client-kind=git --vcs-use-ignore-file=true` to guarantee parity with local developer VCS evaluation.

CI pipelines MUST execute `biome ci --vcs-client-kind=git --vcs-use-ignore-file=true` to guarantee parity with local developer VCS evaluation.

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 Suppression Standard critical for AI coding assistants?

Enforces deterministic configuration inheritance, native Git VCS integration, and structured suppression syntax for Biome 1.9+. Prevents silent linter desynchronization, unverified rule overrides, and CI divergence caused by unanchored configurations or legacy ignore strategies. 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 (Unexplained suppressions, decoupled gitignores, and fractured monorepo inheritance trees in Biome 1.9) 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