Configure Biome as formatter, linter, and import organizer for JavaScript and TypeScript projects.
npx skills add https://github.com/avbel/ai-skills --skill biome-js-avbel
Please help me install this Agent Skill. Skill: biome-js Source: https://github.com/avbel/ai-skills/tree/main/skills/biome-js Command: npx skills add https://github.com/avbel/ai-skills --skill biome-js-avbel
tsc --noEmit. - Bootstrap Script: Generates package.json scripts, biome.jsonc, and VS Code workspace settings via scripts/biome-js-bootstrap.sh strict. - Use Case: When migrating a TypeScript project from XO and Prettier to Biome, use this Skill to produce a strict biome.jsonc, wire up save-time fixes in VS Code, and keep CI running biome ci plus tsc --noEmit. ## Quick Start Ask the agent to set up a strict Biome configuration for your TypeScript project, replacing ESLint and Prettier, and run the bootstrap script to generate the config files.High-intent search queries and answers about installing and using this skill.
Install @biomejs/biome locally, run biome migrate eslint --write as a starting point, then tighten the config manually with strict linter rules and formatter options. Add format, lint, lint:fix, and ci scripts to package.json and disable ESLint/Prettier save-time formatters in VS Code.
Map XO rules to Biome equivalents: eqeqeq becomes suspicious.noDoubleEquals, prefer-const becomes style.useConst, and consistent-type-imports becomes style.useImportType. Import sorting moves to assist.source.organizeImports instead of linter rules.
No, Biome does not replace type-aware rules like no-floating-promises or no-misused-promises. Keep tsc --noEmit in CI for semantic checks, and retain a small ESLint layer only if the project truly needs those rules.
Yes, install the official biomejs.biome extension and set editor.defaultFormatter to biomejs.biome with formatOnSave enabled. Add source.fixAll.biome and source.organizeImports.biome code actions on save for automatic fixes and import sorting.
Biome unsafe fixes may change program behavior, so they should not run automatically in save hooks or CI. Use biome check --write for safe fixes only, and apply --unsafe locally after reviewing the diff.
racurrySelect Biome, ESLint, or Prettier toolchains for JavaScript projects.
fusengineConfigure TypeScript linting and formatting with Biome 2.x or ESLint 9 flat config.
chancetop-comCompare SKILL.md frontmatter name against the containing directory name.
matlabRecreate RoadRunner scenarios programmatically from OpenSCENARIO 1.x files.