feat: Add Kiro CLI support and mcp feature with project mode

[maekawataiki]

Summary

• Rename Kiro IDE → Kiro
  • since Kiro IDE / CLI / Autonomous Agent supports same .kiro/steering rules.
  • ignore is only supported for Kiro IDE. (BTW, Kiro IDE requires .kiroignore instead of .aiignore https://kiro.dev/docs/editor/kiroignore/ so we might need to fix that)
• Adds MCP feature support (.kiro/settings/mcp.json for both Kiro IDE and Kiro CLI. Kiro Autonomous Agent currently requires setting mcp from web app)

Refactored version of #785

Features Added

Tool	rules	ignore	mcp	commands	subagents	skills
Kiro (renamed)	✅	✅	✅ (new)

✅ = project mode, 🌏 = global mode

Implementation Details

• mcp.json output to .kiro/settings/mcp.json

Testing

All tests passing. pnpm cicheck:code passes.

[dyoshikawa]

@maekawataiki Sorry, it's still large. First, can you create a PR about kiro cli rules only? The number of a external developer's PR changed lines should be less than 400 as much as possible I guess. This rule is implicit, so I will add that to CONTRIBUTING.md later.

I will accept your suggestions, of course. Thank you.

[maekawataiki]

@dyoshikawa Thanks for comments. Narrowed down to kiro cli rules only.

[maekawataiki]

Seems the AI code review workflow (OpenCode) cannot access secret for PR from fork.

[dyoshikawa]

Thank you! I've made some changes to CI and other things, so please rebase on the latest main.

[cm-dyoshikawa]

@maekawataiki My question: Is there difference between Kiro IDE and Kiro CLI actually? According to https://kiro.dev/cli description, they are not separate products, and both have shared specifications.

If my opinion is true, please expand the existing implementation for Kiro IDE simply. And Kiro IDE in README.md should be changed to simple Kiro.

[maekawataiki]

Thanks for fixing CI.

That's a fair point. I've separated it because some features require different implementations, such as commands, subagents, and skills, whereas rules and mcp use the same settings file.

Since AWS is converging different products into Kiro with the same .kiro folder as the settings folder, I think it makes more sense to generate/import all files with kiro for both Kiro IDE and Kiro CLI (plus Kiro Autonomous Agent).

I will fix this PR.

[cm-dyoshikawa]

@maekawataiki Thank you! Please follow that strategy.

[maekawataiki]

@cm-dyoshikawa
I've updated the PR. The scope has pivoted to renaming Kiro IDE to Kiro and adding MCP feature support.

[maekawataiki]

By the way, Kiro IDE ignore feature requires .kiroignore file instead of .aiignore.
https://kiro.dev/docs/editor/kiroignore/

Should we fix that?

[cm-dyoshikawa]

Thank you!