ultracite

Configures and runs zero-config linting and formatting for JavaScript and TypeScript projects.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/CarlosPavajeau/light --skill ultracite-carlospavajeau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultracite
Source: https://github.com/CarlosPavajeau/light/tree/main/.claude/skills/ultracite
Command: npx skills add https://github.com/CarlosPavajeau/light --skill ultracite-carlospavajeau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 setup, execution, and troubleshooting of Ultracite, a zero-config preset supporting Biome, ESLint, and Oxlint backends. ## Core Features & Use Cases - Project Initialization: Run interactive or non-interactive setup with flags for package manager, linter backend, editors, agents, frameworks, and git hook integrations. - Lint and Format Operations: Execute check, fix, and doctor commands to detect issues, auto-fix violations, and diagnose configuration problems. - Code Standards Enforcement: Apply type safety, accessibility, security, and performance rules when writing or reviewing JS/TS code. - Use Case: A developer migrating a React project from legacy ESLint/Prettier configs can initialize Ultracite with the Biome backend, remove conflicting config files, and run auto-fix across the codebase in one workflow. ## Quick Start Initialize Ultracite in my project with the Biome linter and then run a check to find and fix any linting issues.

Frequently Asked Questions about ultracite

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

FAQPage Schema
How do I set up Ultracite in a TypeScript project?

Run bunx ultracite init to start interactive setup, or pass flags like --pm bun, --linter biome, and --frameworks react for non-interactive use. The command creates a config file extending Ultracite presets and installs required dependencies.

What is the difference between Ultracite check and fix commands?

The check command runs read-only analysis to report linting and formatting issues without modifying files. The fix command automatically corrects violations where possible. Both accept optional file paths to limit scope.

Biome vs ESLint vs Oxlint: which linter backend should I choose?

Biome is the recommended backend for Ultracite due to its speed and unified tooling. ESLint with Prettier suits teams with existing ESLint ecosystems, while Oxlint with Oxfmt offers a fast Rust-based alternative with optional type-aware linting.

Why are Ultracite rules not applying in my project?

Rules fail to apply when the config file does not extend the correct Ultracite presets for your framework, or when legacy .eslintrc and .prettierrc files conflict. Run bunx ultracite doctor to diagnose installation, config validity, and conflicting tools.

Can Ultracite run in CI pipelines without prompts?

Yes, pass the --quiet flag or set CI=true to suppress interactive prompts during init. Combine with explicit flags for package manager, linter, editors, and frameworks to make setup fully deterministic in automation.