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-vcs-suppression-guardrails

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Suppression

Mandates deterministic monorepo configuration via Biome 1.9 extends syntax, binds discovery directly to Git VCS ignore manifests to eliminate filesystem desync, and requires fully justified inline suppression syntax. Prevents unanchored artifact scanning, legacy ESLint directive leakage, and silent suppression debt.

Prohibited Anti-Pattern: Unanchored Artifact Traversals, Zombie ESLint Directives, and Unjustified Biome 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 Suppression - Mandates deterministic monorepo configuration via Biome 1.9 extends syntax, binds discovery directly to Git VCS ignore manifests to eliminate filesystem desync, and requires fully justified inline suppression syntax. Prevents unanchored artifact scanning, legacy ESLint directive leakage, and silent suppression debt.
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-vcs-suppression-guardrails"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unanchored Artifact Traversals, Zombie ESLint Directives, and Unjustified Biome Suppressions

## System Constraints
You are a Principal Engineer enforcing Biome 1.9 Single-Binary Linter & Formatter standards. Mandate clean configuration inheritance across monorepo boundaries, enforce Git VCS boundary resolution with .gitignore synchronization, and reject all legacy ESLint annotations or unanchored bare biome-ignore directives lacking explicit technical justification.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `vcs` object with `"clientKind": "git"` and `"useIgnoreFile": true` in the root `biome.json` to prevent processing untracked build artifacts and dependencies.
- Engineers MUST use explicit, granular suppression comments matching `// biome-ignore lint/<category>/<rule>: <explanation>` and MUST NOT omit the trailing explanatory string.
- Engineers MUST NOT introduce or retain legacy linter comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or deprecated `// rome-ignore` tokens.
- Child packages within a monorepo MUST inherit common rules using the `extends` property referencing root configurations (`"extends": ["../../biome.json"]` or shared npm configs) rather than duplicating configuration trees.
- CI pipelines MUST execute `biome check --diagnostic-level=error` to ensure invalid suppression syntax, dead suppressions, and untyped overrides block merge trains immediately.

## Bad vs Good Implementations
### Biome Suppression Syntax and VCS-Aligned Typescript Guardrails

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Uses dead legacy ESLint directives, deprecated Rome annotations, and a bare biome-ignore without the required explanation string, degrading rule telemetry and obfuscating bypass motives.
```typescript
/* eslint-disable @typescript-eslint/no-explicit-any */
// biome-ignore lint/suspicious/noExplicitAny
export async function parsePayload(input: string): Promise<any> {
  // rome-ignore lint/security/noGlobalEval: legacy parser fallback
  const raw = eval(`(${input})`);
  return raw;
}
```

#### Production Standard (Correct)
> **Standard**: Adheres strictly to the Biome 1.9 suppression contract (`// biome-ignore <category>/<rule>: <explanation>`), removes dangerous eval invocation, and avoids obsolete ESLint directives.
```typescript
// biome-ignore lint/suspicious/noExplicitAny: Upstream RPC contract returns polymorphic untyped payloads until v3 migration
export async function parsePayload(input: string): Promise<any> {
  // Parse securely without arbitrary code execution vulnerabilities
  const raw: unknown = JSON.parse(input);
  return raw as any;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Biome Language Server Protocol MCP
Exposes Biome 1.9 diagnostics, deterministic formatting, and quick-fix code actions directly to the AI agent runtime.
Recommended Agent Skills (askills.dev)

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

Biome CLI Execution Helper
Executes single-binary deterministic biome check and format operations with zero-dependency native execution.
Architectural Specification & Invariant Rationale

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

Biome 1.9 Configuration Inheritance, VCS Integration, and Strict Suppression defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic monorepo configuration via Biome 1.9 extends syntax, binds discovery directly to Git VCS ignore manifests to eliminate filesystem desync, and requires fully justified inline suppression syntax. Prevents unanchored artifact scanning, legacy ESLint directive leakage, and silent suppression debt. 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 Artifact Traversals, Zombie ESLint Directives, and Unjustified Biome 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 DriftUnanchored Artifact Traversals, Zombie ESLint Directives, and Unjustified Biome 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 the `vcs` object with `"clientKind"

Engineers MUST ALWAYS configure the `vcs` object with `"clientKind": "git"` and `"useIgnoreFile": true` in the root `biome.json` to prevent processing untracked build artifacts and dependencies.

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 use explicit, granular suppression comments matching `// biome-ignore lint/<category>/<rule>

Engineers MUST use explicit, granular suppression comments matching `// biome-ignore lint/<category>/<rule>: <explanation>` and MUST NOT omit the trailing explanatory string.

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 introduce or retain legacy linter comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or deprecated `// rome-ignore` tokens.

Engineers MUST NOT introduce or retain legacy linter comments such as `/* eslint-disable */`, `// eslint-disable-next-line`, or deprecated `// rome-ignore` tokens.

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

Child packages within a monorepo MUST inherit common rules using the `extends` property referencing root configurations (`"extends"

Child packages within a monorepo MUST inherit common rules using the `extends` property referencing root configurations (`"extends": ["../../biome.json"]` or shared npm configs) rather than duplicating configuration trees.

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

CI pipelines MUST execute `biome check --diagnostic-level=error` to ensure invalid suppression syntax, dead suppressions, and untyped overrides block merge trains immediately.

CI pipelines MUST execute `biome check --diagnostic-level=error` to ensure invalid suppression syntax, dead suppressions, and untyped overrides block merge trains immediately.

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

Mandates deterministic monorepo configuration via Biome 1.9 extends syntax, binds discovery directly to Git VCS ignore manifests to eliminate filesystem desync, and requires fully justified inline suppression syntax. Prevents unanchored artifact scanning, legacy ESLint directive leakage, and silent suppression debt. 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 Artifact Traversals, Zombie ESLint Directives, and Unjustified Biome 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