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-vcs-suppression-deterministic-config

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

Enforces strict Biome 1.9 configuration governance across monorepos and standalone repositories using schema pinning, declarative VCS ignore syncing, and deterministic rule suppression syntax. Mandates exact suppression target specifiers with required inline human rationales while forbidding legacy ESLint/Prettier annotations.

Prohibited Anti-Pattern: Unexplained Global Lint Disables, Missing Git VCS Ignore Sync, and Legacy Linter Annotations

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Deterministic Suppression - Enforces strict Biome 1.9 configuration governance across monorepos and standalone repositories using schema pinning, declarative VCS ignore syncing, and deterministic rule suppression syntax. Mandates exact suppression target specifiers with required inline human rationales while forbidding legacy ESLint/Prettier annotations.
globs: biome.json, biome.jsonc, src/**/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-vcs-suppression-deterministic-config"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unexplained Global Lint Disables, Missing Git VCS Ignore Sync, and Legacy Linter Annotations

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 single-binary linter and formatter standards. You must ensure all Biome configurations explicitly declare pinned schemas, integrate with Git-aware VCS ignore files, and strictly govern configuration inheritance across workspace boundaries. You must reject all legacy ESLint/Prettier annotations and require that all Biome suppressions follow the canonical `// biome-ignore <category>/<group>/<rule>: <explanation>` format with an explicit rationale.

## Strict Guidelines
- Engineers MUST ALWAYS specify an explicit human rationale when suppressing rules: `// biome-ignore lint/<group>/<rule>: <explanation>`.
- Engineers MUST NOT use unanchored or category-wide suppressions (e.g., `// biome-ignore lint`) or omit the trailing colon and justification.
- Engineers MUST NOT commit legacy ESLint, TSLint, or Prettier directive comments (e.g., `// eslint-disable`, `// prettier-ignore`).
- Configuration files (biome.json/biome.jsonc) MUST declare the exact schema version URL (`https://biomejs.dev/schemas/1.9.4/schema.json`) and configure `vcs.clientKind: "git"` with `vcs.useIgnoreFile: true`.
- Workspace packages in a monorepo MUST inherit common rules from the repository root using `extends: ["//biome.json"]` or relative path arrays, overriding only package-specific options.
- Deterministic import organization MUST be enabled via `organizeImports.enabled: true` in Biome rather than relying on external conflicting plugins.
- Services MUST execute `biome check --write` in pre-commit hooks and `biome ci` within automated validation pipelines.

## Bad vs Good Implementations
### Deterministic Rule Suppression in TypeScript

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses legacy ESLint and TypeScript suppressions alongside an unanchored Biome suppression without an exact rule path or deterministic architectural rationale.
```typescript
// eslint-disable-next-line
export function deserializePayload(payload: string): any {
  // @ts-ignore
  const parsed = JSON.parse(payload);
  // biome-ignore lint: need to bypass
  console.log('Payload processed', parsed);
  return parsed;
}
```

#### Production Standard (Correct)
> **Standard**: Replaces insecure `any` typing, eliminates legacy lint directives, and anchors the Biome suppression to `lint/suspicious/noConsole` with a clear explanation.
```typescript
export function deserializePayload(payload: string): unknown {
  const parsed: unknown = JSON.parse(payload);
  // biome-ignore lint/suspicious/noConsole: Required for standard output streaming in serverless runtime entrypoint
  console.log('Payload processed', parsed);
  return parsed;
}
```

### Biome 1.9 Base Configuration with VCS Integration and Inheritance

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` definition, omits VCS Git client configuration causing formatting drift on gitignored files, and fails to enable deterministic import organization.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Pins the explicit 1.9.4 schema, synchronizes with Git ignore boundaries, enables deterministic import ordering, and enforces strict linting invariants.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "organizeImports": {
    "enabled": true
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "error"
      }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Model Context Protocol Filesystem Server
Inspects and manages biome.json configuration files and workspace inheritance trees across the repository.
Recommended Agent Skills (askills.dev)

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

Biome CLI Diagnostics Skill
Executes single-binary biome check, lint, and format commands with zero runtime node overhead.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Deterministic Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces strict Biome 1.9 configuration governance across monorepos and standalone repositories using schema pinning, declarative VCS ignore syncing, and deterministic rule suppression syntax. Mandates exact suppression target specifiers with required inline human rationales while forbidding legacy ESLint/Prettier annotations. 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: Unexplained Global Lint Disables, Missing Git VCS Ignore Sync, and Legacy Linter Annotations 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 DriftUnexplained Global Lint Disables, Missing Git VCS Ignore Sync, and Legacy Linter AnnotationsCritical
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 specify an explicit human rationale when suppressing rules

Engineers MUST ALWAYS specify an explicit human rationale when suppressing rules: `// 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.
2

Engineers MUST NOT use unanchored or category-wide suppressions (e.g., `// biome-ignore lint`) or omit the trailing colon and justification.

Engineers MUST NOT use unanchored or category-wide suppressions (e.g., `// biome-ignore lint`) or omit the trailing colon and 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

Engineers MUST NOT commit legacy ESLint, TSLint, or Prettier directive comments (e.g., `// eslint-disable`, `// prettier-ignore`).

Engineers MUST NOT commit legacy ESLint, TSLint, or Prettier directive comments (e.g., `// eslint-disable`, `// prettier-ignore`).

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

Configuration files (biome.json/biome.jsonc) MUST declare the exact schema version URL (`https

Configuration files (biome.json/biome.jsonc) MUST declare the exact schema version URL (`https://biomejs.dev/schemas/1.9.4/schema.json`) and configure `vcs.clientKind: "git"` with `vcs.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.
5

Workspace packages in a monorepo MUST inherit common rules from the repository root using `extends

Workspace packages in a monorepo MUST inherit common rules from the repository root using `extends: ["//biome.json"]` or relative path arrays, overriding only package-specific options.

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

Deterministic import organization MUST be enabled via `organizeImports.enabled

Deterministic import organization MUST be enabled via `organizeImports.enabled: true` in Biome rather than relying on external conflicting plugins.

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.
7

Services MUST execute `biome check --write` in pre-commit hooks and `biome ci` within automated validation pipelines.

Services MUST execute `biome check --write` in pre-commit hooks and `biome ci` within automated validation 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 Strict Deterministic Suppression critical for AI coding assistants?

Enforces strict Biome 1.9 configuration governance across monorepos and standalone repositories using schema pinning, declarative VCS ignore syncing, and deterministic rule suppression syntax. Mandates exact suppression target specifiers with required inline human rationales while forbidding legacy ESLint/Prettier annotations. 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 (Unexplained Global Lint Disables, Missing Git VCS Ignore Sync, and Legacy Linter Annotations) 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