Oxfmt

Use this skill when work touches Oxfmt or Oxc formatting: install/config, day-to-day usage, Prettier/Biome migration, sorting extras, language support, editors, or CI --check gates.

Workflow

1. Inspect the local Oxfmt surface before changing code:
   • Package version for oxfmt (still 0.x / beta until 1.0).
   • Config: prefer oxfmt.config.ts / .mts with defineConfig; also accept .oxfmtrc.json(c) (one type per directory); Vite+ may use fmt in vite.config.ts instead.
   • Remaining Prettier/Biome setup, .prettierignore, scripts (format / format:check), editor default formatter.
2. For setup, how-to, style choices, sorting, monorepos, pairing with Oxlint, or troubleshooting, follow the full guide first: usage-guide.md.
3. Refresh current official docs when versions differ from the snapshot or the work touches language support, sorting, or migration. Start from source-map.md.
4. Route deeper detail to the focused references:
   • Install, CLI, config options, editorconfig: setup-cli-config.md.
   • Languages, sorting (including Tailwind sortTailwindcss), ignores, inline comments: languages-sorting-ignores.md.
   • Prettier/Biome migration, coexistence, CI, and .vscode settings (format / sort imports / remove unused): prettier-migration-ci.md.
5. Preserve the project's print width and quote/semi style unless migrating or the user asks to change them.
6. Verify with bunx oxfmt --check (CI) or bunx oxfmt (write) on the touched paths.