What problem does it solve? Maintaining consistent code style and catching errors across JavaScript/TypeScript projects requires configuring linters and formatters, which is tedious and error-prone. This Skill guides you through setting up Ultracite, running checks and fixes, and following its code standards. ## Core Features & Use Cases - Project Initialization: Set up Ultracite interactively or non-interactively with flags for package manager, linter backend (Biome, ESLint, or Oxlint), editors, agents, frameworks, and git hook integrations. - Linting and Formatting Commands: Run ultracite check for read-only analysis, ultracite fix for auto-fixes, and ultracite doctor to diagnose setup problems. - Code Standards Guidance: Apply Ultracite's rules for type safety, modern JavaScript, async correctness, React accessibility, security, performance, and testing when writing or reviewing code. - Use Case: You join a monorepo using Ultracite with Biome. Before committing, run bunx ultracite fix to auto-format your changes, then use the code standards reference to resolve remaining lint warnings about hook dependencies and accessibility. ## Quick Start Ask the AI to initialize Ultracite in your project with Biome as the linter and then run a check to find and fix linting issues.
