kiro-kit

<div align="center"> <img src="./assets/demo.gif" alt="Installing kiro-kit and running init inside Kiro" width="100%" /> <img src="./assets/banner.png" alt="kiro-kit" width="100%" /> [](https://github.com/ihatesea69/kiro-kit/actions/workflows/ci.yml) [](https://www.npmjs.com/package/kiro-kit) [](./LICENSE) [](https://www.npmjs.com/package/kiro-kit) [](https://nodejs.org) **[Documentation](https://ihatesea69.github.io/kiro-kit/)** </div> --- Setting up a [Kiro](https://kiro.dev) workspace means writing a lot of files by hand: agents, skills, slash commands, hooks, MCP config, spec templates. Kiro-Kit writes them for you. Pick the preset that matches your stack and it all lands in `.kiro/`. Presets don't depend on each other, everything ships inside the npm package so it works offline, and nothing you already wrote gets replaced without asking first. ## Quick Start ```bash npx kiro-kit init ``` Arrow keys to move, Enter to select, Enter again to confirm. That's it — the workspace is ready when the command exits. ```bash # or install globally npm install -g kiro-kit kiro-kit init ``` ## Why another Kiro tool Kiro-Kit is not the first tool to write files into `.kiro/`, and the ones that came before it are worth knowing about: | Tool | What it does | Where it stops | |---|---|---| | Starter templates with an `npx` scaffolder | Copy a skeleton of steering docs and hooks into a new project | The skeleton is thin — a handful of files per stack — and copying is one-way: rerun it on a live workspace and your edits are the cost | | Settings and bundle managers | Move existing skills, steering, and hooks between machines | They move content around. They don't give you any | | Config generators with inheritance | Compose agent configuration from layered config files | Configuration, not content: you still write every agent and skill yourself | | Community steering collections | Curated steering documents to copy by hand | No installer, no versioning, no way to tell what you already took | What Kiro-Kit does differently: - **It ships content, not scaffolding.** A preset is 19–26 agents, 21–37 skills, 66–74 commands, cross-platform hooks, workflows, and worked example specs — written, not stubbed. The whole catalog is in the [preset reference](https://ihatesea69.github.io/kiro-kit/docs/reference). - **Installing twice is safe.** Existing files are never silently replaced: conflicts prompt, every run backs up first, and writes are atomic, so an interrupt cannot leave half a workspace. `restore` rolls back. - **The content is tested, not just published.** Structural tests hold every preset to minimum thresholds and reject orphaned or broken manifest entries; property-based tests cover the merge, backup, and round-trip invariants. Over 600 tests run on three operating systems before anything ships. - **The docs cannot drift.** The reference section is generated from the shipped manifests on every build, so its counts are the real ones. Where it is the wrong choice: Kiro-Kit is opinionated. If you want to hand-pick every file, or you are not on npm, a template repository or a steering collection will fit you better. ## Documentation Full documentation lives at **<https://ihatesea69.github.io/kiro-kit/>**. | | | |---|---| | [Quick Start](https://ihatesea69.github.io/kiro-kit/docs/guide/quick-start) | Install and first workspace | | [Preset Reference](https://ihatesea69.github.io/kiro-kit/docs/reference) | Every preset's commands, agents, skills, hooks, Powers, and example specs | | [CLI Reference](https://ihatesea69.github.io/kiro-kit/docs/guide/cli-reference) | Every command and flag | | [How It Works](https://ihatesea69.github.io/kiro-kit/docs/guide/how-it-works) | Lifecycle, merge semantics, conflict resolution, backups | | [Features](https://ihatesea69.github.io/kiro-kit/docs/features/deep-security-scan) | Deep security scan, spec-driven development, MCP and Powers, native hooks | | [Creating Presets](https://ihatesea69.github.io/kiro-kit/docs/guide/creating-presets) | Author your own preset | The reference section is generated from the preset manifests on every docs build, so its catalogs and counts are always what actually ships. ## How it behaves - Presets ship inside the npm package. Nothing is fetched at install time, so it works offline. - Your files win. If a file already exists with different content, you get a prompt, not an overwrite. Backups are written before anything is replaced. - Writes go to a temp file and then get renamed, so a crash or Ctrl-C can't leave a half-written file behind. - Presets are independent. Installing one never pulls in another, and removing one doesn't break the rest. ## Privacy Telemetry is **off by default** and no data leaves your machine unless you opt in with `kiro-kit telemetry enable`. See the [CLI reference](https://ihatesea69.github.io/kiro-kit/docs/guide/cli-reference#privacy-and-telemetry). ## Contributing Got an idea for a new preset, or want to improve an existing one? See [CONTRIBUTING.md](./CONTRIBUTING.md) and [Creating Presets](https://ihatesea69.github.io/kiro-kit/docs/guide/creating-presets). ```bash git clone https://github.com/ihatesea69/kiro-kit.git cd kiro-kit pnpm install pnpm test ``` ## License [MIT](./LICENSE)