IBM Bob works well with Ultracite when you pair shared Visual Studio Code workspace settings with `AGENTS.md` rules—matching the standard format while keeping editor behavior predictable.
Ultracite uses these IBM Bob settings, rules, and hooks files to keep editor behavior and AI output aligned with your repo standards.
This workspace settings file keeps IBM Bob aligned with Ultracite for format on save, auto-fixes, and TypeScript defaults.
{ "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" }}IBM's AI coding assistant for the IDE, built for agentic modes, literate coding, and enterprise workflows alongside familiar editor ergonomics.
IBM Bob reads `AGENTS.md`, the same rules file used by many AI coding tools. Ultracite writes your standards there so they work across agents while staying version-controlled.
Ultracite still targets the normal `.vscode/settings.json` surface, so format on save, the linter extension, and TypeScript defaults behave like other VS Code–compatible editors.
You can combine editor behavior (settings) with Bob's guidance file so AI output and human edits meet the same bar before review.
Keep Ultracite present in the day-to-day IBM Bob workflow with a few editor-specific habits, not just a one-time setup.
Run npx ultracite@latest init --editors bob to generate .vscode/settings.json and the linter extension defaults Bob-compatible editors expect.
Run with --agents bob (or init both) to append AGENTS.md so Bob picks up Ultracite standards from the shared rules file.
Optionally add extra files under .bob/rules/ for Bob-specific instructions that complement AGENTS.md.
Editor-specific answers for teams rolling out Ultracite in IBM Bob.
These nearby setups make it easier to compare how Ultracite handles shared settings, AI rules, and editor-specific workflow details.
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.
Trae works well with Ultracite when you keep the standard VS Code workspace settings in place and add a dedicated project rules file that teaches the AI how your repo expects code to look.
CodeBuddy works best with Ultracite when you combine committed workspace settings, a branded project memory file, and optional PostToolUse hooks that clean up AI edits after they land.
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.