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

Biome 1.9 Configuration Inheritance, VCS Integration, and Suppression Guardrails

Enforces deterministic Biome 1.9 configuration governance across monorepos and standalone workspaces. Mandates explicit Git VCS integration with ignore-file synchronization, rigid schema inheritance via extends, and syntactically strict inline rule suppressions requiring mandatory human-readable justifications.

Prohibited Anti-Pattern: Uncontrolled Lint Ingestion via Broken VCS Ignores and Justification-Free 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 Suppression Guardrails - Enforces deterministic Biome 1.9 configuration governance across monorepos and standalone workspaces. Mandates explicit Git VCS integration with ignore-file synchronization, rigid schema inheritance via extends, and syntactically strict inline rule suppressions requiring mandatory human-readable justifications.
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-inheritance-suppression-standard"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncontrolled Lint Ingestion via Broken VCS Ignores and Justification-Free Rule Suppressions

## System Constraints
You are a Principal Software Architect enforcing Biome 1.9 standards across TypeScript codebases. Ensure all configuration files leverage root extends patterns, deterministic VCS gitignore integration, and correct inline suppression syntax.

## Strict Guidelines
- Engineers MUST configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json' to prevent linting build artifacts and ignored files.
- Engineers MUST NOT retain legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line') in Biome-managed repositories.
- Code MUST format suppressions using the exact single-line syntax: '// biome-ignore <group>/<rule>: <explanation>' or '// biome-ignore lint/<group>/<rule>: <explanation>' with a non-empty rationale.
- Services MUST inherit shared configurations via the top-level 'extends' array using relative filesystem paths or resolved npm packages.
- Monorepo package configurations MUST extend root configurations rather than redefining root formatter and linter invariants independently.

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

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to declare VCS integration, causing Biome CLI and LSP to process files ignored by git unless manually duplicated in files.ignore. Lacks monorepo extends inheritance.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "files": {
    "ignore": ["dist/**", "node_modules/**"]
  },
  "linter": {
    "enabled": true
  }
}
```

#### Production Standard (Correct)
> **Standard**: Inherits base configuration deterministic rules, activates native Git VCS integration, and automatically synchronizes with .gitignore without redundant glob arrays.
```json
{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.base.json"],
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true,
    "defaultBranch": "main"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}
```

### TypeScript Inline Rule Suppression

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses dead ESLint suppression syntax that Biome ignores, coupled with an explanation-free Biome suppression that violates deterministic auditability.
```typescript
// eslint-disable-next-line @typescript-eslint/no-explicit-any
export function deserializeUnsafePayload(data: string): any {
  // biome-ignore lint/suspicious/noExplicitAny
  return JSON.parse(data) as any;
}
```

#### Production Standard (Correct)
> **Standard**: Applies correct Biome 1.9 suppression syntax with the required lint group and an explicit explanation explaining why the rule must be bypassed.
```typescript
export function deserializeUnsafePayload(data: string): unknown {
  // biome-ignore lint/suspicious/noExplicitAny: Required boundary cast for external untyped RPC payload before schema validation
  return JSON.parse(data) as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Local Filesystem Server
Inspect and synchronize workspace biome.json and .gitignore configurations.
Recommended Agent Skills (askills.dev)

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

Biome CLI Runner
Executes biome check --changed and format validation directly against git staged files.
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 deterministic Biome 1.9 configuration governance across monorepos and standalone workspaces. Mandates explicit Git VCS integration with ignore-file synchronization, rigid schema inheritance via extends, and syntactically strict inline rule suppressions requiring mandatory human-readable justifications. 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: Uncontrolled Lint Ingestion via Broken VCS Ignores and Justification-Free 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 DriftUncontrolled Lint Ingestion via Broken VCS Ignores and Justification-Free 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 configure 'vcs.enabled

Engineers MUST configure 'vcs.enabled: true', 'vcs.clientKind: "git"', and 'vcs.useIgnoreFile: true' in root 'biome.json' to prevent linting build artifacts and ignored 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.
2

Engineers MUST NOT retain legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line') in Biome-managed repositories.

Engineers MUST NOT retain legacy ESLint/Prettier suppression directives (e.g., '// eslint-disable-next-line') in Biome-managed repositories.

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

Code MUST format suppressions using the exact single-line syntax

Code MUST format suppressions using the exact single-line syntax: '// biome-ignore <group>/<rule>: <explanation>' or '// biome-ignore lint/<group>/<rule>: <explanation>' with a non-empty rationale.

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

Services MUST inherit shared configurations via the top-level 'extends' array using relative filesystem paths or resolved npm packages.

Services MUST inherit shared configurations via the top-level 'extends' array using relative filesystem paths or resolved npm packages.

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 package configurations MUST extend root configurations rather than redefining root formatter and linter invariants independently.

Monorepo package configurations MUST extend root configurations rather than redefining root formatter and linter invariants independently.

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 deterministic Biome 1.9 configuration governance across monorepos and standalone workspaces. Mandates explicit Git VCS integration with ignore-file synchronization, rigid schema inheritance via extends, and syntactically strict inline rule suppressions requiring mandatory human-readable justifications. 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 (Uncontrolled Lint Ingestion via Broken VCS Ignores and Justification-Free 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