How do I install the Biomejs skill?

Run npx skillmds@latest add aiko-atami/biomejs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Biomejs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Biomejs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Biomejs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Biomejs?

aiko-atami (@aiko-atami) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Biomejs by aiko-atami — Agent Skill

Name: Biomejs
Author: aiko-atami

Biomejs

Configure and operate BiomeJS in JavaScript/TypeScript projects, including installation, `biome.json` setup, formatter/linter/check workflows, VCS integration, and CI usage. Use when users ask to adopt Biome, tune rules/includes, set up monorepo/shared configs, or troubleshoot Biome command behavior.

aiko-atami Updated Sep 17, 2026

File contents

BiomeJS

Use this skill to implement and operate BiomeJS with predictable steps and minimal disruption. For ESLint/Prettier migration, use the dedicated eslint-prettier-migration skill.

Workflow

Identify intent:

Fresh setup
Config tuning
CI/VCS integration
Diagnostics troubleshooting

Apply the matching path:

Fresh setup: follow references/getting-started.md
Config and file-scoping: follow references/configuration-and-vcs.md
Advanced config templates: follow references/advanced-configuration-templates.md
CLI options/reporters: follow references/cli-basics.md
Monorepo and shared config strategy: follow references/monorepo-and-upgrades.md
Performance debugging: follow references/performance-tracing.md
Pre-commit hooks and CI recipes: follow references/automation-ci-and-hooks.md

Verify with a no-write pass before auto-fixing:

Run biome check .
Then run biome check --write only after confirming scope and intended changes

Operational Defaults

Use these defaults unless user asks otherwise:

Pin Biome version when installing (-E with package managers that support it).
Keep config in project root (biome.json or biome.jsonc).
Run biome check --write for unified format+lint+organize imports.
Run biome ci in CI pipelines.

References

Setup and baseline commands: references/getting-started.md
Configuration, includes, and VCS integration: references/configuration-and-vcs.md
Advanced configuration templates and migration-safe patterns: references/advanced-configuration-templates.md
Useful CLI commands and options: references/cli-basics.md
Monorepo setup and v1->v2 upgrade notes: references/monorepo-and-upgrades.md
Slowness investigation and tracing spans: references/performance-tracing.md
Git hooks and CI recipes: references/automation-ci-and-hooks.md

---name: biomejsdescription: Configure and operate BiomeJS in JavaScript/TypeScript projects, including installation, `biome.json` setup, formatter/linter/check workflows, VCS integration, and CI usage. Use when users ask to adopt Biome, tune rules/includes, set up monorepo/shared configs, or troubleshoot Biome command behavior.---# BiomeJSUse this skill to implement and operate BiomeJS with predictable steps and minimal disruption.For ESLint/Prettier migration, use the dedicated `eslint-prettier-migration` skill.## Workflow1. Identify intent:- Fresh setup- Config tuning- CI/VCS integration- Diagnostics troubleshooting2. Apply the matching path:- Fresh setup: follow `references/getting-started.md`- Config and file-scoping: follow `references/configuration-and-vcs.md`- Advanced config templates: follow `references/advanced-configuration-templates.md`- CLI options/reporters: follow `references/cli-basics.md`- Monorepo and shared config strategy: follow `references/monorepo-and-upgrades.md`- Performance debugging: follow `references/performance-tracing.md`- Pre-commit hooks and CI recipes: follow `references/automation-ci-and-hooks.md`3. Verify with a no-write pass before auto-fixing:- Run `biome check .`- Then run `biome check --write` only after confirming scope and intended changes## Operational DefaultsUse these defaults unless user asks otherwise:- Pin Biome version when installing (`-E` with package managers that support it).- Keep config in project root (`biome.json` or `biome.jsonc`).- Run `biome check --write` for unified format+lint+organize imports.- Run `biome ci` in CI pipelines.## References- Setup and baseline commands: `references/getting-started.md`- Configuration, includes, and VCS integration: `references/configuration-and-vcs.md`- Advanced configuration templates and migration-safe patterns: `references/advanced-configuration-templates.md`- Useful CLI commands and options: `references/cli-basics.md`- Monorepo setup and v1->v2 upgrade notes: `references/monorepo-and-upgrades.md`- Slowness investigation and tracing spans: `references/performance-tracing.md`- Git hooks and CI recipes: `references/automation-ci-and-hooks.md`

Frequently asked questions