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

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

Standardizes Biome 1.9 configuration hierarchies across monorepos and standalone repositories by enforcing strict extends semantics, native VCS ignore integration, and deterministic inline suppression syntax. Prevents configuration drift, unformatted git diff churn, and undocumented rule bypasses by demanding explanatory suppression comments with explicit rule targets.

Prohibited Anti-Pattern: Unpinned Config Inheritance, Disconnected Git Ignored Lists, and Bare Non-Explanatory Suppression Comments

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression - Standardizes Biome 1.9 configuration hierarchies across monorepos and standalone repositories by enforcing strict extends semantics, native VCS ignore integration, and deterministic inline suppression syntax. Prevents configuration drift, unformatted git diff churn, and undocumented rule bypasses by demanding explanatory suppression comments with explicit rule targets.
globs: biome.json, biome.jsonc, apps/**/biome.json, packages/**/biome.json, 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-1-9-monorepo-vcs-deterministic-suppression-standard"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unpinned Config Inheritance, Disconnected Git Ignored Lists, and Bare Non-Explanatory Suppression Comments

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 Single-Binary Linter & Formatter invariants. Mandate absolute determinism in configuration inheritance via extends arrays, explicit git-backed ignore integration via vcs.useIgnoreFile, and documented inline suppression syntax. Reject legacy ESLint/Prettier suppressions, unpinned remote configs, and unannotated biome-ignore comments.

## Strict Guidelines
- Engineers MUST ALWAYS configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in the root 'biome.json' to prevent processing untracked build artifacts and submodule files.
- Engineers MUST ALWAYS provide an explicit reason and rule path when using suppression comments using the syntax '// biome-ignore lint/<group>/<rule>: <explanation>'.
- Engineers MUST NOT use bare suppressions like '// biome-ignore' or '// biome-ignore-all' without explicit rule specifiers and justification tokens.
- Package-level 'biome.json' files in monorepos MUST explicitly inherit from the root workspace config using 'extends: ["../../biome.json"]' rather than redefining global formatter and linter invariants.
- Engineers MUST NOT mix ESLint directives (e.g., '/* eslint-disable */') or Prettier comments with Biome directives; legacy suppression markers MUST be stripped.
- Configurations SHOULD pin schema references using '$schema: "https://biomejs.dev/schemas/1.9.4/schema.json"' to match the active binary release and guarantee deterministic CLI behavior in CI pipelines.

## Bad vs Good Implementations
### Deterministic Biome 1.9 Monorepo Root Configuration with VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits the 1.9 schema declaration, fails to link native gitignore rules via the 'vcs' object (forcing redundant duplicate ignore arrays), and omits strict ruleset definitions, leading to CI/local inconsistencies.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  },
  "files": {
    "ignore": ["node_modules", "dist", "build"]
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins the exact 1.9.4 schema, delegates file ignoring directly to the Git ignore system, and defines unambiguous formatting and linting boundaries.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "formatWithErrors": false,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  }
}
```

### Inline Rule Suppression with Required Scoping and Explanation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses an unsupported ESLint comment and an uninformative bare biome-ignore suppression that lacks a targeted rule category, rule name, and audit explanation.
```typescript
// eslint-disable-next-line
const legacyAny: any = fetchPayload();

// biome-ignore
const unvalidated = JSON.parse(rawBlob);
```

#### Production Standard (Correct)
> **Standard**: Adheres to the deterministic Biome 1.9 suppression format specifying the complete rule identifier ('lint/suspicious/noExplicitAny') accompanied by an architectural justification.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: External webhook payload is dynamic and parsed downstream with Valibot schema
const legacyAny: any = fetchPayload();

// biome-ignore lint/suspicious/noExplicitAny: Raw blob parsing requires deferred structural validation
const unvalidated: any = JSON.parse(rawBlob);
```

### Monorepo Package Configuration Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Creates configuration divergence by redefining formatting attributes locally without explicitly declaring inheritance from the monorepo root.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "formatter": {
    "enabled": true,
    "indentWidth": 4
  }
}
```

#### Production Standard (Correct)
> **Standard**: Uses the 'extends' array to inherit the base VCS and linting constraints from the workspace root while applying targeted package-specific overrides.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.json"],
  "javascript": {
    "formatter": {
      "jsxQuoteStyle": "double"
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Fast Lint & Format Tool
Executes single-binary Biome CLI operations, verifying project syntax, reporting lint errors, and applying formatting.
Recommended Agent Skills (askills.dev)

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

Biome CLI Execution Runner
Runs 'biome check --write' and 'biome ci' across target packages with native git-aware file scoping.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Deterministic Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Standardizes Biome 1.9 configuration hierarchies across monorepos and standalone repositories by enforcing strict extends semantics, native VCS ignore integration, and deterministic inline suppression syntax. Prevents configuration drift, unformatted git diff churn, and undocumented rule bypasses by demanding explanatory suppression comments with explicit rule targets. 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, Disconnected Git Ignored Lists, and Bare Non-Explanatory Suppression Comments 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, Disconnected Git Ignored Lists, and Bare Non-Explanatory Suppression CommentsCritical
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 processing untracked build artifacts and submodule files.

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 provide an explicit reason and rule path when using suppression comments using the syntax '// biome-ignore lint/<group>/<rule>

Engineers MUST ALWAYS provide an explicit reason and rule path when using suppression comments using the syntax '// biome-ignore lint/<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 bare suppressions like '// biome-ignore' or '// biome-ignore-all' without explicit rule specifiers and justification tokens.

Engineers MUST NOT use bare suppressions like '// biome-ignore' or '// biome-ignore-all' without explicit rule specifiers and justification tokens.

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

Package-level 'biome.json' files in monorepos MUST explicitly inherit from the root workspace config using 'extends

Package-level 'biome.json' files in monorepos MUST explicitly inherit from the root workspace config using 'extends: ["../../biome.json"]' rather than redefining global formatter and linter invariants.

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 mix ESLint directives (e.g., '/* eslint-disable */') or Prettier comments with Biome directives

Engineers MUST NOT mix ESLint directives (e.g., '/* eslint-disable */') or Prettier comments with Biome directives; legacy suppression markers MUST be stripped.

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

Configurations SHOULD pin schema references using '$schema

Configurations SHOULD pin schema references using '$schema: "https://biomejs.dev/schemas/1.9.4/schema.json"' to match the active binary release and guarantee deterministic CLI behavior in CI pipelines.

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

Standardizes Biome 1.9 configuration hierarchies across monorepos and standalone repositories by enforcing strict extends semantics, native VCS ignore integration, and deterministic inline suppression syntax. Prevents configuration drift, unformatted git diff churn, and undocumented rule bypasses by demanding explanatory suppression comments with explicit rule targets. 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, Disconnected Git Ignored Lists, and Bare Non-Explanatory Suppression Comments) 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