[mkw5053]

I’ve been using Cursor extensively on TS projects and noticed a big improvement in speed and code quality by enforcing clear guardrails (strict types, linting, formatting) combined with rigorous TDD. When I hit an error or exception, I explicitly tell the agent to pause and first figure out the best way to debug and quickly pinpoint the root cause. This approach generally works well, provided I’ve decomposed the problem enough that we’re debugging just one thing at a time (though that’s not always trivial).

I’m interested to try this out to see if or how much it speeds things up further.

[30minAdayHN]

Co-author here. We found it pretty useful in our personal projects. Would love to hear your feedback on how it went.

If you come across any issues specific to your stack, happy to look into them.

[arthurgousset]

Thanks for sharing!

> When I hit an error or exception, I explicitly tell the agent to pause and first figure out the best way to debug and quickly pinpoint the root cause.

Out of curiosity, how do you tell Cursor about the bug? Do you copy/paste console messages from the terminal into the prompt?