Skip to content

Instantly share code, notes, and snippets.

@Stormix
Created February 24, 2026 15:38
Show Gist options
  • Select an option

  • Save Stormix/4c82378e8c7b6c5ab78f6f0cd58b499f to your computer and use it in GitHub Desktop.

Select an option

Save Stormix/4c82378e8c7b6c5ab78f6f0cd58b499f to your computer and use it in GitHub Desktop.
Cursor 101 - Short version

Starting fresh on a project? Here's how I set up my Cursor.

Recommended plugins:

  • Context7
  • Superpowers
  • Continual Learning
  • Cursor Team Kit

Start by creating 5 foundational rules:

You can use /create-rule to add these, but I would discard the AI output and write them manually

1. General ADRs - Document key architectural decisions AI agents should respect. Keep it brief and high-signal.

2. Codebase Structure - Short map of your packages/apps (especially useful for monorepos), plus conventions like "tests go in a /tests directory mirroring the service name."

3. Workflow - Plan, analyze patterns, create TODO, validate, run lint and type checks.

And my favorite addition:

"This codebase will outlive you. Every shortcut becomes someone else's burden. Every hack compounds into technical debt that slows the whole team down. You are not just writing code. You are shaping the future of this project. The patterns you establish will be copied. The corners you cut will be cut again. Fight entropy. Leave the codebase better than you found it."

4. Coding Style - No any, prefer utility types over re-creating them, self-documenting code, DRY, etc.

5. Self-Improvement - Instruct the agent to propose new rules when patterns are consistently reused. Alternatively, run /continual-learning after a few sessions.

Add skills (like rules, but dynamic):

Check out this unlisted Cursor video explanation: https://www.youtube.com/watch?v=L_p5GxGSB_I

Stack-specific recommendations:

Superpowers skills are already bundled with the plugin.

Your workflow as a developer:

Fresh chat every time - no stale context.

Plan mode - Use a strong model (Opus, GPT Codex 5.3, or Sonnet 4.6 Thinking). Describe your task or use Superpowers (check the "Try in Chat" button on the plugin page).

Template:

"We need to build X feature to support Y. Ask me 5-10 questions to refine the scope and create an implementation plan. No code snippets needed."

Skip the questions if your codebase context is already well-established.

Review and iterate on the plan until it's solid.

Switch to build mode - Composer 1.5 / 1 / Sonnet models, then hit Build.

Review the output - Ask Opus to diff staged changes against the original plan.

Finish strong - Add tests, run linters and type checks.

Optional: Run /deslop from Cursor Team Kit for a final cleanup pass.

What now?

After a few chats, run /continual-learning to distill learnings from your previous agent transcripts into additional context in AGENTS.md.

Then create skills using skill-creator for common tasks:

  • /fix-pr - Check a PR status on GitHub and fix failing checks.
  • /commit - Commit staged changes after running lint hooks with a well-formatted message following your standard conventions.
  • /review - Shorthand to have Cursor review your code for security issues, bad patterns, and potential problems.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment