agentleFS
Sign inStart free
raniellimontagnaraniellimontagna/agent-toolkit/skills/quality/biome-formatting/SKILL.md

biome-formatting

Skill3 starsChanged 33 days agoMITView on GitHub

Use Biome for formatting and linting in JavaScript, TypeScript, Astro, React, JSON, and CSS projects. Use when the repository has biome.json, Biome scripts, or tasks that require code style, import organization, lint fixes, or formatting validation.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the repository's Biome configuration as the source of truth for formatting, linting, import organization, and safe automatic fixes.

    line 8
  2. Very specific:

    Check package.json scripts and biome.json before choosing commands.

    line 13
  3. Very specific:

    Prefer the repository script, such as pnpm lint, pnpm lint:fix, or its documented verification command.

    line 14
  4. Distinctive:

    Use automatic writes only for formatting, import organization, and safe fixes.

    line 16
  5. Distinctive:

    Keep unrelated files out of the commit unless the formatter intentionally touched them.

    line 18
  6. Distinctive:

    Do not hand-format against Biome output or add ESLint/Prettier when Biome is already configured.

    line 24
  7. Very specific:

    Use JSON-aware edits for biome.json, package.json, and similar config.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Formatting

Use the repository's Biome configuration as the source of truth for formatting, linting, import organization, and safe automatic fixes.

Workflow

  1. Check package.json scripts and biome.json before choosing commands.
  2. Prefer the repository script, such as pnpm lint, pnpm lint:fix, or its documented verification command.
  3. Use automatic writes only for formatting, import organization, and safe fixes.
  4. Re-run validation after automatic fixes.
  5. Keep unrelated files out of the commit unless the formatter intentionally touched them.

Implementation Rules

  • Let Biome decide quote style, semicolons, trailing commas, and import ordering.
  • Do not hand-format against Biome output or add ESLint/Prettier when Biome is already configured.
  • Use JSON-aware edits for biome.json, package.json, and similar config.
  • Review semantic code changes separately from mechanical formatter changes.

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.

Check your setup, free