Ultracite for Visual Studio Code

Use Ultracite to generate a clean Visual Studio Code settings file with format on save, auto-fixes, and TypeScript defaults that stay consistent across every contributor's workspace.

Setup files for Visual Studio Code

Ultracite uses these Visual Studio Code settings, rules, and hooks files to keep editor behavior and AI output aligned with your repo standards.

Workspace settings

This workspace settings file keeps Visual Studio Code aligned with Ultracite for format on save, auto-fixes, and TypeScript defaults.

.vscode/settings.json

{  "editor.defaultFormatter": "esbenp.prettier-vscode",  "editor.formatOnPaste": true,  "editor.formatOnSave": true,  "emmet.showExpandedAbbreviation": "never",  "js/ts.tsdk.path": "node_modules/typescript/lib",  "js/ts.tsdk.promptToUseWorkspaceVersion": true,  "[css]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[graphql]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[html]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[javascript]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[javascriptreact]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[json]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[jsonc]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[markdown]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[mdx]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[svelte]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[typescript]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[typescriptreact]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[vue]": {    "editor.defaultFormatter": "biomejs.biome"  },  "[yaml]": {    "editor.defaultFormatter": "biomejs.biome"  },  "editor.codeActionsOnSave": {    "source.fixAll.biome": "explicit",    "source.organizeImports.biome": "explicit"  }}

Why Visual Studio Code teams choose Ultracite

Microsoft's popular code editor with extensive extension support and built-in Git integration.

  • Commit-friendly workspace defaults: Ultracite writes predictable workspace settings that every VS Code contributor can commit and share.
  • Works with the editor your team already uses: You keep the full Visual Studio Code extension ecosystem while still getting consistent format-on-save behavior.
  • Low-friction onboarding: The generated settings stay narrow and readable, so onboarding new contributors does not require a custom editor guide.

Workflow tips for Visual Studio Code

Keep Ultracite present in the day-to-day Visual Studio Code workflow with a few editor-specific habits, not just a one-time setup.

  1. Run npx ultracite@latest init --editors vscode to generate .vscode/settings.json for the repo.
  2. Commit the workspace settings so every contributor inherits the same formatter and save-time fixes.
  3. Install the matching linter extension once, then let Visual Studio Code keep the project aligned automatically.

Visual Studio Code FAQ

Editor-specific answers for teams rolling out Ultracite in Visual Studio Code.

Can I commit Ultracite's Visual Studio Code settings to the repo?

Does the Visual Studio Code setup work with different Ultracite linters?

Does Ultracite need extra rules or hooks for plain Visual Studio Code?

Compare Visual Studio Code with other Ultracite-supported editors

These nearby setups make it easier to compare how Ultracite handles shared settings, AI rules, and editor-specific workflow details.

  • Antigravity: Google's next-generation IDE. Antigravity can plug into the same Ultracite-managed Visual Studio Code settings file.
  • Void: Open-source AI editor that still uses the familiar VS Code workspace settings model for formatting, lint fixes, and consistent team defaults.
  • IBM Bob: Works well with Ultracite when you pair shared Visual Studio Code workspace settings with AGENTS.md rules.

Trusted by top companies

And used by thousands of open source projects.

Install in seconds. Run in milliseconds.

Install Ultracite and start shipping code faster in seconds.