I do like the idea of saving prompts for projects like these (Which is also where the above question is answered: "Creating an MIT-licensed wrapper around Moto that has 100% feature parity with Localstack." [0] Which (i assume) is motivated by the recent changes to Localstack's distribution model [1])

[0] https://github.com/robotocore/robotocore/blob/main/prompts/2...

[1] https://blog.localstack.cloud/the-road-ahead-for-localstack/

Digital twin to me means an additional synchronized representation of a system that I can use to interact with the underlying plant.

I think this sort of thing is still useful. I'd never attempt to build something like this without modern AI tools. This is arguably a good use case assuming you are checking your work against AWS actual.

So this is awesomely timed.