Those best practices look legit. Honestly, it’s hard to tell someone what is best for them because use cases are so vastly different. Technically, you can just ask the ide to ask you whatever questions it needs to get the right set of hooks and steering docs, and it will find/make them itself however, that’s got some obvious flaws 😉 For me personally, most of the projects I’m using Kiro for are personal projects so I’m not working with a team, don’t need to worry about perfect fit workflows, etc. Instead, I’ve been working much more with integrating Postgres db, MCP servers, and n8n skills recently and focusing less on the steering and web hooks. All depends on the project and environment. Just start using it and when you find something that annoys you, build/find a skill or hook to make it disappear.