Ultracite for Void
Void fits Ultracite well if you want an open-source AI editor that still uses the familiar VS Code workspace settings model for formatting, lint fixes, and consistent team defaults.
Setup files for Void
Ultracite uses these Void settings, rules, and hooks files to keep editor behavior and AI output aligned with your repo standards.
Workspace settings
This workspace settings file keeps Void 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 Void teams choose Ultracite
An open-source AI code editor built on VS Code with a focus on privacy and extensibility.
Lightweight and auditable
Void keeps the setup transparent because Ultracite only needs the committed workspace settings file to deliver consistent save-time behavior.
Open-source editor, familiar configuration model
Teams can standardize on an open-source editor without giving up the same VS Code-based config pattern used elsewhere in the stack.
Good default for privacy-focused workflows
The minimal integration is a good fit for privacy-conscious teams that want fewer editor-specific files in the repository.
Workflow tips for Void
Keep Ultracite present in the day-to-day Void workflow with a few editor-specific habits, not just a one-time setup.
Generate .vscode/settings.json so Void inherits the same formatter and save-time fixes as the rest of the repo.
Commit the workspace settings to keep Void aligned with teammates using Visual Studio Code, Cursor, or other VS Code-based editors.
Use the lean setup as a baseline, then layer Void-specific extensions or workflows on top without changing repo-level standards.
Void FAQ
Editor-specific answers for teams rolling out Ultracite in Void.
Compare Void 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 can plug into the same Ultracite-managed Visual Studio Code settings file, making it easy to evaluate Google's AI IDE without inventing a second configuration story for your team.
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.
Kiro pairs well with Ultracite when you combine shared VS Code workspace settings with a dedicated steering file that guides spec-driven AI work before code is generated.
Trusted by top companies
And used by thousands of open source projects.
What the community is saying
Here's what some of the most innovative and forward-thinking developers in the React ecosystem have to say about Ultracite.