Skip to content

Instantly share code, notes, and snippets.

@wilmoore
Last active February 20, 2025 22:45
Show Gist options
  • Select an option

  • Save wilmoore/19871143e2fef3c09c5b2cd2eb80fdb2 to your computer and use it in GitHub Desktop.

Select an option

Save wilmoore/19871143e2fef3c09c5b2cd2eb80fdb2 to your computer and use it in GitHub Desktop.
Software Engineering :: Pair Programming :: AI Assistant :: Cursor :: About :: You are using Cursor AI incorrectly...

Software Engineering :: Pair Programming :: AI Assistant :: Cursor :: About :: You are using Cursor AI incorrectly...

⪼ Made with 💜 by Polyglot.

I'm hesitant to give this advice away for free, but I'm gonna push past it and share it anyway. You're using Cursor incorrectly.

Over the last few weeks I've been doing /zooms with software engineers - from entry level, to staff level and all the way up to principal level.

Here's what I've seen:

  • Using Cursor as a replacement for Google Search.
  • Under specification of prompts, not knowing how to drive outcomes and using low-level thinking of "implement XYZ please".
  • Treating Cursor as if it is an IDE, instead of it being an autonomous agent.
  • Blissful unawareness to the concept that you can program LLM outcomes.
  • Unnecessary usage of pleasantries ("please" and "can you") with it as if it was a human. If it fucks up, swear at it - go all caps and call it a clown. It soothes the soul.

Okay, well that last point - it doesn't really change the outcome of Cursor so let's focus on the other points....

Cursor has a pretty powerful feature called Cursor Rules and it's a killer feature that is being slept on/is misunderstood. A quick scour of GitHub for implementations and scouting the community forums reveals that people are using them incorrectly - they all roughly look like this...


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment