feat: add Kiro IDE support via config-driven installer (#1589)

Replace broken kiro-cli.js custom installer with config-driven approach
using platform-codes.yaml. Creates Kiro-specific templates with
inclusion: manual frontmatter and #[[file:...]] reference syntax.
This commit is contained in:
Alex Verkhovsky
2026-02-08 09:18:28 -06:00
committed by GitHub
parent b1bfce9aa7
commit fc5ef57a5a
13 changed files with 87 additions and 341 deletions
+12 -1
View File
@@ -15,11 +15,22 @@ That means the authoritative list lives **in your project**, not in a static doc
## Where Commands Are Generated
The installer writes command files into your project (example paths for Claude Code):
The installer writes command files into your project. The location and format depend on your AI tool:
| AI Tool | Location | File Reference Syntax |
| --- | --- | --- |
| Claude Code | `.claude/commands/` | `@path` references |
| Kiro | `.kiro/steering/` | `#[[file:path]]` references with `inclusion: manual` frontmatter |
| Cursor | `.cursor/commands/` | `@path` references |
| Windsurf | `.windsurf/workflows/` | `@{project-root}/path` references |
Example paths for Claude Code:
- `.claude/commands/bmad/<module>/agents/`
- `.claude/commands/bmad/<module>/workflows/`
All tools invoke the same underlying `_bmad/` workflows and agents — only the launcher format differs.
These folders are the **canonical, project-specific command list**.
## Common Commands