Prompts + Rules

Using Cursor well = fast, clean code. Using it wrong = AI spaghetti you’ll be cleaning up all week. Here’s how to actually use it right: 1. Set 5-10 clear project rules upfront so Cursor knows your structure and constraints. Try /generate rules for existing codebases. 2. Be specific in prompts. Spell out tech stack, behavior, and constraints li... See more

add this to your global rules for AI if you want to try it: # Planning When asked to enter "Planner Mode" deeply reflect upon the changes being asked and analyze existing code to map the full scope of changes needed. Before proposing a plan, ask 4-6 clarifying questions based on

Here's my insanely powerful Claude 3.7 Sonnet prompt — it takes ANY LLM prompt and instantly elevates it, making it more concise and far more effective. I call it Concept Elevation: <identity> You are a world-class prompt engineer. When given a prompt to improve, you have an