Maintaining a roadmap.md file capturing the general state of the project/startup (what you're focused on, next steps, what you tried that didn't work, external pressures) keeps the AI on the same page as you, which is the overarching goal of all prompts and comments: syncing the context in your brain with Cursor.

Use Cursor's chat mode for questions (asking it something) and composer/agent mode for changes; always use agent mode since it can use tools, run terminal commands, and edit files with no real downside.

Adding 'do not stop working on this until you've implemented this feature fully and completely' to prompts reduces model laziness, since models otherwise complete only two or three of several stages and ask if you'd like them to proceed.

When choosing between two solutions, prompting Claude to write a detailed paragraph arguing for each before concluding counters its tendency to be a 'yes man' that agrees with whatever it senses the user wants or its own previous reasoning, because once it recommends a solution in the first 5-10% of its response the rest is committed.

Because Cursor and AI models simply follow your instructions and won't correct your judgment, you the developer must make all big decisions and retain the vision; the bigger the decision, the less you should trust AI — trust it on naming variables and structuring functions, but not on design principles, tech stack, or which features to build.

Once a codebase grows large enough you should create specialized markdown files (e.g. database_setup.md documenting table structure, RLS policies, mandatory/nullable fields, and SQL queries) that you tag whenever working on that area, acting as internal documentation that gives the model everything it needs.

Environment variables should be placed in a .cursorignore file so chat and composer don't accidentally rewrite them, but you must then describe what's in those env files in the cursorrules file, otherwise Cursor has no knowledge of which env files exist.

The optimal setup uses Cursor as the programmer to implement code and Claude as a separate advisor/consultant for brainstorming features and next steps, keeping Claude's dedicated project context unbiased and uninfluenced by the full codebase that overfills Cursor's chat.

The hardest and most valuable skill in building a startup is not implementing features but identifying what truly matters and ruthlessly narrowing each new feature to its MVP — done in two stages (at brainstorm, then after a few hours of building) — because most parts of a feature are unnecessary and most people work on things that don't matter.

Prompting a model to 'start the reasoning paragraph with lots of uncertainty and slowly gain confidence as you think about the item more' counteracts the failure mode where models commit confidently and lose objectivity; this can be embedded as a 'reasoning' field at the start of structured JSON output to improve agent reliability.

Adding the phrase 'the fewer lines of code the better' to prompts produces cleaner, more minimal code because models otherwise try to impress you with overly advanced implementations full of unnecessary lines.

Instead of relying on Cursor's built-in Docs feature (which is imperfect), create a markdown file containing the full contents of frequently-referenced documentation so you can reliably tag it whenever needed.

Creating a .cursorrules file at the project root with project overview, desired AI personality, full tech stack, repeated processes, environment variable references, and current file structure dramatically improves how accurately Cursor responds to your codebase.

A robust prompt structure for building is: describe what you're doing in 2-4 sentences, tag the relevant files (avoiding files not immediately relevant), specify how to execute and what not to do, dump context (e.g. documentation), use delimiters to signal section breaks, repeat the core instruction, and specify output format.

You should switch to a new composer when you see weird behaviors or the model forgets key information, because that signals the context window is overloaded with too much code and too many referenced files.

Forcing the model to write three reasoning paragraphs before changing code on complex errors greatly improves accuracy, because LLMs predict the next token; once a model states it is certain it knows the error, the rest of its response is locked into that wrong direction.

AI models do not know how to prompt other AI models effectively, so you should have Cursor write a one-paragraph search query formatted as instructions to a human researcher, then paste it into Perplexity or ChatGPT, which have better web search than Cursor's built-in feature.

Putting the exact file location and name (including folder path) as a comment at the top of each file gives the AI critical context whenever the file is tagged or copied into another tool like Claude that lacks Cursor's location awareness.

Using a speech-to-text tool like Whisper Flow lets you dictate prompts at ~200-250 words per minute, far faster than typing (even at 120 wpm), which is hugely valuable for brain-dumping complex multi-file instructions quickly.

How much value you can extract from AI is inherently limited by your own skill level; improving your code understanding, abstraction, and logic raises the ceiling on what the AI can accomplish for you, so beginners who outsource everything and refuse to learn cripple themselves.