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

Biome 1.9 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards

Biome 1.9 requires strict configuration inheritance hierarchies across monorepos, authoritative VCS ignore alignment, and deterministic, reason-mandated suppression syntax. Inconsistent root anchoring leads to silent file skips and CI divergence, while ad-hoc suppression syntax creates unmonitored code quality debt.

Prohibited Anti-Pattern: Unanchored Monorepo Extends, Missing VCS Git Anchoring, and Unexplained Suppression Pragmas

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards - Biome 1.9 requires strict configuration inheritance hierarchies across monorepos, authoritative VCS ignore alignment, and deterministic, reason-mandated suppression syntax. Inconsistent root anchoring leads to silent file skips and CI divergence, while ad-hoc suppression syntax creates unmonitored code quality debt.
globs: biome.json, biome.jsonc, **/*.ts, **/*.tsx, **/*.js, **/*.jsx, **/*.json
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-configuration-vcs-suppression-standards"
---

# Biome 1.9 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored Monorepo Extends, Missing VCS Git Anchoring, and Unexplained Suppression Pragmas

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards across enterprise multi-package workspaces. Enforce deterministic configuration inheritance, strict VCS integration (`vcs.useIgnoreFile = true`), and the mandatory Biome suppression format (`// biome-ignore <group>/<rule>: <explicit rationale>`). Reject any legacy ESLint/Prettier suppressions, unanchored monorepo extends, or suppressions lacking explicit justification.

## Strict Guidelines
- Engineers MUST configure 'vcs' explicitly in the root 'biome.json' with 'clientKind': 'git', 'enabled': true, and 'useIgnoreFile': true.
- Engineers MUST specify the full rule identity and a non-empty rationale in all inline suppressions using the exact format: '// biome-ignore <group>/<rule>: <explanation>'.
- Engineers MUST NOT use legacy ESLint comments (e.g., '// eslint-disable-next-line') or generic Biome ignore directives lacking group categorization.
- Workspace packages MUST extend the root configuration via explicit relative paths in the 'extends' array (e.g., 'extends': ['../../biome.json']).
- Teams MUST enforce '$schema' pointers matching the exact installed Biome version (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to guarantee IDE validation parity.

## Bad vs Good Implementations
### Biome Root Configuration & Monorepo Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits $schema validation, fails to declare VCS integration (leading to formatting of gitignored artifacts like dist/ and node_modules), and lacks deterministic file pattern boundaries.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Anchors VCS to Git ignore configurations, declares schema for real-time validation, and standardizes workspace formatting rules.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": false,
    "includes": ["src/**", "tests/**"]
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an unparsed legacy ESLint comment that Biome ignores, and includes a Biome suppression that lacks the mandatory explanation suffix required for architectural tracking.
```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 strictly to the Biome 1.9 suppression contract: '// biome-ignore <group>/<rule>: <explanation>', preventing silent lint failures and enforcing audit trails.
```typescript
export function deserializePayload(input: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Required for third-party upstream webhook contract which omits schema
  const rawData: any = JSON.parse(input);
  return rawData;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Filesystem MCP
Validates workspace root structures, glob patterns, and biome.json placement.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes 'biome check --write' and 'biome ci' to enforce deterministic linting and formatting.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards

Biome 1.9 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards defines an industrial-grade behavioral standard for frontend engineering. Biome 1.9 requires strict configuration inheritance hierarchies across monorepos, authoritative VCS ignore alignment, and deterministic, reason-mandated suppression syntax. Inconsistent root anchoring leads to silent file skips and CI divergence, while ad-hoc suppression syntax creates unmonitored code quality debt. 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: Unanchored Monorepo Extends, Missing VCS Git Anchoring, and Unexplained Suppression Pragmas 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 DriftUnanchored Monorepo Extends, Missing VCS Git Anchoring, and Unexplained Suppression PragmasCritical
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 configure 'vcs' explicitly in the root 'biome.json' with 'clientKind'

Engineers MUST configure 'vcs' explicitly in the root 'biome.json' with 'clientKind': 'git', 'enabled': true, and 'useIgnoreFile': true.

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 specify the full rule identity and a non-empty rationale in all inline suppressions using the exact format

Engineers MUST specify the full rule identity and a non-empty rationale in all inline suppressions using the exact format: '// biome-ignore <group>/<rule>: <explanation>'.

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 ESLint comments (e.g., '// eslint-disable-next-line') or generic Biome ignore directives lacking group categorization.

Engineers MUST NOT use legacy ESLint comments (e.g., '// eslint-disable-next-line') or generic Biome ignore directives lacking group categorization.

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

Workspace packages MUST extend the root configuration via explicit relative paths in the 'extends' array (e.g., 'extends'

Workspace packages MUST extend the root configuration via explicit relative paths in the 'extends' array (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.
5

Teams MUST enforce '$schema' pointers matching the exact installed Biome version (e.g., 'https

Teams MUST enforce '$schema' pointers matching the exact installed Biome version (e.g., 'https://biomejs.dev/schemas/1.9.4/schema.json') to guarantee IDE validation parity.

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 Deterministic Configuration Inheritance, VCS Anchoring, and Suppression Standards critical for AI coding assistants?

Biome 1.9 requires strict configuration inheritance hierarchies across monorepos, authoritative VCS ignore alignment, and deterministic, reason-mandated suppression syntax. Inconsistent root anchoring leads to silent file skips and CI divergence, while ad-hoc suppression syntax creates unmonitored code quality debt. 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 (Unanchored Monorepo Extends, Missing VCS Git Anchoring, and Unexplained Suppression Pragmas) 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