agentleFS
ItalyPaleAleItalyPaleAle/skills/biome-lint-format/SKILL.md

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.

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
  1. Distinctive:

    Keep ESLint/Prettier or migrate fully

    line 15
  2. Very specific:

    Add project scripts for lint/format/check/ci flows.

    line 21
  3. Distinctive:

    Add optional pre-commit checks with Husky + lint-staged if requested.

    line 25
  4. Distinctive:

    If migrating from ESLint + Prettier, remove old config carefully and run a first auto-fix pass.

    line 27
  5. Very specific:

    Use for installation, baseline biome.json, scripts, VS Code setup, pre-commit setup, and command examples.

    line 36
  6. Distinctive:

    Use only when migrating from ESLint + Prettier or running a hybrid temporary setup.

    line 39
  7. Distinctive:

    Use for config detection issues, editor conflicts, schema/version mismatches, and performance tuning.

    line 42
  8. Distinctive:

    Use only when the user asks for concrete rule customizations.

    line 45
  9. Very specific:

    Keep SKILL.md short and procedural.

    line 49
  10. Very specific:

    Use biome check as the default all-in-one command.

    line 50
  11. Very specific:

    Do not claim Biome replaces tsc type checking.

    line 51

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Biome Lint Format

Set up Biome with a consistent workflow and minimal friction.

Workflow

  1. Confirm project context:
  • Package manager
  • JavaScript/TypeScript scope
  • Keep ESLint/Prettier or migrate fully
  • Need Tailwind CSS directive support
  • Need pre-commit hooks
  1. Install Biome and create baseline configuration.
  2. Add project scripts for lint/format/check/ci flows.
  3. Configure editor integration (VS Code) if requested.
  4. Add optional pre-commit checks with Husky + lint-staged if requested.
  5. If migrating from ESLint + Prettier, remove old config carefully and run a first auto-fix pass.
  6. Validate setup by running check commands and confirming CI command behavior.

Reference Map

Load only the reference needed for the current request:

  • references/setup.md Use for installation, baseline biome.json, scripts, VS Code setup, pre-commit setup, and command examples.
  • references/migration.md Use only when migrating from ESLint + Prettier or running a hybrid temporary setup.
  • references/troubleshooting.md Use for config detection issues, editor conflicts, schema/version mismatches, and performance tuning.
  • references/rule-customization.md Use only when the user asks for concrete rule customizations.

Guardrails

  • Keep SKILL.md short and procedural; store details in references.
  • Use biome check as the default all-in-one command.
  • Do not claim Biome replaces tsc type checking.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.