Biome Lint Format
Set up Biome with a consistent workflow and minimal friction.
Workflow
- •Confirm project context:
- •Package manager
- •JavaScript/TypeScript scope
- •Keep ESLint/Prettier or migrate fully
- •Need Tailwind CSS directive support
- •Need pre-commit hooks
- •
Install Biome and create baseline configuration.
- •
Add project scripts for lint/format/check/ci flows.
- •
Configure editor integration (VS Code) if requested.
- •
Add optional pre-commit checks with Husky + lint-staged if requested.
- •
If migrating from ESLint + Prettier, remove old config carefully and run a first auto-fix pass.
- •
Validate setup by running check commands and confirming CI command behavior.
Reference Map
Load only the reference needed for the current request:
- •
references/setup.mdUse for installation, baselinebiome.json, scripts, VS Code setup, pre-commit setup, and command examples. - •
references/migration.mdUse only when migrating from ESLint + Prettier or running a hybrid temporary setup. - •
references/troubleshooting.mdUse for config detection issues, editor conflicts, schema/version mismatches, and performance tuning. - •
references/rule-customization.mdUse only when the user asks for concrete rule customizations.
Guardrails
- •Keep
SKILL.mdshort and procedural; store details in references. - •Use
biome checkas the default all-in-one command. - •Do not claim Biome replaces
tsctype checking.