Cursor lessons: workflows, costs, mistakes, prompts
Reference lessons to use after the step-by-step tutorial.
Workflows
Bug fix loop
- Repro steps.
- Fix + test.
- Review diff.
Costs
The weekly pool covers Cursor and Grok usage. Set spending caps for third-party models.
Prompt library
Where is [feature] handled? List files and functions, with line ranges. Don't edit anything.Use-case playbooks
Bug fix
- Commit.
- Give a repro and expected value.
- Ask for a test, then run it.
New endpoint
- Write a rule scoped to the folder.
- Ask for route plus test.
- Review the diff.
Refactor
- Ask for a plan first.
- Approve one step at a time.
Animated walkthrough
Animated walkthrough
Press play, or pick a chapter. Each chapter animates its steps.
Troubleshooting
I hit a limit. What now?
Every tier's usage pool is shared across Cursor and Grok and refreshes weekly; third-party models are billed at API list price (Cursor). Start a new chat with a short summary instead of dragging a long one.
The answer cites a page that doesn't say that.
Treat the claim as unverified. Ask: quote the exact sentence from that page that supports this, or say it isn't there. Then open the page yourself.
It forgot my earlier instructions.
Long chats push early text out of context. Put standing instructions where Cursor keeps them (Rules: Project Rules in .cursor/rules (as .mdc files), User Rules, Team Rules, and AGENTS.md (Cursor docs).) and start a fresh chat.
It agrees with everything I say.
Ask it to argue the other side and list the strongest evidence against your view, with sources.
How do I keep costs down?
Free $0, Plus $8/mo (Grok models only), Premium $30/mo, Super $100/mo, Ultra $200/mo, Teams $30+/user/mo (cursor.com/pricing).
Cost control
Every tier's usage pool is shared across Cursor and Grok and refreshes weekly; third-party models are billed at API list price (Cursor).
- Test with the free tier on real tasks for a week first.
- Set a calendar reminder 2 days before any renewal.
- Keep one paid assistant, not three, unless each earns its place.
Prompt library: bad vs good
Bad: help me
Good: The checkout total is off by the tax when a coupon is applied. Repro: $100 cart, 10% coupon, 8% tax; expected $97.20. Find the cause, fix it, add a test, run the tests.
Why: situation, task, format and limits.
Bad: research this
Good: Find the 5 most relevant official sources from the last 12 months on [topic]. For each: title, date, link, and one sentence it actually says.
Why: asks for dated, quotable, checkable sources.
Bad: make it better
Good: Rewrite this for a busy customer: max 100 words, one ask, no jargon. Then list what you cut.
Why: a reader, a length and an audit of changes.
Bad: should I do X?
Good: List the 3 strongest reasons for and against X for someone in [situation]. Mark which reasons depend on facts I should check.
Why: balanced, and separates facts from judgement.
Privacy and safety
Download from cursor.com, open your project folder and make a git commit before the first big change.
- Don't paste passwords, ID numbers, card numbers or other people's private details.
- Assume the company can read and keep your chats unless its official policy says otherwise.
- For health, money or legal decisions, confirm with a professional or an official source.
Failure modes to watch
- Agent loops on one failing test.
- Rules file named .md and silently ignored.
- Changes outside the intended folder.
When to use it vs other bots
| Use Cursor for | Consider another bot when |
|---|---|
|
See: ChatGPT · Claude · Gemini · Perplexity · Copilot · comparison |
Leveled tutorials
Where these facts come from
- cursor.com/pricing: plans, usage pool, API and tax notes
Checked Oct 29, 2026. Plans change, so confirm on the official page before you pay.
Next: DeepSeek tutorial →