ts-lint-format

Configure TypeScript linting and formatting with Biome 2.x or ESLint 9 flat config.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/fusengine/kimi-code --skill ts-lint-format-fusengine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ts-lint-format
Source: https://github.com/fusengine/kimi-code/tree/main/plugins/typescript-expert/skills/ts-lint-format
Command: npx skills add https://github.com/fusengine/kimi-code --skill ts-lint-format-fusengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing and configuring a TypeScript lint/format stack is confusing: Biome 2.x, ESLint 9 flat config with typescript-eslint, Prettier, and Oxlint overlap in scope, and picking the wrong combination leads to conflicting formatters, slow typed linting, or missing rule coverage. ## Core Features & Use Cases - Stack Decision Guidance: Compares Biome 2.x versus ESLint 9 + typescript-eslint typed linting, including Biome's ~75% type-aware coverage gap and Oxlint as a fast challenger. - Biome 2.x Configuration: Covers biome.json, rule groups and severity, domains auto-enabled by dependencies, safe versus unsafe fixes, and CI gating with biome ci. - ESLint Typed Linting: Covers eslint.config.mjs flat config, recommendedTypeChecked/strictTypeChecked presets, and projectService for type-aware rules. - Use Case: Starting a new TypeScript project, you get a ready-to-copy biome.json with formatter, linter, and import organization configured, plus package.json scripts and a CI step. ## Quick Start Ask the agent to set up Biome 2.x linting and formatting for a new TypeScript project, or to configure ESLint 9 flat config with typescript-eslint typed linting for an existing codebase.

Frequently Asked Questions about ts-lint-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Should I use Biome or ESLint for a TypeScript project?▼

New projects should default to Biome 2.x for a single fast binary that formats, lints, and organizes imports with near-zero config. Established or type-heavy codebases should use ESLint 9 with typescript-eslint typed linting for full no-unsafe-* rules and cross-file narrowing.

How do I enable typed linting with typescript-eslint?▼

Swap the presets to their TypeChecked variants such as recommendedTypeChecked or strictTypeChecked, then set parserOptions.projectService to true in eslint.config.mjs. This runs TypeScript's type checker so rules gain cross-file type awareness.

Can Biome replace Prettier and ESLint together?▼

Biome replaces Prettier entirely since it bundles a formatter, and it covers roughly 75% of typed-linting needs without invoking tsc. It still lacks rules like import/no-cycle, full no-unsafe-*, and plugin ecosystems such as testing-library.

Can I run Biome and Prettier on the same files?▼

No, never run Biome and Prettier on the same files because their formatters conflict. Pick one formatter per project: Biome on the Biome stack, or Prettier paired with ESLint on the ESLint stack.

Why is typed linting slow in ESLint?▼

Typed linting runs a TypeScript build pass before ESLint lints, which is inherently slower than syntactic rules. IDE plugins cache results to stay fast, and teams typically run the full typed pass pre-push or in CI.

Does linting replace TypeScript type checking?▼

No, neither Biome nor ESLint replaces tsc --noEmit. Linters complement the type checker, so keep tsc --noEmit in CI for real type safety alongside whichever lint stack you choose.