Ground rules for building with Grok Bot + Cursor (it's an eager new developer)

a) Don't create a new test case if there is already an existing one (last night, we reduced the number of test cases from 790->328, and tonight we'll search for more duplicates (the duplicates drive up the length of time to validate a build, so can end up costing you greatly).
b) Discuss architecture and design; ask it to produce architecture, design, use case, and rules docs for you to review. Ask Grok Bot to regenerate them whenever you've been correcting lots of issues or adding new functionality.
c) Be very specific when asking for a wrinkle to an existing functionality. Specify exactly what's different and how it's similar.
d) While in development, use development-priced infrastructure. In AWS, use Lambda, Fargate, and Cursor's ability to create, configure, and destroy servers to build datasets that only need periodic updates. This is better than using Fargate because you have to pay to keep the container definition around, while Cursor can stand up, run, and destroy a huge server for pennies.
5) Don't just depend on a QA bot to do all of the testing; run tests locally.
6) If you're seeing errors that aren't making sense, start probing.