|
|
|
|
|
by dugidugout
78 days ago
|
|
I think you are still speaking in the lower abstraction in terms of zwaps' provided understanding. "Tagging specific code" or "files" is likely the type of interfacing most Claude Code users are _not_ doing. 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. |
|
I'm not telling you to go use cursor, just to help clarify that you can drive both solutions with the exact same approach and skillset and get very similar results - the difference is the UI. I personally like being able to paste screenshots into the agent, etc.