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

Biome 1.9 Configuration Inheritance, Git VCS Integration, and Strict Rule Suppression

Enforces Biome 1.9 architectural standards across monorepos and standalone frontend packages. Mandates explicit Git VCS integration to prevent redundant ignore drift, structured multi-layer configuration inheritance via extends, and deterministic inline rule suppression with mandatory explanatory justification tokens.

Prohibited Anti-Pattern: Unanchored ignore glob divergence, legacy ESLint suppression comments, and naked biome-ignore directives lacking reason tokens.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, Git VCS Integration, and Strict Rule Suppression - Enforces Biome 1.9 architectural standards across monorepos and standalone frontend packages. Mandates explicit Git VCS integration to prevent redundant ignore drift, structured multi-layer configuration inheritance via extends, and deterministic inline rule suppression with mandatory explanatory justification tokens.
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-1-9-config-inheritance-vcs-suppression-standard"
---

# Biome 1.9 Configuration Inheritance, Git VCS Integration, and Strict Rule Suppression

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored ignore glob divergence, legacy ESLint suppression comments, and naked biome-ignore directives lacking reason tokens.

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 linter and formatter invariants across enterprise frontend projects. Enforce proper configuration hierarchy (biome.jsonc inheritance), direct VCS Git alignment with useIgnoreFile, and strict deterministic suppression comment formatting (biome-ignore <ruleGroup>/<ruleName>: <reason>). Reject any legacy ESLint/Prettier suppression annotations and non-deterministic unannotated ignore tags.

## Strict Guidelines
- Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.jsonc` to honor `.gitignore` files deterministically without duplicate glob lists.
- Engineers MUST ALWAYS provide an explicit explanation after the colon in suppression comments using the deterministic Biome 1.9 syntax: `// biome-ignore <group>/<rule>: <explanation>`.
- Engineers MUST NOT use legacy comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or `// prettier-ignore` in codebases governed by Biome.
- Engineers MUST NOT issue bare `// biome-ignore` or `// biome-ignore-all` without both the explicit rule path (e.g., `lint/suspicious/noExplicitAny`) and a descriptive reason.
- Monorepo packages MUST inherit shared architectural rule presets using relative paths in the `extends` property (`extends: ['../../biome.base.jsonc']`), overriding only package-specific globals and domain constraints.
- Codebases SHOULD use `biome.jsonc` instead of `biome.json` to allow in-source documentation of linting overrides and architectural boundary declarations.

## Bad vs Good Implementations
### Suppression Comment Formatting and Legacy Rule Migration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses inert ESLint directive comments ignored by Biome, a naked `// biome-ignore` without rule path, and a suppression lacking the required colon and reason explanation token.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(raw: string): any {
  // biome-ignore
  const payload = JSON.parse(raw);
  // biome-ignore lint/suspicious/noDoubleEquals
  if (payload.status == 200) {
    return payload.data;
  }
  return null;
}
```

#### Production Standard (Correct)
> **Standard**: Applies compliant Biome 1.9 syntax including fully qualified rule groups (`lint/suspicious/...`) followed by mandatory explanatory justification tokens after the colon.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Upstream third-party webhook payload is unstructured dynamic JSON
export function deserializePayload(raw: string): any {
  const payload = JSON.parse(raw) as Record<string, unknown>;
  // biome-ignore lint/suspicious/noDoubleEquals: Coercion required for legacy API returning numeric strings
  if (payload.status == 200) {
    return payload.data;
  }
  return null;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Execution MCP
Executes single-binary Biome check, format, and lint commands directly against current workspaces.
Recommended Agent Skills (askills.dev)

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

Biome 1.9 CLI Tooling
Runs `biome check --write --vcs-client-kind=git` to format, lint, and sort imports deterministically.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, Git VCS Integration, and Strict Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces Biome 1.9 architectural standards across monorepos and standalone frontend packages. Mandates explicit Git VCS integration to prevent redundant ignore drift, structured multi-layer configuration inheritance via extends, and deterministic inline rule suppression with mandatory explanatory justification tokens. 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 ignore glob divergence, legacy ESLint suppression comments, and naked biome-ignore directives lacking reason tokens. 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 ignore glob divergence, legacy ESLint suppression comments, and naked biome-ignore directives lacking reason tokens.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 configure `vcs.enabled

Engineers MUST ALWAYS configure `vcs.enabled: true`, `vcs.clientKind: 'git'`, and `vcs.useIgnoreFile: true` in the root `biome.jsonc` to honor `.gitignore` files deterministically without duplicate glob lists.

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 explanation after the colon in suppression comments using the deterministic Biome 1.9 syntax

Engineers MUST ALWAYS provide an explicit explanation after the colon in suppression comments using the deterministic Biome 1.9 syntax: `// 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 comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or `// prettier-ignore` in codebases governed by Biome.

Engineers MUST NOT use legacy comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or `// prettier-ignore` in codebases governed by Biome.

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 issue bare `// biome-ignore` or `// biome-ignore-all` without both the explicit rule path (e.g., `lint/suspicious/noExplicitAny`) and a descriptive reason.

Engineers MUST NOT issue bare `// biome-ignore` or `// biome-ignore-all` without both the explicit rule path (e.g., `lint/suspicious/noExplicitAny`) and a descriptive reason.

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 architectural rule presets using relative paths in the `extends` property (`extends

Monorepo packages MUST inherit shared architectural rule presets using relative paths in the `extends` property (`extends: ['../../biome.base.jsonc']`), overriding only package-specific globals and domain constraints.

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

Codebases SHOULD use `biome.jsonc` instead of `biome.json` to allow in-source documentation of linting overrides and architectural boundary declarations.

Codebases SHOULD use `biome.jsonc` instead of `biome.json` to allow in-source documentation of linting overrides and architectural boundary declarations.

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

Enforces Biome 1.9 architectural standards across monorepos and standalone frontend packages. Mandates explicit Git VCS integration to prevent redundant ignore drift, structured multi-layer configuration inheritance via extends, and deterministic inline rule suppression with mandatory explanatory justification tokens. 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 ignore glob divergence, legacy ESLint suppression comments, and naked biome-ignore directives lacking reason tokens.) 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