←back to thread

Kiro: A new agentic IDE

(kiro.dev)
1015 points QuinnyPig | 2 comments | 14 Jul 25 14:24 UTC | HN request time: 0.416s | source
Show context
NathanKP ◴[14 Jul 25 15:03 UTC] No.44561071[source]▶
Hello folks! I've been working on Kiro for nearly a year now. Happy to chat about some of the things that make it unique in the IDE space. We've added a few powerful things that I think make it a bit different from other similar AI editors.

In specific, I'm really proud of "spec driven development", which is based on the internal processes that software development teams at Amazon use to build very large technical projects. Kiro can take your basic "vibe coding" prompt, and expand it into deep technical requirements, a design document (with diagrams), and a task list to break down large projects into smaller, more realistic chunks of work.

I've had a ton of fun not just working on Kiro, but also coding with Kiro. I've also published a sample project I built while working on Kiro. It's a fairly extensive codebase for an infinite crafting game, almost 95% AI coded, thanks to the power of Kiro: https://github.com/kirodotdev/spirit-of-kiro

replies(27): >>44561401 #>>44561480 #>>44561505 #>>44561508 #>>44561540 #>>44561643 #>>44562248 #>>44562738 #>>44562815 #>>44562867 #>>44562880 #>>44563346 #>>44563915 #>>44563941 #>>44563988 #>>44563992 #>>44564153 #>>44564270 #>>44564551 #>>44565359 #>>44565453 #>>44565634 #>>44565909 #>>44566659 #>>44567132 #>>44568049 #>>44570644 #
1. spgingras ◴[14 Jul 25 16:46 UTC] No.44562248[source]▶
Can you comment on how the IDE performs on large codebases? Does the spec based approach help with it? Any examples you can give from experience at Amazon?
replies(1): >>44562829 #
2. NathanKP ◴[14 Jul 25 17:27 UTC] No.44562829[source]▶
It works great in really large codebases!

I've published a sample project that is medium sized, about 20k lines encompassing a game client, game server, and background service: https://github.com/kirodotdev/spirit-of-kiro This has been all developed by Kiro. The way Kiro is able to work in these larger projects is thanks to steering files like these:

- Structure, helps Kiro navigate the large project: https://github.com/kirodotdev/spirit-of-kiro/blob/main/.kiro...

- Tech, helps Kiro stay consistent with the tech it uses in a large project: https://github.com/kirodotdev/spirit-of-kiro/blob/main/.kiro...

And yes, the specs do help a lot. They help Kiro spend more time gathering context before getting to work, which helps the new features integrate into the existing codebase better, with less duplication, and more accuracy.