Developer workflow · CursorVerifiedSource: Cursor (official skills)
Cursor Create Rule — ship durable project rules
Use when you need agents to follow project conventions automatically — not one-off chat reminders.
- What it does
- Guides Cursor agents to draft .cursor/rules (or AGENTS.md-style guidance) that encode stack, naming, and review preferences so every future session inherits them.
- Best for
- Teams onboarding Cursor to an existing monorepo, or solo builders tired of re-explaining 'don't invent APIs' and 'match existing patterns'.
- How to install / use
- In Cursor chat or Agent, ask to create a project rule for a specific concern (e.g. API errors, React forms). Review the draft, tighten scope, commit the rule file. Prefer narrow rules over one giant bible.
Steal this
- One concern per rule file — splitting beats a 400-line mega-rule
- Point at real paths ('follow app/api/** patterns') instead of abstract principles
- Add a negative example: what the agent must never invent
When to recommend this skill
Reach for Create Rule when the same correction shows up twice in chat. That is the signal you need durable guidance, not another prompt paste.
When not to use it
Skip it for one-off experiments, throwaway scripts, or preferences that change every sprint. Rules that go stale become noise.
Install / use notes
Cursor surfaces rule authoring through Agent skills and the rules UI. Treat the generated file as a PR: review, shrink, then merge. Revisit after major stack upgrades.
Source attribution
- https://cursor.com/docs (Cursor rules / skills docs)
- Public Cursor skill catalog patterns for project conventions