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-config-and-suppression-guardrail

Deterministic Configuration Inheritance, VCS Integration, and Suppression Invariants in Biome 1.9

Biome 1.9 relies on single-binary execution speed and strict configuration inheritance using the 'extends' array across workspaces. Mixing ESLint-style suppression directives, failing to enable VCS integration for ignore file honoring, or using malformed inline suppressions breaks deterministic linting across continuous integration pipelines.

Prohibited Anti-Pattern: ESLint-Style Suppression Comments and Unanchored Biome Configurations Compromising CI Determinism

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Configuration Inheritance, VCS Integration, and Suppression Invariants in Biome 1.9 - Biome 1.9 relies on single-binary execution speed and strict configuration inheritance using the 'extends' array across workspaces. Mixing ESLint-style suppression directives, failing to enable VCS integration for ignore file honoring, or using malformed inline suppressions breaks deterministic linting across continuous integration pipelines.
globs: biome.json, biome.jsonc, packages/**/biome.json, apps/**/biome.json, src/**/*.{ts,tsx,js,jsx,json,css}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-1-9-monorepo-config-and-suppression-guardrail"
---

# Deterministic Configuration Inheritance, VCS Integration, and Suppression Invariants in Biome 1.9

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: ESLint-Style Suppression Comments and Unanchored Biome Configurations Compromising CI Determinism

## System Constraints
You are a Principal Engineer enforcing strict adherence to Biome 1.9 architecture. Ensure all workspace configurations strictly inherit from the root configuration, VCS git integration is explicitly configured to honor .gitignore, and rule suppressions strictly follow Biome's deterministic comment syntax with mandatory inline rationale.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.clientKind: 'git'`, `vcs.enabled: true`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent accidental scanning of ignored artifacts.
- Engineers MUST NEVER use ESLint suppression directives like `// eslint-disable-next-line` or generic `@ts-ignore` comments to bypass Biome diagnostic checks.
- Inline suppressions MUST strictly use the format `// biome-ignore <category>/<ruleName>: <explanation>` and MUST include an explicit explanation justifying why the rule is suppressed.
- Sub-packages in a monorepo MUST inherit from root configuration using `extends: ['../../biome.json']` rather than duplicating rule definitions or overriding globally enforced invariants.
- CI pipelines MUST ALWAYS run Biome with `--error-on-warnings` and `--check` to guarantee zero-drift enforcement across all teams and branches.

## Bad vs Good Implementations
### Configuration Inheritance and VCS Integration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure `vcs` integration to automatically honor `.gitignore`, duplicates ignore patterns, and misses strict schema-backed workspace definitions.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist", "node_modules", "coverage"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Properly hooks into Git VCS via `vcs.useIgnoreFile: true`, ignores unknown binary formats cleanly, and enforces explicit diagnostic severities.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "files": {
    "ignoreUnknown": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  }
}
```

### Rule Suppression Syntax and Justification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Biome completely ignores ESLint pragmas, and the biome-ignore directive lacks the required explanatory rationale, which causes modern Biome configurations with strict suppression rules to fail.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function processPayload(payload: any): void {
  // biome-ignore lint/suspicious/noDebugger
  debugger;
  console.log(payload);
}
```

#### Production Standard (Correct)
> **Standard**: Uses the canonical Biome 1.9 suppression syntax (`biome-ignore <category>/<rule>: <explanation>`) with deterministic reasoning that passes `--error-on-warnings`.
```typescript
/**
 * Explicit rationale required for biome-ignore
 */
// biome-ignore lint/suspicious/noExplicitAny: Raw untyped RPC payload from third-party vendor webhook
export function processPayload(payload: any): void {
  // biome-ignore lint/suspicious/noConsole: Legitimate diagnostic logging in local worker sandbox
  console.log(payload);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Filesystem MCP
Inspects workspace configurations and confirms deterministic Biome JSON structure across monorepo packages.
Recommended Agent Skills (askills.dev)

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

Biome CLI
Executes single-binary linting, formatting, and CI verification commands (`biome check --error-on-warnings`).
Architectural Specification & Invariant Rationale

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

Deterministic Configuration Inheritance, VCS Integration, and Suppression Invariants in Biome 1.9 defines an industrial-grade behavioral standard for frontend engineering. Biome 1.9 relies on single-binary execution speed and strict configuration inheritance using the 'extends' array across workspaces. Mixing ESLint-style suppression directives, failing to enable VCS integration for ignore file honoring, or using malformed inline suppressions breaks deterministic linting across continuous integration pipelines. 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: ESLint-Style Suppression Comments and Unanchored Biome Configurations Compromising CI Determinism 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 DriftESLint-Style Suppression Comments and Unanchored Biome Configurations Compromising CI DeterminismCritical
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.clientKind

Engineers MUST ALWAYS configure `vcs.clientKind: 'git'`, `vcs.enabled: true`, and `vcs.useIgnoreFile: true` in the root `biome.json` to prevent accidental scanning of 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 ESLint suppression directives like `// eslint-disable-next-line` or generic `@ts-ignore` comments to bypass Biome diagnostic checks.

Engineers MUST NEVER use ESLint suppression directives like `// eslint-disable-next-line` or generic `@ts-ignore` comments to bypass Biome diagnostic checks.

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

Inline suppressions MUST strictly use the format `// biome-ignore <category>/<ruleName>

Inline suppressions MUST strictly use the format `// biome-ignore <category>/<ruleName>: <explanation>` and MUST include an explicit explanation justifying why the rule is suppressed.

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

Sub-packages in a monorepo MUST inherit from root configuration using `extends

Sub-packages in a monorepo MUST inherit from root configuration using `extends: ['../../biome.json']` rather than duplicating rule definitions or overriding globally enforced 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

CI pipelines MUST ALWAYS run Biome with `--error-on-warnings` and `--check` to guarantee zero-drift enforcement across all teams and branches.

CI pipelines MUST ALWAYS run Biome with `--error-on-warnings` and `--check` to guarantee zero-drift enforcement across all teams and branches.

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 Configuration Inheritance, VCS Integration, and Suppression Invariants in Biome 1.9 critical for AI coding assistants?

Biome 1.9 relies on single-binary execution speed and strict configuration inheritance using the 'extends' array across workspaces. Mixing ESLint-style suppression directives, failing to enable VCS integration for ignore file honoring, or using malformed inline suppressions breaks deterministic linting across continuous integration pipelines. 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 (ESLint-Style Suppression Comments and Unanchored Biome Configurations Compromising CI Determinism) 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