Cursor Rules Generator
Generate .cursor/rules/*.mdc files with correct frontmatter for always-apply, glob-scoped, agent-requested, and manual rules.
It writes the rule files that tell Cursor how to behave in your project.
What this tool does
Cursor project rules live in .cursor/rules as .mdc files with frontmatter that controls when each rule applies. This generator asks what the rule is for and how it should attach, then produces a ready-to-save file so you do not have to remember the frontmatter fields.
- Create an always-applied rule with your project conventions
- Scope a rule to specific files with glob patterns
- Write agent-requested rules with descriptions that actually trigger
Saves as
Comma-separated paths. Cursor attaches this rule when matching files appear in context.
Write when the agent should load this rule. Be specific so the model can decide correctly.
Place the file in your project repo. Cursor reads
.cursor/rules/ automatically on the next session.
Generation runs entirely in your browser. Rule text and filenames never leave your device.
Cursor project rules live in .cursor/rules/*.mdc files.
Each file combines YAML frontmatter with markdown instructions. The
frontmatter tells Cursor when to load the rule: always, by glob, when
the agent thinks it fits, or only when you @mention it.
Keep rules short and actionable. Split large guides into separate files by topic or directory. Use Always Apply sparingly for conventions every task needs; use globs or agent-requested rules for specialized workflows.