BiomeJS is a tool that checks your code for mistakes and enforces a consistent style. This guide helps you set up its configuration for your project. You will learn how to extend shared configs, handle monorepo settings, and add custom overrides.
Using the right BiomeJS configuration keeps your code clean and prevents common bugs. The patterns shown here follow the Sablier project style. They work for libraries, frontend apps, and even GraphQL projects.
Global
mkdir -p ~/.claude/skills/biome-jsProject
mkdir -p .claude/skills/biome-jsSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective