Instead they are defining architecture through specs and verification-loops and attempting to one-shot solutions fitting clear tests. On reflection, I personally don't have many prompts with CC referencing files or code directly, rather I speak in specifications I can then track to a given instance of work in review.
This isn't to suggest you can't work at this abstraction in cursor or w/e interface, but the features you suggest are hardly relevant to the divide zwaps is identifying.