Cursor Rules and AGENTS.md
Our verdict
If you vibe-code in Cursor, rules are how you stop re-explaining your stack. Start with a short project rule and grow it when you catch repeated mistakes.
- Who it's for
- Cursor users on any project that lasts more than a day
- Leverage
- Consistent AI output across sessions
- Effort
- Low
- Date added
What it does
Cursor supports Project, Team and User Rules, plus AGENTS.md, as persistent instructions that shape how the agent writes code.
How builders use it
- Add a project rule describing stack, folder structure and do/don'ts.
- Scope rules to file patterns (e.g. API routes vs UI).
- Commit rules to the repo so collaborators share them.
What to expect
Less drift and fewer 'that's not how we do it' fixes.
Copy this: Project rule starter
Stack: Next.js App Router, TypeScript, Tailwind, Supabase.
- Server components by default; 'use client' only when needed.
- Data access only through lib/db/*.
- Validate all inputs with zod at API boundaries.
- Never commit secrets; read from process.env.
- After changes, run `npm run build` and fix errors.Related discoveries
- Vibe-Coding & Prompt-to-AppTool
Context7: up-to-date docs for AI editors
Feeds current, version-specific library docs into your coding assistant.
Effort: Low
- Coding & Shipping AgentsTool
Cursor Cloud Agents
Run Cursor's agent in the cloud so tasks continue while you work on something else.
Effort: Low
- Coding & Shipping AgentsTool
Cursor Bugbot for PR review
An AI reviewer that flags bugs and security issues on every pull request.
Effort: Low
- Coding & Shipping AgentsUse case
Give your agent a conventions file
A short CONVENTIONS.md stops agents from fighting your style every session.
Effort: Low
Want more like this?
Practical discoveries, without the noise.