Browse / Security Testing / BiomeJS Configuration

BiomeJS Configuration

Configures BiomeJS for code formatting and linting using best practices for monorepos, UI projects, and Git hooks.

SkillSecurity TestingSkill AuthoringProject ManagementGithubConfig

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Quick reference for key linter rules and their rationale
  • Monorepo and shared configuration patterns
  • UI-specific configurations for Tailwind CSS projects
  • Specific overrides for test files, generated code, and import restrictions
  • Git hook integration using lint-staged and Husky

Use cases

  • Fine-tuning BiomeJS rules with specific overrides for different file types.
  • Setting up BiomeJS from scratch in a new project or monorepo.
  • Configuring pre-commit hooks to automatically format and lint code.

FAQ

Does this skill handle all file formatting?

This skill focuses on configuring Biome, which excels at formatting and linting JavaScript, TypeScript, JSX, JSON, and CSS. For other file types like Markdown (.md) or YAML (.yml), it recommends using Prettier alongside Biome.

How does this skill improve my workflow?

It saves significant time by providing proven configurations for complex scenarios like monorepos and UI projects. By integrating with Git hooks, it automates code quality checks, ensuring consistency and preventing errors before they are committed.

What key capabilities does it provide?

It offers patterns for monorepo inheritance, UI-specific setups for sorting Tailwind CSS classes, rules for test files, import restrictions, and a pre-configured `lint-staged` setup for automated pre-commit checks.

What does the BiomeJS Configuration skill do?

This skill provides expert guidance and ready-to-use code snippets to configure BiomeJS for consistent code formatting and linting, based on best practices for modern web development projects.

When should I use this skill?

Use this skill when you need to set up a `biome.jsonc` file, configure a monorepo, create specific overrides for test or generated files, or integrate Biome with Git hooks using lint-staged and Husky.