ultracite

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

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill ultracite-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultracite
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.claude/skills/ultracite
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill ultracite-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up and maintaining consistent linting and formatting across JavaScript/TypeScript projects requires juggling multiple tools, configs, and presets. This Skill guides you through initializing Ultracite, running checks and fixes, following its code standards, and troubleshooting configuration issues. ## Core Features & Use Cases - Project Initialization: Run ultracite init interactively or non-interactively with flags for package manager, linter backend (Biome, ESLint, or Oxlint), editors, agents, frameworks, and git hook integrations. - Lint & Format Operations: Execute ultracite check for read-only analysis, ultracite fix for auto-fixes, and ultracite doctor to diagnose setup problems like conflicting legacy configs. - Code Standards Guidance: Apply Ultracite's rules for type safety, modern JS/TS patterns, async correctness, React accessibility, security, performance, and testing when writing or reviewing code. - Use Case: You join a Next.js project using Ultracite with Biome. Use this Skill to verify the config extends the right presets, run a fix pass on changed files, and ensure your new components follow the accessibility and hooks rules. ## Quick Start Ask the assistant to check whether this project uses Ultracite and run a lint check with auto-fix on the current source files.

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 new project?

Run `bunx ultracite init` for interactive setup, or pass flags like `--pm bun --linter biome --frameworks react next --quiet` for non-interactive CI use. It creates a config extending Ultracite presets and can install editor settings, agent files, and git hooks.

Biome vs ESLint vs Oxlint backend in Ultracite?

Ultracite supports three linter backends: Biome (recommended, single tool for lint and format), ESLint with Prettier and Stylelint, and Oxlint with Oxfmt. Choose with the `--linter` flag during init; each has its own preset set under `ultracite/<linter>/<preset>`.

How do I run Ultracite lint checks and auto-fixes?

Run `bunx ultracite check` for read-only analysis and `bunx ultracite fix` to auto-fix issues. Both accept optional file paths, and unknown options pass through to the underlying linter, such as `--max-warnings 0`.

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.

Does Ultracite support type-aware linting?

Yes, pass the `--type-aware` flag during init. With Biome it extends the `type-aware` preset; with Oxlint it installs `oxlint-tsgolint` for type-aware rule support.