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.
Ultracite uses these Antigravity settings, rules, and hooks files to keep editor behavior and AI output aligned with your repo standards.
This workspace settings file keeps Antigravity 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" }}An AI-powered development platform built on VS Code for building and deploying applications faster.
Antigravity can stay on the same committed `.vscode/settings.json` contract as the rest of a mixed-editor team.
Ultracite keeps format-on-save and auto-fixes predictable while teams experiment with Antigravity's AI-driven workflows.
The setup is intentionally lightweight, which makes Antigravity a good fit for teams that want consistency without extra editor-specific files.
Keep Ultracite present in the day-to-day Antigravity workflow with a few editor-specific habits, not just a one-time setup.
Generate .vscode/settings.json so Antigravity uses the same formatter and code actions as the rest of the repository.
Commit the workspace config to keep Antigravity pilots aligned with teammates who still use Visual Studio Code or Cursor.
Use the shared editor settings as the baseline, then layer Antigravity-specific workflow experiments on top without changing repo-level standards.
Editor-specific answers for teams rolling out Ultracite in Antigravity.
These nearby setups make it easier to compare how Ultracite handles shared settings, AI rules, and editor-specific workflow details.
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.
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.
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.
And used by thousands of open source projects.
Here's what some of the most innovative and forward-thinking developers in the React ecosystem have to say about Ultracite.