That is interesting. So far we are just using the task list to keep track of the list of implemented tasks. In the long run I expect there will be an even more rigorous mapping between the actual requirements and the specific lines of code that implement the requirements. So there might be a fourth file one day!

Coding standards / style guide are both part of the "steering" files: https://kiro.dev/docs/steering/index