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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails

Enforces architectural compliance for Biome 1.9 tooling setups across monorepos and standalone repositories. Mandates deterministic VCS-aware ignore tracking, disciplined configuration inheritance hierarchies, and mandatory justification comments for all inline rule suppressions.

Prohibited Anti-Pattern: Unjustified Bare Rule Suppressions, VCS-Ignored File Leaks, and Monorepo Config Drift

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails - Enforces architectural compliance for Biome 1.9 tooling setups across monorepos and standalone repositories. Mandates deterministic VCS-aware ignore tracking, disciplined configuration inheritance hierarchies, and mandatory justification comments for all inline rule suppressions.
globs: biome.json, biome.jsonc, **/biome.json, **/biome.jsonc, src/**/*.{ts,tsx,js,jsx,json,jsonc}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/biome-config-inheritance-vcs-suppression-standard"
---

# Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unjustified Bare Rule Suppressions, VCS-Ignored File Leaks, and Monorepo Config Drift

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 toolchain governance across enterprise codebases. You must strictly enforce Biome's single-binary configuration standards, deterministic suppression grammar with required reasoning, explicit versioned schemas, and seamless VCS integration to prevent ignore-rule divergence and configuration fragmentation.

## Strict Guidelines
- Engineers MUST ALWAYS provide an explicit, human-readable justification for inline suppressions using the exact syntax `// biome-ignore <category>/<rule>: <explanation>`. Bare suppressions without descriptions MUST NOT be accepted.
- Engineers MUST enable native VCS integration in the root `biome.jsonc` (`vcs.enabled: true`, `vcs.clientKind: 'git'`, `vcs.useIgnoreFile: true`) to ensure `.gitignore` patterns are deterministically honored without duplicate configuration files.
- Monorepo packages MUST inherit shared configurations via the `extends` property (e.g., `extends: ['../../biome.jsonc']`) rather than redeclaring entire linter and formatter definitions.
- Every `biome.json` or `biome.jsonc` MUST declare a pinned `$schema` matching the installed Biome binary version (e.g., `https://biomejs.dev/schemas/1.9.4/schema.json`) to enforce strict type checking on compiler options.
- Engineers MUST NOT commit legacy tooling suppression comments (such as `// eslint-disable-next-line` or `// prettier-ignore`) in codebases governed by Biome.

## Bad vs Good Implementations
### Deterministic Suppression Syntax with Explanatory Reason

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Biome 1.9 deprecates and warns against bare rule suppressions lacking an explanatory reason after the rule name, degrading architectural auditability.
```typescript
// biome-ignore lint/suspicious/noExplicitAny
export function deserializePayload(raw: string): any {
  return JSON.parse(raw);
}
```

#### Production Standard (Correct)
> **Standard**: The suppression explicitly names the category, rule name, and provides a clear audit trail rationale separated by a colon.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: third-party webhook payload schema is polymorphic and validated at runtime via Zod
export function deserializePayload(raw: string): any {
  return JSON.parse(raw);
}
```

### Industrial-Grade Biome 1.9 Root Configuration (`biome.jsonc`)

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Missing `$schema` causes loss of IDE diagnostics, manual ignore lists duplicate `.gitignore` leading to drift, and VCS integration is omitted.
```json
{
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  },
  "formatter": {
    "enabled": true
  },
  "files": {
    "ignore": ["node_modules", "dist", "build", ".next"]
  }
}
```

#### Production Standard (Correct)
> **Standard**: Specifies pinned schema URL, binds directly to Git's ignore mechanics, and establishes strict formatting and linting baselines.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 2,
    "lineWidth": 100
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "suspicious": {
        "noExplicitAny": "warn"
      }
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome CLI Execution Protocol
Standardized MCP wrapper to run `biome check --write` and parse machine-readable diagnostic outputs directly within the agent workflow.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Automated skill executing Biome 1.9 single-binary linting, formatting, and imports sorting against staged VCS changes.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails defines an industrial-grade behavioral standard for frontend engineering. Enforces architectural compliance for Biome 1.9 tooling setups across monorepos and standalone repositories. Mandates deterministic VCS-aware ignore tracking, disciplined configuration inheritance hierarchies, and mandatory justification comments for all inline rule suppressions. 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: Unjustified Bare Rule Suppressions, VCS-Ignored File Leaks, and Monorepo Config Drift 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 DriftUnjustified Bare Rule Suppressions, VCS-Ignored File Leaks, and Monorepo Config DriftCritical
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 provide an explicit, human-readable justification for inline suppressions using the exact syntax `// biome-ignore <category>/<rule>

Engineers MUST ALWAYS provide an explicit, human-readable justification for inline suppressions using the exact syntax `// biome-ignore <category>/<rule>: <explanation>`. Bare suppressions without descriptions MUST NOT be accepted.

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 enable native VCS integration in the root `biome.jsonc` (`vcs.enabled

Engineers MUST enable native VCS integration in the root `biome.jsonc` (`vcs.enabled: true`, `vcs.clientKind: 'git'`, `vcs.useIgnoreFile: true`) to ensure `.gitignore` patterns are deterministically honored without duplicate configuration 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.
3

Monorepo packages MUST inherit shared configurations via the `extends` property (e.g., `extends

Monorepo packages MUST inherit shared configurations via the `extends` property (e.g., `extends: ['../../biome.jsonc']`) rather than redeclaring entire linter and formatter definitions.

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

Every `biome.json` or `biome.jsonc` MUST declare a pinned `$schema` matching the installed Biome binary version (e.g., `https

Every `biome.json` or `biome.jsonc` MUST declare a pinned `$schema` matching the installed Biome binary version (e.g., `https://biomejs.dev/schemas/1.9.4/schema.json`) to enforce strict type checking on compiler 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.
5

Engineers MUST NOT commit legacy tooling suppression comments (such as `// eslint-disable-next-line` or `// prettier-ignore`) in codebases governed by Biome.

Engineers MUST NOT commit legacy tooling suppression comments (such as `// 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.
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 Suppression Guardrails critical for AI coding assistants?

Enforces architectural compliance for Biome 1.9 tooling setups across monorepos and standalone repositories. Mandates deterministic VCS-aware ignore tracking, disciplined configuration inheritance hierarchies, and mandatory justification comments for all inline rule suppressions. 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 (Unjustified Bare Rule Suppressions, VCS-Ignored File Leaks, and Monorepo Config Drift) 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