biome-lint-format
Skill1 starsChanged 9 months agoMITView on GitHub
Set up Biome for fast linting and formatting in JavaScript/TypeScript projects, including editor integration, package scripts, optional pre-commit hooks, and migration from ESLint + Prettier. Use when adding or standardizing lint/format tooling, replacing ESLint/Prettier, or troubleshooting Biome configuration and workflow issues.
In this repository5 other files it gives its agents.
- cut-releaseSkill
- go-package-skill-creatorSkill
- go-service-scaffolderSkill
- react-spa-viteSkill
- writing-qualitySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Keep ESLint/Prettier or migrate fully
- Very specific: line 21
Add project scripts for lint/format/check/ci flows.
- Distinctive: line 25
Add optional pre-commit checks with Husky + lint-staged if requested.
- Distinctive: line 27
If migrating from ESLint + Prettier, remove old config carefully and run a first auto-fix pass.
- Very specific: line 36
Use for installation, baseline biome.json, scripts, VS Code setup, pre-commit setup, and command examples.
- Distinctive: line 39
Use only when migrating from ESLint + Prettier or running a hybrid temporary setup.
- Distinctive: line 42
Use for config detection issues, editor conflicts, schema/version mismatches, and performance tuning.
- Distinctive: line 45
Use only when the user asks for concrete rule customizations.
- Very specific: line 49
Keep SKILL.md short and procedural.
- Very specific: line 50
Use biome check as the default all-in-one command.
- Very specific: line 51
Do not claim Biome replaces tsc type checking.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

