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

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

Enforces deterministic Biome 1.9+ architecture across TypeScript workspaces by mandating centralized config inheritance, canonical Git VCS ignore integration, and strict, rationale-backed suppression comments. Eliminates configuration drift across monorepos and prevents unvetted static analysis bypasses.

Prohibited Anti-Pattern: Ad-Hoc Tool Configuration Drift and Unjustified Naked Rule Suppressions

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 Rule Suppression - Enforces deterministic Biome 1.9+ architecture across TypeScript workspaces by mandating centralized config inheritance, canonical Git VCS ignore integration, and strict, rationale-backed suppression comments. Eliminates configuration drift across monorepos and prevents unvetted static analysis bypasses.
globs: biome.json, biome.jsonc, packages/**/biome.json, 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-deterministic-suppression"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Ad-Hoc Tool Configuration Drift and Unjustified Naked Rule Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards. Mandate zero configuration drift via 'extends', single-source-of-truth file exclusions via the native Git VCS integration ('useIgnoreFile'), and strictly verified suppression comment syntax ('// biome-ignore <group>/<rule>: <explanation>'). Reject any legacy ESLint/Prettier directives, unprincipled blanket ignore globs, or unexplained suppressions.

## Strict Guidelines
- Engineers MUST ALWAYS configure VCS-aware file resolution in root 'biome.json' ('vcs.enabled: true', 'vcs.clientKind: "git"', 'vcs.useIgnoreFile: true') to eliminate duplicate ignore-list maintenance.
- Engineers MUST ALWAYS supply an actionable justification when suppressing a rule using the format: '// biome-ignore <group>/<rule>: <justification>'.
- Monorepo packages MUST inherit shared configuration via 'extends: ["@org/biome-config"]' or relative root paths instead of redefining foundational rules.
- Engineers MUST NOT use naked Biome suppressions missing the reason payload or omit the category group prefix (e.g. '// biome-ignore noExplicitAny' is prohibited).
- Engineers MUST NOT retain obsolete ESLint/Prettier suppressions ('// eslint-disable', '/* prettier-ignore */') in Biome-governed projects.
- Workspace overrides MUST target specific globs using the top-level 'overrides' array rather than relying on distributed, inconsistent package-level root configurations.

## Bad vs Good Implementations
### Root Biome 1.9 Configuration with VCS Integration and Schema Validation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits the '$schema' version lock, manually duplicates files already defined in '.gitignore' without VCS delegation, and lacks deterministic rule group governance.
```json
{
  "linter": {
    "enabled": true
  },
  "formatter": {
    "enabled": true
  },
  "files": {
    "ignore": ["node_modules", "dist", "build", ".turbo", ".next"]
  }
}
```

#### Production Standard (Correct)
> **Standard**: Locks schema to Biome 1.9.4, delegates file exclusion directly to Git's ignore engine, and explicitly enforces formatter and recommended linter rules.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedVariables": "error"
      }
    }
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  }
}
```

### Deterministic Rule Suppression in TypeScript Source Code

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses obsolete ESLint directives and provides an unexplained Biome suppression without the mandatory colon and rationale.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializePayload(raw: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(raw) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Uses the exact Biome 1.9 suppression syntax including group name, rule name, and an explicit, auditable rationale explaining why the bypass is necessary.
```typescript
export function deserializePayload(raw: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Boundary adapter handles polymorphic wire protocols before schema validation
  return JSON.parse(raw) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Filesystem MCP
Allows the agent to read and validate biome.json configs and workspace boundary hierarchies directly.
Recommended Agent Skills (askills.dev)

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

Biome CLI Executor
Runs 'biome check --write --vcs-client-kind=git' for high-performance formatting and lint verification.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Rule Suppression defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic Biome 1.9+ architecture across TypeScript workspaces by mandating centralized config inheritance, canonical Git VCS ignore integration, and strict, rationale-backed suppression comments. Eliminates configuration drift across monorepos and prevents unvetted static analysis bypasses. 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: Ad-Hoc Tool Configuration Drift and Unjustified Naked Rule 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 DriftAd-Hoc Tool Configuration Drift and Unjustified Naked Rule SuppressionsCritical
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-aware file resolution in root 'biome.json' ('vcs.enabled

Engineers MUST ALWAYS configure VCS-aware file resolution in root 'biome.json' ('vcs.enabled: true', 'vcs.clientKind: "git"', 'vcs.useIgnoreFile: true') to eliminate duplicate ignore-list maintenance.

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 supply an actionable justification when suppressing a rule using the format

Engineers MUST ALWAYS supply an actionable justification when suppressing a rule using the format: '// biome-ignore <group>/<rule>: <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

Monorepo packages MUST inherit shared configuration via 'extends

Monorepo packages MUST inherit shared configuration via 'extends: ["@org/biome-config"]' or relative root paths instead of redefining foundational rules.

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 naked Biome suppressions missing the reason payload or omit the category group prefix (e.g. '// biome-ignore noExplicitAny' is prohibited).

Engineers MUST NOT use naked Biome suppressions missing the reason payload or omit the category group prefix (e.g. '// biome-ignore noExplicitAny' is prohibited).

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 retain obsolete ESLint/Prettier suppressions ('// eslint-disable', '/* prettier-ignore */') in Biome-governed projects.

Engineers MUST NOT retain obsolete ESLint/Prettier suppressions ('// eslint-disable', '/* prettier-ignore */') in Biome-governed projects.

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

Workspace overrides MUST target specific globs using the top-level 'overrides' array rather than relying on distributed, inconsistent package-level root configurations.

Workspace overrides MUST target specific globs using the top-level 'overrides' array rather than relying on distributed, inconsistent package-level root configurations.

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

Enforces deterministic Biome 1.9+ architecture across TypeScript workspaces by mandating centralized config inheritance, canonical Git VCS ignore integration, and strict, rationale-backed suppression comments. Eliminates configuration drift across monorepos and prevents unvetted static analysis bypasses. 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 (Ad-Hoc Tool Configuration Drift and Unjustified Naked Rule 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