biome-js
Provides specific BiomeJS configuration patterns for JavaScript/TypeScript projects, with examples for extending shared configs, monorepo setups, and Git hooks. Focuses on practical patterns from real projects rather than generic documentation.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install paulrberg-dot-claude-biome-js
Repository
Skill path: skills/biome-js
Provides specific BiomeJS configuration patterns for JavaScript/TypeScript projects, with examples for extending shared configs, monorepo setups, and Git hooks. Focuses on practical patterns from real projects rather than generic documentation.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: JavaScript/TypeScript developers setting up BiomeJS for new projects or migrating from ESLint/Prettier, especially those working in monorepos or using shared configuration patterns..
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: PaulRBerg.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install biome-js into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/PaulRBerg/dot-claude before adding biome-js to shared team environments
- Use biome-js for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: biome-js
description: This skill should be used when the user asks to "configure Biome", "extend biome config", "set up BiomeJS", "add biome overrides", "biome lint-staged", "fix biome errors", or mentions biome.jsonc, Biome linting, or Biome formatting configuration.
---
# BiomeJS Skill
Quick guidance for BiomeJS configuration based on Sablier project patterns.
## Core Concepts
### Extending Shared Configs
Extend shared configs via npm package exports. The consuming project must always provide its own `files.includes`:
```jsonc
{
"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
"extends": ["@sablier/devkit/biome"],
"files": {
"includes": ["**/*.{js,json,jsonc,ts}", "!node_modules/**/*"]
}
}
```
For UI projects, extend both base and ui configs:
```jsonc
{
"extends": ["@sablier/devkit/biome/base", "@sablier/devkit/biome/ui"],
"files": {
"includes": ["**/*.{css,js,jsx,json,jsonc,ts,tsx}"]
}
}
```
### Monorepo Inheritance
In monorepos, workspace configs inherit from root using `"//"`:
```jsonc
// packages/my-package/biome.jsonc
{
"extends": ["//"],
"overrides": [
// package-specific overrides
]
}
```
### File Includes Pattern
Always specify `files.includes` explicitly. Common patterns:
| Project Type | Pattern |
| ------------ | --------------------------------------------- |
| Library | `**/*.{js,json,jsonc,ts}` |
| UI/Frontend | `**/*.{css,js,jsx,json,jsonc,ts,tsx}` |
| With GraphQL | `**/*.{css,graphql,js,jsx,json,jsonc,ts,tsx}` |
Exclusions: `!node_modules/**/*`, `!**/generated`, `!dist`
## Common Overrides
### Test Files
Relax strict rules in test files:
```jsonc
{
"overrides": [
{
"includes": ["**/tests/**/*.ts", "**/*.test.ts"],
"linter": {
"rules": {
"style": {
"noNonNullAssertion": "off"
},
"suspicious": {
"noExplicitAny": "off"
}
}
}
}
]
}
```
### Generated/ABI Files
Disable sorting and compact formatting for generated code:
```jsonc
{
"overrides": [
{
"includes": ["**/abi/**/*.ts", "**/generated/**/*.ts"],
"assist": {
"actions": {
"source": {
"useSortedKeys": "off"
}
}
},
"javascript": {
"formatter": {
"expand": "never"
}
}
}
]
}
```
### Import Restrictions
Enforce barrel imports for specific modules:
```jsonc
{
"overrides": [
{
"includes": ["src/**/*.{ts,tsx}"],
"linter": {
"rules": {
"correctness": {
"noRestrictedImports": {
"level": "error",
"options": {
"paths": {
"@/core": "Import from @/core (barrel) instead of subpaths"
}
}
}
}
}
}
}
]
}
```
## Key Rules Reference
| Rule | Default | Rationale |
| ------------------------- | -------------------- | --------------------------------------- |
| `noFloatingPromises` | error | Floating promises cause bugs |
| `noUnusedImports` | off | Allow during dev, enforce in pre-commit |
| `noUnusedVariables` | error | Keep code clean |
| `useImportType` | warn (separatedType) | Explicit type imports |
| `useSortedKeys` | on | Consistent object ordering |
| `useSortedClasses` | warn (UI) | Tailwind class sorting |
| `useFilenamingConvention` | kebab/camel/Pascal | Flexible naming |
| `noVoid` | off | Useful for useEffect callbacks |
| `useTemplate` | off | Allow string concatenation |
## Git Hooks Integration
### Lint-Staged Configuration
Standard pattern for pre-commit hooks:
```javascript
// .lintstagedrc.js
module.exports = {
"*.{json,jsonc,ts,tsx}": "bun biome check --write",
"*.{md,yml,yaml}": "bun prettier --cache --write",
"*.{ts,tsx}": "bun biome lint --write --only correctness/noUnusedImports",
};
```
The separate `noUnusedImports` pass enforces import cleanup only at commit time, not during development.
### Husky Setup
```bash
# .husky/pre-commit
bun lint-staged
```
## Just Recipes
Standard Biome recipes from devkit:
| Recipe | Alias | Command |
| ------------- | ----- | -------------------------------------- |
| `biome-check` | `bc` | `biome check .` |
| `biome-lint` | `bl` | `biome lint .` |
| `biome-write` | `bw` | `biome check --write` + unused imports |
| `full-check` | `fc` | biome + prettier + tsc |
| `full-write` | `fw` | biome + prettier fixes |
Usage: `just bw` to fix all issues, `just bc` to check without fixing.
## UI-Specific Configuration
For frontend projects with Tailwind CSS:
```jsonc
{
"css": {
"parser": {
"cssModules": true,
"tailwindDirectives": true
}
},
"assist": {
"actions": {
"source": {
"useSortedAttributes": "on"
}
}
},
"linter": {
"rules": {
"nursery": {
"useSortedClasses": {
"fix": "safe",
"level": "warn",
"options": {
"attributes": ["classList"],
"functions": ["clsx", "cva", "cn", "tv", "tw"]
}
}
}
}
}
}
```
## Troubleshooting
### Common Issues
**"No files matched"**: Check `files.includes` patterns match your file structure.
**Conflicting rules**: Overrides are applied in order; later overrides take precedence.
**Schema errors**: Use local schema reference for IDE support:
```jsonc
"$schema": "./node_modules/@biomejs/biome/configuration_schema.json"
```
### Biome vs Prettier
Biome handles JS/TS/JSON/CSS formatting. Use Prettier for:
- Markdown (`.md`, `.mdx`)
- YAML (`.yml`, `.yaml`)
## Additional Resources
### Examples
Working examples in `examples/`:
- **`base-config.jsonc`** - Minimal library configuration
- **`ui-config.jsonc`** - Frontend project with Tailwind
- **`lint-staged.js`** - Pre-commit hook configuration
### Full Documentation
For advanced features, migrations, or complete rule reference, consult the official Biome documentation via Context7 MCP:
```
Use context7 to fetch Biome documentation for [specific topic]
```
The official docs at biomejs.dev should be consulted as a last resort for features not covered here.