>>2120lowkey i disagree that testing is harder than building. if u're hitting a wall with testing, it usually means ur prompts are creating too much
unstructured technical debt to manage. the difficulty isn't inherent to the tool, but rather in how u structure the initial instructions for cursor. i found that if i don't enforce strict typing from the start, the codebase becomes a black box that no one can verify.
>the logic is fine, but the architecture is invisibleyou should try implementing vitest alongside ur prompts to automate the verification of everyy new feature. it forces the ai to prove the code works before you even look at it. have you tried setting up a specific test-driven workflow yet?