It covers the 2026 arbitrage between the two — new projects default to Biome for a fast
zero-config start, established/typed-heavy codebases lean ESLint + typescript-eslint — plus
a note on Oxlint as a challenger, and the rule to never run Biome and Prettier on the same
files.
Out of scope: type checking itself (tsc --noEmit, tsconfig flags) belongs to ts-config;
test-runner configuration belongs to ts-testing.
TypeScript Linting & Formatting
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Detect existing lint/format config, project age, framework
- fuse-ai-pilot:research-expert - Verify latest Biome 2.x + typescript-eslint via Context7/Exa
- mcp__context7__query-docs - Check Biome and typescript-eslint docs
After implementation, run fuse-ai-pilot:sniper for validation.
Use when
- Choosing a linter/formatter stack for a TS project (new vs established codebase)
- Configuring Biome 2.x (
biome.json, biome check, domains, type-aware rules)
- Configuring ESLint 9 flat config + typescript-eslint typed linting
- Migrating from ESLint+Prettier, or adding a CI lint gate
Do NOT use for
- Runtime execution → use ts-runtime-node / ts-runtime-bun
- Framework-specific style rules owned by that framework's own config
- Type checking itself — linters complement, never replace,
tsc --noEmit
Critical Rules
- Pick ONE formatter - Biome formats AND lints in one binary; do not also run Prettier on the same files.
- Type-aware linting needs the type checker -
typescript-eslint typed rules and Biome's type-aware rules both cost a build pass; expect them to be slower than syntactic rules.
- Biome does NOT format-lint - It never reports formatting via lint rules; the formatter owns all formatting decisions.
- ESLint 9 = flat config - Use
eslint.config.mjs with typescript-eslint's tseslint.configs.*; legacy .eslintrc is deprecated.
- Coverage gap is real - Biome's type-aware rules cover ~75% of typed-linting needs; full cross-file narrowing and
no-unsafe-* still require typescript-eslint.
Architecture
project/
├── biome.json # Biome path: one binary, format + lint
│ OR
├── eslint.config.mjs # ESLint path: flat config + typescript-eslint
├── .prettierrc # (only on ESLint path; Biome replaces Prettier)
└── tsconfig.json # required for typed linting (both tools)
→ See config-examples.md for both stacks
Reference Guide
Concepts
| Topic |
Reference |
When to Consult |
| Tool choice (2026) |
tool-choice.md |
Deciding Biome vs ESLint; Oxlint challenger |
| Biome setup |
biome-setup.md |
Configuring biome.json, rules, domains, CI |
| ESLint typed |
eslint-typed.md |
Flat config + typescript-eslint typed linting |
Templates
| Template |
When to Use |
| config-examples.md |
Copy a Biome or ESLint config into a project |
Best Practices
DO
- New project → default to Biome 2.x (one binary, fast, zero-config start)
- Established/typed-heavy codebase → ESLint 9 + typescript-eslint typed linting
- Run the linter in CI with
error severity to gate merges
DON'T
- Run Biome and Prettier on the same files (conflicting formatting)
- Enable typed linting and then complain about speed — it's the type checker cost
- Assume Biome covers every typescript-eslint rule — check the gaps first
1---2name: ts-lint-format3description: Use when choosing or configuring a TS linter/formatter — Biome 2.x vs ESLint 9 flat config + typescript-eslint typed linting. Not for type checking itself (ts-config).4versions:5 biome: "2.x"6 eslint: "9 (flat config)"7 typescript-eslint: "8.x"8 typescript: "5.8+ (latest stable 6.0)"9references: references/tool-choice.md, references/biome-setup.md, references/eslint-typed.md, references/templates/config-examples.md10related-skills: ts-runtime-node, ts-runtime-bun, solid-generic11metadata:12 source: https://skillmd.com/skills/fusengine/ts-lint-format13---1415<objective>16This skill covers choosing and configuring a TypeScript linting/formatting stack: Biome 2.x17as a single binary that formats and lints (biome.json, domains, type-aware rules covering18~75% of typed-linting needs) versus ESLint 9 flat config (eslint.config.mjs) with19typescript-eslint for full typed linting including cross-file narrowing and no-unsafe-*20rules.2122It covers the 2026 arbitrage between the two — new projects default to Biome for a fast23zero-config start, established/typed-heavy codebases lean ESLint + typescript-eslint — plus24a note on Oxlint as a challenger, and the rule to never run Biome and Prettier on the same25files.2627Out of scope: type checking itself (tsc --noEmit, tsconfig flags) belongs to ts-config;28test-runner configuration belongs to ts-testing.29</objective>3031# TypeScript Linting & Formatting3233## Agent Workflow (MANDATORY)3435Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:36371. **fuse-ai-pilot:explore-codebase** - Detect existing lint/format config, project age, framework382. **fuse-ai-pilot:research-expert** - Verify latest Biome 2.x + typescript-eslint via Context7/Exa393. **mcp__context7__query-docs** - Check Biome and typescript-eslint docs4041After implementation, run **fuse-ai-pilot:sniper** for validation.4243## Use when4445- Choosing a linter/formatter stack for a TS project (new vs established codebase)46- Configuring **Biome 2.x** (`biome.json`, `biome check`, domains, type-aware rules)47- Configuring **ESLint 9 flat config** + **typescript-eslint** typed linting48- Migrating from ESLint+Prettier, or adding a CI lint gate4950## Do NOT use for5152- Runtime execution → use [ts-runtime-node](../ts-runtime-node/SKILL.md) / [ts-runtime-bun](../ts-runtime-bun/SKILL.md)53- Framework-specific style rules owned by that framework's own config54- Type checking itself — linters complement, never replace, `tsc --noEmit`5556## Critical Rules57581. **Pick ONE formatter** - Biome formats AND lints in one binary; do not also run Prettier on the same files.592. **Type-aware linting needs the type checker** - `typescript-eslint` typed rules and Biome's type-aware rules both cost a build pass; expect them to be slower than syntactic rules.603. **Biome does NOT format-lint** - It never reports formatting via lint rules; the formatter owns all formatting decisions.614. **ESLint 9 = flat config** - Use `eslint.config.mjs` with `typescript-eslint`'s `tseslint.configs.*`; legacy `.eslintrc` is deprecated.625. **Coverage gap is real** - Biome's type-aware rules cover ~75% of typed-linting needs; full cross-file narrowing and `no-unsafe-*` still require typescript-eslint.6364## Architecture6566```67project/68├── biome.json # Biome path: one binary, format + lint69│ OR70├── eslint.config.mjs # ESLint path: flat config + typescript-eslint71├── .prettierrc # (only on ESLint path; Biome replaces Prettier)72└── tsconfig.json # required for typed linting (both tools)73```7475→ See [config-examples.md](references/templates/config-examples.md) for both stacks7677## Reference Guide7879### Concepts8081| Topic | Reference | When to Consult |82|-------|-----------|-----------------|83| **Tool choice (2026)** | [tool-choice.md](references/tool-choice.md) | Deciding Biome vs ESLint; Oxlint challenger |84| **Biome setup** | [biome-setup.md](references/biome-setup.md) | Configuring `biome.json`, rules, domains, CI |85| **ESLint typed** | [eslint-typed.md](references/eslint-typed.md) | Flat config + typescript-eslint typed linting |8687### Templates8889| Template | When to Use |90|----------|-------------|91| [config-examples.md](references/templates/config-examples.md) | Copy a Biome or ESLint config into a project |9293## Best Practices9495### DO96- New project → default to **Biome 2.x** (one binary, fast, zero-config start)97- Established/typed-heavy codebase → **ESLint 9 + typescript-eslint** typed linting98- Run the linter in CI with `error` severity to gate merges99100### DON'T101- Run Biome and Prettier on the same files (conflicting formatting)102- Enable typed linting and then complain about speed — it's the type checker cost103- Assume Biome covers every typescript-eslint rule — check the gaps first