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

Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance

Standardizes Biome 1.9 single-binary integration across monorepos and isolated repositories. Enforces strict Git-backed VCS ignore propagation, modular configuration inheritance via `extends`, and strictly justified, fully qualified `biome-ignore` comment suppressions. Prevents silent unformatted code commits, fragmented lint configurations, and unexplained rule overrides.

Prohibited Anti-Pattern: Fragmented configs, bypassed Git-ignore alignment, and naked unexplained inline suppressions.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance - Standardizes Biome 1.9 single-binary integration across monorepos and isolated repositories. Enforces strict Git-backed VCS ignore propagation, modular configuration inheritance via `extends`, and strictly justified, fully qualified `biome-ignore` comment suppressions. Prevents silent unformatted code commits, fragmented lint configurations, and unexplained rule overrides.
globs: biome.json, biome.jsonc, **/*.{js,mjs,cjs,ts,mts,cts,jsx,tsx,json,jsonc,css}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-vcs-inheritance-suppression-production-standard"
---

# Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Fragmented configs, bypassed Git-ignore alignment, and naked unexplained inline suppressions.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 production standards. You must ensure all Biome configuration files utilize structured inheritance via the `extends` property, strictly enable VCS Git-ignore synchronization (`vcs.clientKind = 'git'`, `vcs.useIgnoreFile = true`), and enforce deterministic, fully qualified rule suppressions with mandatory human-readable justifications.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent indexing and checking git-ignored artifacts.
- Engineers MUST NEVER use naked `// biome-ignore` suppressions without specifying both the full rule identifier (`lint/<group>/<ruleName>`) and a non-empty human rationale explaining why the rule is waived.
- Monorepos MUST use configuration inheritance (`extends: ["../../biome.json"]` or npm package specs) instead of duplicating lint and formatting rules across workspace packages.
- Files MUST NOT mix legacy ESLint/Prettier suppression pragmas (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) with Biome-governed projects; all suppressions must target Biome directly.
- Engineers MUST set `formatter.enabled: true` and align indentation (`indentStyle`, `lineWidth`) deterministically at the root configuration to eliminate diff churn across automated tools.

## Bad vs Good Implementations
### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The first suppression is a naked ignore that disables all checks silently. The second provides the rule name but lacks an explanatory rationale, violating deterministic auditability requirements.
```typescript
// biome-ignore
const rawData: any = JSON.parse(eventPayload);

// biome-ignore lint/suspicious/noExplicitAny
const unsafeState: any = window.__INITIAL_STATE__;
```

#### Production Standard (Correct)
> **Standard**: Both suppressions specify the fully qualified rule category and name (`lint/suspicious/noExplicitAny`) followed by a clear colon-separated justification explaining why the suppression is unavoidable.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Webhook payloads have dynamic runtime schemas validated downstream by Zod
const rawData: any = JSON.parse(eventPayload);

// biome-ignore lint/suspicious/noExplicitAny: Global SSR state injection is untyped before hydration parsing
const unsafeState: any = (window as unknown as Record<string, unknown>).__INITIAL_STATE__;
```

### Biome Configuration Inheritance and VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manual file ignore lists drift out of sync with `.gitignore` and lack VCS-level tracking. In a package workspace, this causes redundant configuration and unaligned rules.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".next"]
  },
  "linter": {
    "rules": {
      "recommended": true
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Inherits shared base configurations cleanly via `extends`, leverages Git VCS integration directly to reuse `.gitignore` without duplication, and specifies explicit schema versioning.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["@acme/config-biome/base"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP
Validates workspace root biome.json, package-level extensions, and .gitignore file locations.
Git MCP Server
Verifies Git ignore patterns and staged change boundaries for Biome CLI VCS resolution.
Recommended Agent Skills (askills.dev)

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

Biome CLI Diagnostics Skill
Executes `biome check --diagnostic-level=error --write` against changed files in accordance with VCS integration.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance

Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance defines an industrial-grade behavioral standard for frontend engineering. Standardizes Biome 1.9 single-binary integration across monorepos and isolated repositories. Enforces strict Git-backed VCS ignore propagation, modular configuration inheritance via `extends`, and strictly justified, fully qualified `biome-ignore` comment suppressions. Prevents silent unformatted code commits, fragmented lint configurations, and unexplained rule overrides. 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 configs, bypassed Git-ignore alignment, and naked unexplained 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 DriftFragmented configs, bypassed Git-ignore alignment, and naked unexplained 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 the root `biome.json` to prevent indexing and checking git-ignored 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 NEVER use naked `// biome-ignore` suppressions without specifying both the full rule identifier (`lint/<group>/<ruleName>`) and a non-empty human rationale explaining why the rule is waived.

Engineers MUST NEVER use naked `// biome-ignore` suppressions without specifying both the full rule identifier (`lint/<group>/<ruleName>`) and a non-empty human rationale explaining why the rule is waived.

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

Monorepos MUST use configuration inheritance (`extends

Monorepos MUST use configuration inheritance (`extends: ["../../biome.json"]` or npm package specs) instead of duplicating lint and formatting rules across workspace packages.

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

Files MUST NOT mix legacy ESLint/Prettier suppression pragmas (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) with Biome-governed projects

Files MUST NOT mix legacy ESLint/Prettier suppression pragmas (e.g., `// eslint-disable-next-line` or `// prettier-ignore`) with Biome-governed projects; all suppressions must target Biome directly.

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

Engineers MUST set `formatter.enabled

Engineers MUST set `formatter.enabled: true` and align indentation (`indentStyle`, `lineWidth`) deterministically at the root configuration to eliminate diff churn across automated tools.

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 Deterministic Biome 1.9 Configuration Inheritance, VCS Sync, and Suppression Compliance critical for AI coding assistants?

Standardizes Biome 1.9 single-binary integration across monorepos and isolated repositories. Enforces strict Git-backed VCS ignore propagation, modular configuration inheritance via `extends`, and strictly justified, fully qualified `biome-ignore` comment suppressions. Prevents silent unformatted code commits, fragmented lint configurations, and unexplained rule overrides. 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 configs, bypassed Git-ignore alignment, and naked unexplained 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

Deterministic