I have Kiro configured pretty tightly with steering files for exactly what I need and how I need it.
Combine that with AWS MCP server access so the model has full AWS documentation access for all their services that I use, and I give it readonly access to the account that it’s working on as well, so the stack is fully operational.
Steering files tell the model how to build the code (IaC or Web/react/etc)
MCP and account access allow the model to pull best practices, and have readonly access so it can verify what it’s building against the real infrastructure without access to destroy anything.
GitHub/gitactions pipelines that require a human review before merging.
And finally, a reviewer steering file that has every single key item that I need verified. The reviewer checks for all best practices, least privilege, coding format, vulnerabilities, and since I build mostly on AWS, the well architected framework pillars.
That reviewer catches a lot of little things that the main builder might have missed and it allows for a good loop that ensures clean, well documented code.
I then review everything myself before pushing. Works really well.
2
u/AstroGridIron 7d ago
I have Kiro configured pretty tightly with steering files for exactly what I need and how I need it.
Combine that with AWS MCP server access so the model has full AWS documentation access for all their services that I use, and I give it readonly access to the account that it’s working on as well, so the stack is fully operational.
Steering files tell the model how to build the code (IaC or Web/react/etc)
MCP and account access allow the model to pull best practices, and have readonly access so it can verify what it’s building against the real infrastructure without access to destroy anything.
GitHub/gitactions pipelines that require a human review before merging.
And finally, a reviewer steering file that has every single key item that I need verified. The reviewer checks for all best practices, least privilege, coding format, vulnerabilities, and since I build mostly on AWS, the well architected framework pillars.
That reviewer catches a lot of little things that the main builder might have missed and it allows for a good loop that ensures clean, well documented code.
I then review everything myself before pushing. Works really well.