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, following its code standards, and diagnosing configuration problems. ## Core Features & Use Cases - Project Setup: Initialize 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 issues. - Code Standards Reference: 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 repository using Ultracite with Biome and need to fix lint errors before committing. Run the fix command, then use doctor to resolve a conflicting legacy .eslintrc file left over from migration. ## Quick Start Ask the assistant to run an Ultracite check on your project and fix any linting or formatting issues it finds.
