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-v1-9-config-vcs-suppression-guardrail

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrail

Enforces strict configuration architecture for Biome v1.9+ across monorepos and standalone repositories. Prevents configuration drift by mandating deterministic extends arrays, strict git-backed VCS integration to respect ignore files, and exact inline suppression comment formatting with mandatory rationales.

Prohibited Anti-Pattern: Unpinned Config Inheritance, Unlinked VCS Ignores, and Naked Inline 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 Suppression Guardrail - Enforces strict configuration architecture for Biome v1.9+ across monorepos and standalone repositories. Prevents configuration drift by mandating deterministic extends arrays, strict git-backed VCS integration to respect ignore files, and exact inline suppression comment formatting with mandatory rationales.
globs: biome.json, biome.jsonc, src/**/*.{js,ts,jsx,tsx,json,jsonc,css}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-v1-9-config-vcs-suppression-guardrail"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unpinned Config Inheritance, Unlinked VCS Ignores, and Naked Inline Suppressions

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. You must ensure that Biome configurations utilize strict inheritance with pinned local/specifier paths, explicit VCS integration enabled via Git to avoid dual-ignore maintenance, and that all inline rule suppressions follow the deterministic Biome syntax (biome-ignore lint/group/rule: <explanation>) with actionable justifications.

## Strict Guidelines
- Engineers MUST ALWAYS enable 'vcs.enabled: true' with 'vcs.clientKind: "git"' and 'vcs.useIgnoreFile: true' in the root 'biome.json' to prevent discrepancies between .gitignore and Biome scanning.
- Engineers MUST NOT use unanchored or vague inline suppressions like '// biome-ignore' or '// eslint-disable'; suppressions MUST strictly use the format '// biome-ignore lint/<group>/<rule>: <technical-justification>'.
- Child configurations in monorepo packages MUST use relative file paths or explicit workspace specifiers in the 'extends' array rather than duplicating base rules.
- Configurations MUST define deterministic formatter options ('indentStyle', 'lineWidth', 'quoteStyle') exclusively in the base configuration unless scoped overrides are explicitly justified.
- Engineers MUST NOT commit suppressions without a non-empty, actionable explanation stating why the lint rule cannot be resolved safely in code.

## Bad vs Good Implementations
### Biome Configuration: Root VCS Integration and Monorepo Extends

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to leverage Biome's native VCS integration, forcing developers to manually duplicate ignore rules already present in .gitignore. Missing schema locking and root extends configuration.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", ".next"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Correctly links Biome directly to Git's ignore mechanism via vcs options, pins the exact schema version, and establishes global deterministic linting and formatting baselines.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses naked suppression without rule name or reason, and applies legacy ESLint comments which Biome does not respect, leading to uncaught lint failures.
```typescript
// biome-ignore
const userData: any = JSON.parse(rawInput);

// eslint-disable-next-line @typescript-eslint/no-explicit-any
function processPayload(payload: any) {
  return payload.id;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres strictly to the Biome 1.9 suppression format '// biome-ignore <group>/<rule>: <explanation>' providing precise rule targeting and audit-ready justifications.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: external third-party webhook payload lacks official typing definitions
const userData: any = JSON.parse(rawInput);

// biome-ignore lint/suspicious/noExplicitAny: generic wire protocol handler before runtime Zod schema parsing
function processPayload(payload: any) {
  return payload.id;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Protocol MCP
Provides real-time workspace diagnostic analysis, auto-formatting, and quick-fix operations directly from the Biome daemon.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes single-binary biome check, format, and lint commands with --write and --staged flags in CI/CD pipelines.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration architecture for Biome v1.9+ across monorepos and standalone repositories. Prevents configuration drift by mandating deterministic extends arrays, strict git-backed VCS integration to respect ignore files, and exact inline suppression comment formatting with mandatory rationales. 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: Unpinned Config Inheritance, Unlinked VCS Ignores, and Naked 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 DriftUnpinned Config Inheritance, Unlinked VCS Ignores, and Naked Inline 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

Engineers MUST ALWAYS enable 'vcs.enabled

Engineers MUST ALWAYS enable 'vcs.enabled: true' with 'vcs.clientKind: "git"' and 'vcs.useIgnoreFile: true' in the root 'biome.json' to prevent discrepancies between .gitignore and Biome scanning.

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 NOT use unanchored or vague inline suppressions like '// biome-ignore' or '// eslint-disable'

Engineers MUST NOT use unanchored or vague inline suppressions like '// biome-ignore' or '// eslint-disable'; suppressions MUST strictly use the format '// biome-ignore lint/<group>/<rule>: <technical-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.
3

Child configurations in monorepo packages MUST use relative file paths or explicit workspace specifiers in the 'extends' array rather than duplicating base rules.

Child configurations in monorepo packages MUST use relative file paths or explicit workspace specifiers in the 'extends' array rather than duplicating base rules.

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

Configurations MUST define deterministic formatter options ('indentStyle', 'lineWidth', 'quoteStyle') exclusively in the base configuration unless scoped overrides are explicitly justified.

Configurations MUST define deterministic formatter options ('indentStyle', 'lineWidth', 'quoteStyle') exclusively in the base configuration unless scoped overrides are explicitly justified.

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 NOT commit suppressions without a non-empty, actionable explanation stating why the lint rule cannot be resolved safely in code.

Engineers MUST NOT commit suppressions without a non-empty, actionable explanation stating why the lint rule cannot be resolved safely in code.

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

Enforces strict configuration architecture for Biome v1.9+ across monorepos and standalone repositories. Prevents configuration drift by mandating deterministic extends arrays, strict git-backed VCS integration to respect ignore files, and exact inline suppression comment formatting with mandatory rationales. 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 (Unpinned Config Inheritance, Unlinked VCS Ignores, and Naked 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

Biome