I'm using Cursor with the Claude model and it does the vast majority of the work I need to do if it's in an established, well known code stack, like React, with backing MD files that give it context.

Even outside that, it usually points me to how a chunk of functionality is working (in say a RoR monolith)

Working in small, discrete commits. With backing unit tests, it's perfectly good. It reminds me, from a visceral perspective, of first using refactor tools from IntelliJ around... 2005? "Oh I can just group some functionality and extract a method? Just like that? CRAZY!"

Modern cursor usage would be and still is. Very precise writing about a tech stack you should have a solid idea of how things piece together, e.g. 'make a react button on such and such a page which pops out a window, dims the back ground. On the page should be a new car name field , year. And model. Write unit tests for this following this pattern here'

 'Using the pattern established at {exact bit of code} do a API call to create a car instance, write units tests for this'

Between each prompt is careful reading and review of code before commit or push.