Subscribe
Sign in
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:
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 :)
Are there any must have MCP tools that you found have improved your workflow?
Hello PH!
I'm Hyuntak form South Korea, quite new to this community, first time posting.
I'm a med student and solo developer.
Cursor did deal with hassles that would otherwise have me glued to the monitors for days.
BUT, cursor(actually, the AI) did made things harder in some cases.
Not to mention what I call "the loop of errors" - when you ask the AI to resolve error A, it makes error B, and then to resolve error B, it makes error A,
the extreme case was the ai suggested me to create a whole new project and migrate my current codebase, which wasn't the case.
As a fellow Cursor user, could you share your moment of "loop of errors" or extreme suggestions that the Cursor(ai) made?
