How does Kiro's steering file differ from the normal editor settings?

The settings file handles editor behavior like format on save, while the steering file gives Kiro higher-level repo guidance before it starts implementing a task.

Should I still commit the Visual Studio Code settings for Kiro?

Yes. Kiro still benefits from the shared `.vscode/settings.json`, so human edits and AI-assisted edits follow the same formatter and code action defaults.

Who is the Kiro setup best suited for?

Teams using Kiro for structured task planning, specs, or implementation outlines usually get the most value because the steering file reinforces repo-wide standards during that planning step.

Ultracite for Kiro

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.

Setup files for Kiro

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

Workspace settings

This workspace settings file keeps Kiro 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 Kiro teams choose Ultracite

AWS's spec-driven AI development environment for building production-ready applications.

Steering files match Kiro's planning model

Kiro can read an Ultracite steering file, which makes it a strong fit for teams that rely on spec-first development.

Spec-driven guidance without losing standard editor defaults

Ultracite still anchors the day-to-day editor behavior in a normal VS Code settings file, so workspace expectations stay familiar.

Moves quality earlier in the workflow

The steering file helps Kiro generate code that already reflects your repo conventions instead of relying only on after-the-fact fixes.

Workflow tips for Kiro

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

Use .vscode/settings.json to keep Kiro's editor behavior aligned with the rest of the repository.

Add .kiro/steering/ultracite.md so Kiro sees Ultracite's code standards while turning specs into implementation work.

Treat the steering file as durable repo guidance and update it alongside broader changes to your coding standards.

Kiro FAQ

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

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

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.

TraeByteDance's AI IDE

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.

CodeBuddyTencent Cloud's AI code editor

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.