biome-developer

Codifies Biome development best practices and common gotchas for Rust-based AST work.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/kage1020/dotfiles --skill biome-developer-kage1020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biome-developer
Source: https://github.com/kage1020/dotfiles/tree/main/dot_claude/skills/biome-developer
Command: npx skills add https://github.com/kage1020/dotfiles --skill biome-developer-kage1020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide general development best practices, common gotchas, and Biome-specific patterns that apply across the codebase, helping developers avoid mistakes and write safer, more maintainable Biome code.

Core Features & Use Cases

  • Biome-wide best-practice reference covering AST, syntax nodes, string extraction, and embedded languages.
  • Practical guidance on common pitfalls, how to inspect and reason about Biome's AST without expensive builds, and how to apply borrow-checker and Clippy-style guidance.
  • Use cases include onboarding new contributors, reviewing code for Biome projects, and debugging complex parsing or transformation tasks.

Quick Start

Consult this guide when coding with Biome to follow patterns and avoid common mistakes.

Frequently Asked Questions about biome-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect Biome AST syntax nodes without triggering expensive builds?

You can inspect Biome AST syntax nodes without expensive builds by applying specific reasoning patterns and string extraction guidance to analyze syntax trees directly, avoiding full compilation during development and debugging.

What are the best practices for handling embedded languages in the Biome codebase?

Handling embedded languages in Biome requires following codified best practices for syntax node inspection and AST patterns, ensuring safe coding practices to avoid common parsing and transformation gotchas.

Do I need Rust familiarity to contribute to Biome development?

Yes, Rust familiarity is a prerequisite for Biome development, alongside understanding Biome architecture and access to guidance on AST patterns, string extraction, and borrow-checker guidelines.

How do I apply borrow-checker and Clippy-style guidelines when developing Biome?

Applying borrow-checker and Clippy-style guidelines in Biome involves using codified safe coding practices to navigate AST patterns and syntax nodes, ensuring maintainable and error-free Rust code.

What are common gotchas when analyzing Biome ASTs and transforming syntax?

Common gotchas when analyzing Biome ASTs include mishandling embedded languages and string extraction; avoiding these requires following concise, action-oriented best practices for syntax node transformation and inspection.