✅ - I think the idea of kiro is great, force planning (spec), systematic rules (steering)

[uneven rampart]

Hey, I'm super happy to have gotten access to Kiro. I think it's a great start and welcome a new player in the field.
I also think it was quite necessary to try to "steer" users towards better context management.

However, after now having tested it extensively, I think the execution is quite disappointing to be honest. My existing workflows I use with cursor and claude already do what these do, so I'm sure for vibe coders who tried to one-shot everything it's better, but to me, it wastes a lot of tokens, gets ahead of itself and is just to eager.

I'm still learning, I try to get a hang of all the tools, and I am excited that it's amazon and so I hope it'll stick around for a while and get better.

I thought I'd leave this feedback.

[tight heart]

Hi @uneven rampart, we are carefully reviewing all the feedback shared by the community and appreciate your input and initial impressions. We want to ensure users have a delightful experience with Kiro and are rapidly iterating on the product while it's in preview. As you continue building with it, please keep the feedback flowing because we want to hear how it's being used, what went well, what can be improved, etc. Thanks!

[uneven rampart]

Will do. I'm learning the INS and out with existing projects. I'll make one from scratch for the hackathon and then I can provide more feedback too

[flint jewel]

@uneven rampart I'd love to chat sometime to understand the problems you've run into with Kiro.

[uneven rampart]

Hey sure. I'm documenting and I likely make a write up as I did some guides on cursor. Then I think I have a very in depth view of what's different what I'd like to see and also my hacks which work

Can I hit you up after that? It should definitely be before the end of the hackathon as I'm kind of using this as an excuse to learn kiro

[frosty hound]

I've experienced some of this frustration, too. TBH, the biggest issue is that even the best current models don't understand how to work with existing code, APIs, style, etc.

Maybe it would be helpful to have an explicit "set up your steering docs" button so that devs know that we can do that. I didn't find out about steering docs until I had thrown away 3 iterations of a test project.

[uneven rampart]

I have a good work around for that I use in CC and Cursor, i shared this on the cursor sub a bit ago and also made a write down on my blog from the feedback it seems to work for many: any package or library I use a lot, I create detailed documentation that I edit and break down, then I add an index file that I include in the context to let the model know that it should find things here and ask it to always look at the relevant docs. I edit them and truncate to make sure it's positive prompts. Since I use the same libraries I can use the docs in several projects usually so it's worth it.

What I want to do in steering is now to include the summary of the summary and the rules the models break most often. playing around with that right now

[flint jewel]

Would you be open to getting on a call sometime

[uneven rampart]

yeah sure, as I mentioned I'm also logging and taking notes I can probably offer more later, but I'm also open to just chat. cheers

[uneven rampart]

@flint jewel I finished my write-up given the changes, I think Kiro has a lot of promise, here is a wish list, my hacks and issues I ran into compared to Cursor: https://aileverage.substack.com/p/comparing-kiro-with-cursor-after

[flint jewel]

Thank you for that writeup Oliver. There's a lot of the things mentioned we're working on. Would love to get on a call with you sometime next week.

I DM'd you my email

[drifting lantern]

Idea was great, but execution (in terms of current problems with billing) is totally bad.

[tawdry sapphire]

✅ - I think the idea of kiro is great, force planning (spec), systematic rules (steering)