biome-knowledge-patch
Biome v2.0-2.4 changes since training cutoff — linter domains, includes replacing ignore/include, assists, GritQL plugins, type-aware linting, Vue/Svelte/Astro full support, embedded snippets. Load before writing Biome config or rules.
What this skill does
# Biome v2.0–v2.4 Knowledge Patch
You know Biome through v1.6.x: basic lint/format for JS/TS/JSX/TSX/JSON, biome.json config, biome check/format/lint commands, Prettier-compatible formatter, ~200 lint rules, partial Astro/Svelte/Vue support.
This patch covers v2.0–v2.4 (2025-06-17 – 2026-02-10).
## Index
| Topic | Reference | Key changes |
|-------|-----------|-------------|
| Configuration & Migration | [references/config-and-migration.md](references/config-and-migration.md) | `files.includes` replaces ignore/include, config discovery, nested configs for monorepos |
| Linting & Plugins | [references/linting-and-plugins.md](references/linting-and-plugins.md) | Linter domains, type-aware linting, suppression comments, GritQL plugins |
| Formatting & Language Support | [references/formatting-and-languages.md](references/formatting-and-languages.md) | Assists, HTML formatter, embedded snippets, Vue/Svelte/Astro, Tailwind v4 CSS |
---
## Quick Reference — Breaking Changes
### `files.includes` replaces `files.ignore` and `files.include`
**This is the most impactful v2 breaking change.** Both fields merged into one.
```json
{
"files": {
"includes": [
"**",
"!**/generated",
"!!**/dist"
]
}
}
```
- Globs no longer auto-prepend `**/` — you must write full patterns
- `*` no longer matches `/`
- Globs are relative to config file location, not working directory
- `!` prefix — skip formatting/linting but still index for types (v2.3)
- `!!` prefix — completely exclude from all Biome operations (v2.3)
See [references/config-and-migration.md](references/config-and-migration.md) for config discovery and monorepo setup.
---
## Quick Reference — Linter Domains
Framework-specific rule groups that auto-activate based on `package.json` dependencies.
| Domain | Activates for |
|--------|---------------|
| `react` | React projects |
| `next` | Next.js projects |
| `solid` | SolidJS projects |
| `vue` | Vue projects |
| `playwright` | Playwright tests |
| `drizzle` | Drizzle ORM |
| `qwik` | Qwik projects |
| `project` | Module graph analysis (import cycles, unresolved imports) |
| `types` | Type inference rules (no TS compiler needed) |
| `test` | Test-specific rules |
```json
{
"linter": {
"domains": {
"react": "recommended",
"next": "all",
"project": "recommended",
"types": "recommended"
}
}
}
```
Values: `"recommended"` (stable rules), `"all"` (including nursery), `"none"`.
CLI: `--only=project`, `--skip=test`.
See [references/linting-and-plugins.md](references/linting-and-plugins.md) for type-aware linting, suppression comments, and GritQL plugins.
---
## Quick Reference — Assists
New category between formatter and linter. Actions without diagnostics. Import organizing moved here from linter.
```json
{
"assist": {
"actions": {
"source": {
"organizeImports": "on",
"useSortedKeys": { "level": "on", "options": { "groupByNesting": true } },
"useSortedAttributes": "on",
"noDuplicateClasses": "on"
}
}
}
}
```
Import organizer revamp: cross-chunk sorting, import merging from same module, custom ordering, export organizing, import attribute sorting.
See [references/formatting-and-languages.md](references/formatting-and-languages.md) for HTML formatter, embedded snippets, and framework support.
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.