Designers using Cursor, where are you all? đ
Hello, PH! Iâm a designer who boldly switched from Framer, which I had been loyal to for two years, to Cursor recently. This has been the best decision Iâve made this year. The biggest reason is that the cost savings have been truly dramatic. Cost comparison: Framer: Even the mini version costs $15 per month ($180 annually), and running 3 sites would cost $540 a year (if I had created with Framer, it would have added another $180, totaling $720). Cursor: Just $120 for an annual subscription! Unlimited projects possible. And there are no hidden costs or additional feature fees at all. The Cursor subscription fee covers everything. (I feel like Iâm advertising now;;;) Besides the cost, here are the other benefits of Cursor for designers: - Anything is possible beyond the features offered by Framer. - No need for complicated tutorials or studying; you can use it right away. - You can implement everything you imagine just with prompts. I think Iâll continue using Cursor, so Iâd love to connect with other designers. Is there a group for designers using Cursor?? I want to share good tips with designers who use Cursor!
Experimenting with Cursor
At @Bucket, we're always looking for products that can boost productivity and inspire us to build better software. We recently experimented with @Cursor to replace @Github Copilot.
Key takeaways
Tab completion: Cursor includes a helpful tab completion feature, suggesting refactorings and improvements as you go â huge time saver!
Chat: the chat/composer is better than Copilot as it can modify across files in the codebase. However, we still needed to correct the code most of the time :/
Full context: Cursor has full context, so it provides more helpful advice and changes
Generating comments: it makes it easier to add code comments â they need clarifications from time to time tho
Working with existing codebases: Cursor seems better at writing code from scratch than contributing to large existing codebases
Hallucinations: as far as we can tell, it had fewer hallucinations compared to alternatives
Prompting strategies: being somewhat specific in prompts by referencing classes and functions seems to work well â We're currently experimenting with `.cursorrules` files to improve prompt quality
#vibecoding: What are your favorite Cursor pro-tips?
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
Windsurf users: which models are you using?
There's a lot of options for models these days. I've been using Claude 3.7 but I'm curious what's been working well for others. What model are you using and why?
Is the thinking version of @Claude by Anthropic worth the extra credit spend? Does @DeepSeek work well enough to save some credits? Is it worth trying any of the @ChatGPT by OpenAI models?
Any favorite MCP tools?
I'm fascinated by the ability to extend what Cursor can do with MCP features but there are so many out there, with some of questionable pedigree, that I'm having a hard time finding the gems.
I've tried a few but so far I've only gotten good usage from the Think tool which allows Cursor to basically jot down notes on it's process which it can then refer to later. Theoretically allowing more context than just the context window https://github.com/DannyMac180/mcp-think-tool Since I've installed it Cursor seems to use it a lot but it's hard to gauge how much it helps in practice. I'm glad the AI likes it though :)
What do you think the future looks like for developers when it comes to AI?
ICYMI: @levelsio shipped a flight simulator game last week. It's pretty fun, it's got some low poly / minecraft-esque graphics, pretty good physics, a turbo boost, and even PvP. The kicker is he built it, at least the version one anyway entirely by prompting @Cursor.
It got me thinking about a question that a ton of people have tried to answer in the past few years; What does the future look like for someone getting into development?
