Ultracite

Ultracite is a zero-config preset for ESLint, Biome, and Oxlint that helps teams and AI write consistent, type-safe code. It generates editor settings, agent instructions, and hooks so shared code standards stay aligned across human and AI workflows.

AI 코드 어시스턴트 AI 에이전트 개발 AI 개발 도구

웹사이트 방문

Overview

Ultracite is a zero-config preset for ESLint, Biome, and Oxlint that helps teams and AI produce consistent, type-safe code. It is positioned as a production-grade setup that generates linting, formatter, editor, and agent configuration from one install flow.

Instead of requiring teams to hand-maintain separate rules for editors and AI tools, Ultracite creates repo-specific files such as workspace settings, agent instructions, and hooks. The site emphasizes keeping code style, linting, and TypeScript defaults aligned across contributors while still allowing framework-specific rules and optional customization.

Key features

Custom install command generation

Generate a stack-specific init command after choosing a linter, frameworks, editors, agents, and optional hooks. The install page shows the command changing based on the selected setup.

Multiple linting stacks

Choose between Biome, ESLint + Prettier + Stylelint, or Oxlint + Oxfmt when generating your configuration. The site presents Ultracite as a preset that adapts to the linting toolchain you already use.

Framework-specific rule presets

Add framework-specific rules for React, Next.js, Solid, Vue, Svelte, Qwik, Angular, Remix, TanStack, Astro, NestJS, Jest, and Vitest/Bun. The homepage also shows framework-aware presets in its configuration examples.

Editor configuration files

Generate editor settings that enable format-on-save, auto-fixes, and TypeScript defaults. The VS Code page shows committed workspace settings for consistent behavior across contributors.

Agent instructions and hooks

Create rules files and hooks for AI agents so terminal or chat-based edits follow the same standards as human-written code. The source pages mention support for AGENTS.md, CLAUDE.md, and other agent-specific files.

Workflow commands and MCP support

Use the integrated `fix`, `check`, and `doctor` commands referenced in the Claude Code rules output to inspect or repair code and diagnose setup issues. The source also describes MCP support for linting and formatting without running Ultracite locally.

Common use cases

Bootstrapping a new codebase
Use Ultracite when you want a new repository to start with shared linting and formatting rules without manually wiring every config file. The init flow generates the relevant preset based on your stack choices.
Standardizing team editors
Use the editor configuration output when a team needs format-on-save and auto-fixes to behave the same way in Visual Studio Code across multiple contributors. The page shows committed workspace settings designed for shared projects.
Aligning AI coding assistants
Use agent files and hooks when AI tools are part of the workflow and you want those edits to follow the same standards as the rest of the repo. The site shows generated instructions for Claude Code and support for many other agents.
Applying stack-aware rules
Use framework-specific presets when a project combines a JavaScript or TypeScript framework with linting rules tailored to that stack. The homepage examples include React, Next.js, Vitest, and other common frameworks.
Checking and maintaining code quality
Use the generated `fix`, `check`, and `doctor` commands when you need to verify formatting, inspect rule violations, or diagnose setup issues from the terminal. The Claude Code instructions surface those commands directly in the generated rules file.

Pros and Cons

Pros

Supports multiple linting stacks, including Biome, ESLint + Prettier + Stylelint, and Oxlint + Oxfmt.
Generates editor settings and agent files so teams can keep human and AI workflows aligned in the same repository.
Includes framework-specific presets for common JavaScript and TypeScript stacks such as React and Next.js.
Offers install-time configuration choices for editors, agents, and hooks instead of requiring a manual setup path.
Describes commands for checking, fixing, and diagnosing code, which supports day-to-day maintenance.

Cons

The provided source does not include pricing details, so cost and plan structure are unclear from these pages alone.
Feature coverage outside the homepage and selected integration pages is partial in the provided evidence, so some integrations and workflows need documentation review before adoption.

FAQ

How do you set up Ultracite for a project?

Ultracite is configured through its init flow, which generates the linting, editor, and agent files that match your selected stack. The homepage and install page show setup paths for Biome, ESLint + Prettier + Stylelint, or Oxlint + Oxfmt, plus editor and agent files such as `.vscode/settings.json`, `AGENTS.md`, and `CLAUDE.md`.

Which editors and agents does Ultracite support?

The source pages show support for Visual Studio Code and Zed on the editor side, and agent files or hooks for tools such as Claude Code, Cursor, Windsurf, CodeBuddy, GitHub Copilot, Aider, Amazon Q CLI, Gemini, and Replit. The homepage also says Ultracite supports 40+ agents.

Can teams commit Ultracite settings to the repo?

Ultracite is designed to generate shared workspace settings and rules files so contributors and AI tools follow the same formatting and linting standards. The VS Code page specifically describes committed workspace settings that keep behavior consistent across contributors.

Does Ultracite work with agent hooks?

Yes. The Claude Code page shows Ultracite writing instructions to `.claude/CLAUDE.md` and a companion hook config at `.claude/settings.json`, and the homepage says it can generate agent hooks for supported tools.

Is Ultracite a hosted SaaS or an installable preset?

The site presents Ultracite as a preset for ESLint, Biome, and Oxlint rather than a hosted service, and it emphasizes installing it into your codebase with `npx ultracite@latest init` or a custom install command. Pricing details are not shown in the provided source text.