Free browser utility
All toolsCursor rules generator
Turn your project guidance into a scoped Cursor rule. Choose when it applies, state the edit boundaries and verification commands, and specify the evidence an agent should return.
This utility generates in your browser without uploading input. No signup or AI provider is needed. Use non-secret project context.
Generated Cursor rule
Start with the example or enter your own facts. Use Generate Cursor rule when you are ready, then review the result.
Methodology and format
This generator formats supplied instructions as an MDC file: YAML frontmatter between delimiter lines, followed by a Markdown instruction body. Save the reviewed project-guidance.mdc file in .cursor/rules/ in your repository. The .mdc extension is required for Cursor project rules; a plain .md file in that directory is not a project rule.
Activation follows Cursor's documented frontmatter table. Always apply sets alwaysApply to true and omits description and globs. Apply to specific files sets it to false and includes the description and globs. Apply intelligently sets it to false and includes description but omits globs. Apply manually sets it to false and omits both description and globs so that the description cannot accidentally enable agent selection. Your description is preserved in the body in every mode.
Description strings and comma-separated glob strings are double-quoted and escaped for YAML, including quotes, backslashes, line breaks and non-printable characters. The alwaysApply value is a Boolean, not quoted text. Glob input must be one line without control characters; clear it when switching to another mode. This checks the input shape, not whether a glob matches your files. The instruction body preserves your text under fixed headings; blank optional sections are omitted. No commands, permissions or successful results are invented.
Input limits are 1,000 characters each for description and globs, 6,000 for guidance, and 3,000 each for boundaries, commands and evidence, counted as UTF-16 code units. Surrounding whitespace is trimmed. Imported drafts accept only known fields and valid activation choices. Share links are limited to 8,000 characters; use the file download for longer drafts.
Generation runs in your browser without uploading input, inspecting files, calling an AI provider or automatically saving drafts. Copy and download happen on request. Copy share link puts the inputs in a URL fragment readable by anyone with that link; use non-secret drafting context. Other website features have their own data handling described in the privacy policy.
YAML 1.2.2: escaped characters — Reference for escaped characters in double-quoted metadata strings; the character-set section explains non-printable characters.
Cursor documentation: rules — Primary reference for .cursor/rules, MDC files, the four activation combinations, comma-separated globs and the limits of rules. Activation table checked October 9, 2026.
Limitations
Rules are prompt guidance, not a security boundary or guarantee of agent behavior. This tool does not install a rule, execute verification commands or check conflicts with your existing Cursor rules. Review the result in Cursor and confirm its activation before relying on it.
Glob patterns are not evaluated against a repository. Agent-selected activation depends on Cursor's relevance decision. The description requirement for manual and always modes is a drafting choice of this form, not a Cursor metadata requirement. Rules target Agent behavior; they do not govern Cursor Tab.
The bicycle dashboard example is fictional and its commands have not been executed. Replace the paths and checks with ones your project actually uses. The exported instruction body retains your text, including any Markdown you enter; review it before using or rendering the file elsewhere.
Frequently asked questions
Where do I save the generated Cursor rule?
Download project-guidance.mdc, review it, and place it in your repository's .cursor/rules directory. You can rename the file while keeping the .mdc extension. Check existing rules before adding it and confirm the activation shown in Cursor.
How do the four activation modes differ?
Always apply includes the rule in every chat session. File-specific rules attach when a matching file is in context. Intelligent rules let Agent select them using the description. Manual rules apply when you @-mention them. Manual exports omit both description and globs from metadata; the description remains readable in the body.
Does this generator choose rules or run my verification commands?
No. It deterministically formats the facts and instructions you supply. It does not inspect a repository, infer framework guidance, execute commands or verify agent compliance. Blank optional sections are omitted; a command in the file is an instruction, not evidence that it passed.
How do I enter more than one file glob?
Choose Apply to specific files and separate patterns with commas on one line, for example src/**/*.ts, tests/**/*.ts. The generator checks the input shape but does not match patterns against your repository. Leave File globs empty for the other activation modes.
Is my rule text uploaded by this utility?
Generation runs in your browser without uploading input or automatically saving drafts. Copy, file download and sharing are explicit actions. A share link contains the inputs in its URL fragment and is readable by anyone with the link. Use non-secret context; see the privacy policy for other website features.
Related guides and tools
Compare three scoped Cursor rules examples
Draft repository guidance as AGENTS.md
Draft a session-specific agent handoff
Coordinate Claude Code, Cursor and Codex