ultracite

Configure and run zero-config linting and formatting for JavaScript and TypeScript projects.

3.3k|126|Updated Mar 18, 2022
One-click install
npx skills add https://github.com/haydenbleasel/ultracite --skill ultracite-haydenbleasel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ultracite
Source: https://github.com/haydenbleasel/ultracite/tree/main/skills/ultracite
Command: npx skills add https://github.com/haydenbleasel/ultracite --skill ultracite-haydenbleasel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Maintaining consistent code style and catching bugs across JavaScript/TypeScript projects requires configuring linters and formatters, which is tedious and error-prone. Ultracite provides a zero-config preset that works with Oxlint, Biome, or ESLint backends, so teams get consistent code standards without hand-tuning rule configurations. ## Core Features & Use Cases - Project Initialization: Run ultracite init to set up linting and formatting with your choice of package manager, linter backend, editor, AI agent, framework, and git hook integrations. - Lint and Format Commands: Use ultracite check to find issues, ultracite fix to auto-fix them, and ultracite doctor to diagnose setup problems like conflicting legacy configs. - Code Standards Guidance: When writing or reviewing code in an Ultracite project, follow its built-in standards covering type safety, async correctness, React accessibility, security, performance, and testing. - Use Case: You join a Next.js project that uses Ultracite with Biome. Before committing, run bunx ultracite fix to auto-format and lint your changes, then consult the code standards reference to ensure your React components meet accessibility requirements. ## Quick Start Ask the AI to initialize Ultracite in your project with your preferred linter and framework, or to run a lint check and fix any issues it finds.

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 JavaScript project?▼

Run `bunx ultracite init` (or npx/pnpx equivalent) to start interactive setup. For CI environments, pass flags like `--pm bun --linter biome --frameworks react --quiet` to configure non-interactively.

How do I run linting and formatting with Ultracite?▼

Use `bunx ultracite check` to find issues read-only and `bunx ultracite fix` to auto-fix them. Both accept optional file paths, and unknown options pass through to the underlying linter.

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

Oxlint with Oxfmt is the recommended default and is selected automatically when `--linter` is omitted. Biome offers a type-aware preset, while ESLint pairs with Prettier and Stylelint for teams needing the traditional ecosystem.

Does Ultracite work with frameworks like Next.js or Vue?▼

Yes, Ultracite provides presets for React, Next.js, Vue, Svelte, Solid, Qwik, Remix, Angular, Astro, NestJS, and more. Pass them via `--frameworks` during init or extend `ultracite/<linter>/<preset>` in your config file.

Why are Ultracite rules not applying in my project?▼

Run `bunx ultracite doctor` to diagnose the issue. Common causes are conflicting legacy `.eslintrc.*` or `.prettierrc.*` files, missing ultracite in devDependencies, or a config file that does not extend the correct presets.