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

Biome 1.9 Deterministic Configuration, VCS Integration, and Rule Suppression Guardrails

Enforces strict configuration ergonomics, VCS-aware file resolution, and deterministic inline suppression syntax in Biome 1.9. Prevents unindexed artifact evaluation, broken monorepo inheritance trees, and unreasoned lint suppressions.

Prohibited Anti-Pattern: Ignoring VCS ignore files, omitting pinned schemas, and applying bare or unstructured lint suppressions.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Deterministic Configuration, VCS Integration, and Rule Suppression Guardrails - Enforces strict configuration ergonomics, VCS-aware file resolution, and deterministic inline suppression syntax in Biome 1.9. Prevents unindexed artifact evaluation, broken monorepo inheritance trees, and unreasoned lint suppressions.
globs: biome.json, biome.jsonc, src/**/*.{js,jsx,ts,tsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-configuration-inheritance-vcs-suppression"
---

# Biome 1.9 Deterministic Configuration, VCS Integration, and Rule Suppression Guardrails

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ignoring VCS ignore files, omitting pinned schemas, and applying bare or unstructured lint suppressions.

## System Constraints
You are a Principal Software Architect enforcing production-grade Biome 1.9 configuration and code hygiene. Ensure all Biome config files use pinned schema versions matching the runtime CLI, enable native VCS integration to honor .gitignore, handle monorepo configuration inheritance via 'extends' paths safely, and strictly require well-formed, documented inline suppression comments.

## Strict Guidelines
- Engineers MUST ALWAYS pin the `$schema` attribute to the exact Biome minor version used by the project CLI (e.g., https://biomejs.dev/schemas/1.9.4/schema.json).
- Engineers MUST ALWAYS configure the `vcs` object with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent formatting or linting of build artifacts and gitignored assets.
- Engineers MUST ALWAYS format inline suppressions using the strict syntax `// biome-ignore lint/<category>/<rule>: <explanation>` where `<explanation>` is a mandatory justification for the suppression.
- Engineers MUST NOT use legacy suppression syntax (e.g., `// biome-ignore: rule`), ESLint comments (`// eslint-disable-next-line`), or omit rule-specific categories.
- Monorepo packages MUST inherit shared workspace rules using the `extends` property referencing relative or root workspace configurations instead of copying rule sets.
- CI validation pipelines MUST run `biome check --diagnostic-level=warn` with VCS detection active, avoiding ad-hoc file lists that bypass ignore heuristics.

## Bad vs Good Implementations
### Biome 1.9 Configuration: Monorepo Inheritance & VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to pin `$schema`, leaves `vcs` unconfigured (forcing Biome to traverse gitignored folders like dist/ and node_modules/), and misses configuration inheritance in monorepos.
```json
{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins schema for IDE auto-completion, extends root workspace rules, and enables Git ignore integration to prevent evaluating build artifacts.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["//biome.base.json"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2
  }
}
```

### Deterministic Rule Suppression Syntax

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Biome ignores ESLint comments. Bare rule names and omissions of category groups or explanation strings fail Biome 1.9's deterministic parser expectations.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const payloadLegacy: any = getPayload();

// biome-ignore noExplicitAny
const payloadShort: any = getPayload();

// biome-ignore lint/suspicious/noExplicitAny
const payloadNoReason: any = getPayload();
```

#### Production Standard (Correct)
> **Standard**: Uses the canonical suppression structure `biome-ignore lint/<group>/<rule>: <explanation>` mandated by Biome 1.9.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External legacy webhook payload lacks a validated schema contract
const payloadValidated: any = getPayload();
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem MCP
Allows agents to inspect biome.json, .gitignore, and package configs across the workspace.
Recommended Agent Skills (askills.dev)

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

Biome CLI Execution
Validates, formats, and checks repository source files using `biome check --write`.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Biome 1.9 Deterministic Configuration, VCS Integration, and Rule Suppression Guardrails

Biome 1.9 Deterministic Configuration, VCS Integration, and Rule Suppression Guardrails defines an industrial-grade behavioral standard for frontend engineering. Enforces strict configuration ergonomics, VCS-aware file resolution, and deterministic inline suppression syntax in Biome 1.9. Prevents unindexed artifact evaluation, broken monorepo inheritance trees, and unreasoned lint 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: Ignoring VCS ignore files, omitting pinned schemas, and applying bare or unstructured lint 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 DriftIgnoring VCS ignore files, omitting pinned schemas, and applying bare or unstructured lint 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 pin the `$schema` attribute to the exact Biome minor version used by the project CLI (e.g., https

Engineers MUST ALWAYS pin the `$schema` attribute to the exact Biome minor version used by the project CLI (e.g., https://biomejs.dev/schemas/1.9.4/schema.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.
2

Engineers MUST ALWAYS configure the `vcs` object with `enabled

Engineers MUST ALWAYS configure the `vcs` object with `enabled: true`, `clientKind: "git"`, and `useIgnoreFile: true` to prevent formatting or linting of build artifacts and gitignored assets.

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 suppressions using the strict syntax `// biome-ignore lint/<category>/<rule>

Engineers MUST ALWAYS format inline suppressions using the strict syntax `// biome-ignore lint/<category>/<rule>: <explanation>` where `<explanation>` is a mandatory justification for the suppression.

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 use legacy suppression syntax (e.g., `// biome-ignore

Engineers MUST NOT use legacy suppression syntax (e.g., `// biome-ignore: rule`), ESLint comments (`// eslint-disable-next-line`), or omit rule-specific categories.

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 shared workspace rules using the `extends` property referencing relative or root workspace configurations instead of copying rule sets.

Monorepo packages MUST inherit shared workspace rules using the `extends` property referencing relative or root workspace configurations instead of copying rule sets.

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

CI validation pipelines MUST run `biome check --diagnostic-level=warn` with VCS detection active, avoiding ad-hoc file lists that bypass ignore heuristics.

CI validation pipelines MUST run `biome check --diagnostic-level=warn` with VCS detection active, avoiding ad-hoc file lists that bypass ignore heuristics.

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, VCS Integration, and Rule Suppression Guardrails critical for AI coding assistants?

Enforces strict configuration ergonomics, VCS-aware file resolution, and deterministic inline suppression syntax in Biome 1.9. Prevents unindexed artifact evaluation, broken monorepo inheritance trees, and unreasoned lint 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 (Ignoring VCS ignore files, omitting pinned schemas, and applying bare or unstructured lint 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