Software engineers share best practices for using Cursor to write production-grade code
A software engineer asked the community for best practices when using Cursor to write production-grade code. The user currently provides architecture and design principle markdown files to guide the AI, but still encounters issues with object naming and placement not covered in those files.
Entities
Related
Users share strategies to reduce iteration loops with Claude Code
A Reddit user describes a multi-step workflow to minimize back-and-forth with Claude Code for production-ready code, involving iterative plan refinement before code generation. The post highlights a common pain point of excessive iteration in AI-assisted coding.
Developer seeks ways to have AI improve existing features rather than suggest new ones
A developer with over a year of AI-assisted project building reports difficulty getting AI to suggest improvements on existing features instead of proposing new ones. They have tried asking the AI to scan a project directory but find it consistently veers toward new feature suggestions.
Article argues expert intuition, not prompts, determines AI coding tool success
A member-only article contends that the effectiveness of AI coding tools like Claude Code, Codex, and Cursor Agent depends more on the user's expert intuition and organizational knowledge than on prompt engineering. It questions why the same tools yield vastly different results across engineers, suggesting that expertise in routing business requirements is key.
Users complain about pinned prompt in Claude Code overlay update on Cursor
After a recent Claude Code overlay update in Cursor, the user's prompt is now permanently pinned to the top while Claude generates a response, reducing the visible space for streaming output. Users are seeking ways to revert to the previous unpinned behavior.
Developer tests AI code review tools: Claude/Codex vs Cursor Bugbot vs others
A developer spent two weeks testing AI code review options after their team's review queue grew unmanageable. They found that asking Claude or Codex to review diffs works well solo but doesn't scale to teams doing 10+ PRs daily, and they began evaluating Cursor's Bugbot as a more automated alternative.