Why does the CodeBuddy setup use settings, CODEBUDDY.md, and hooks?

The workspace settings control format on save and code actions, `CODEBUDDY.md` gives CodeBuddy repo-level instructions for how generated code should look, and `.codebuddy/settings.json` can run Ultracite automatically after AI edits.

Can CodeBuddy share the same committed workspace settings as other editors?

Yes. Ultracite keeps the shared `.vscode/settings.json` file as the baseline so CodeBuddy can stay aligned with teammates using other VS Code-style editors.

What do CodeBuddy hooks add on top of CODEBUDDY.md?

The memory file shapes how CodeBuddy writes code up front, while the hook config lets Ultracite run after `Write` and `Edit` actions so formatting and safe fixes happen automatically.

Ultracite for CodeBuddy

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.

Setup files for CodeBuddy

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

Workspace settings

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

.vscode/settings.json

JSON config

{  "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 CodeBuddy teams choose Ultracite

Tencent Cloud CodeBuddy is a next-generation AI code editor powered by the Tencent Yuanbao Code large model.

Combines memory, settings, and hooks

CodeBuddy can pair shared VS Code-style workspace settings with both a branded memory file and project-level hooks, so editor behavior and AI cleanup stay aligned in one repo contract.

Covers both pre- and post-edit quality

Using `CODEBUDDY.md` makes repo guidance explicit before CodeBuddy generates code, while hooks in `.codebuddy/settings.json` can clean up what is still auto-fixable after edits land.

Fits existing VS Code-style collaboration

The setup stays familiar for teams already standardizing on `.vscode/settings.json`, which keeps onboarding simple even in an AI-heavy editor.

Workflow tips for CodeBuddy

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

Generate .vscode/settings.json so CodeBuddy follows the same formatter, code actions, and TypeScript defaults as the rest of the repo.

Add CODEBUDDY.md to give CodeBuddy a committed memory file that reflects Ultracite's coding standards.

Enable .codebuddy/settings.json when you want Ultracite to run after CodeBuddy Write and Edit actions and clean up AI-generated changes automatically.

CodeBuddy FAQ

Editor-specific answers for teams rolling out Ultracite in CodeBuddy.

Compare CodeBuddy 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.

CursorThe AI-first code editor

Cursor works best with Ultracite when you combine committed workspace settings, a dedicated Cursor rules file, and optional post-edit hooks that run after AI-driven changes land in your repo.

WindsurfThe agentic IDE by Codeium

Use Ultracite with Windsurf to pair standard VS Code workspace settings with Windsurf-specific rules and optional hooks that tidy AI-generated edits after every write.

IBM BobIBM's AI coding assistant

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.