Focused .mdc output
Each generated rule includes description, globs, alwaysApply, and short sections Cursor can retrieve for the matching files.
Free Tool
Free Cursor Rules Generator
A Cursor rules generator creates copy-ready .cursor/rules files that tell Cursor how to work inside your codebase. Choose a stack, add architecture and verification rules, then copy a modern .mdc file with frontmatter.
Build a Cursor rule
next-js-app-router-standards.mdc
---
description: Next.js App Router Standards rules for Next.js projects
globs: src/app/**/*.{ts,tsx},src/components/**/*.{ts,tsx}
alwaysApply: false
---
# Next.js App Router Standards
## Architecture
- Prefer server components for route shells.
- Keep client components small and colocated with the route that owns them.
- Export metadata from the page or layout that owns the URL.
## Code style
- Reuse existing design tokens and components.
- Use lucide-react icons for actions.
- Keep labels and generated output readable on mobile widths.
## Verification
- Run npm run lint.
- Run npm run build.
- Smoke-test the generated route and copy/download actions.
## Pull request checklist
- Confirm generated files match the selected stack and globs.
- Confirm public-facing copy is specific, accurate, and mobile-safe.
- Confirm verification commands and any skipped checks are documented.
How to generate Cursor rules
- Choose a stack. Pick the project type that best matches the files Cursor should work on.
- Add focused guidance. Write architecture, style, and verification rules as short, specific lines.
- Set globs and apply mode. Scope the rule with file globs, then decide whether it should always apply.
- Copy the .mdc file. Copy or download the generated rule and save it under .cursor/rules.
Stack-aware presets
Start from Next.js, Python CLI, or documentation defaults, then tailor the rule to your repository and review workflow.
Browser-only generation
Your project guidance stays in the page session. The generator formats text locally for copy or download.
Cursor rules FAQ
What is a Cursor rules generator?
A Cursor rules generator creates .cursor/rules .mdc files that tell Cursor how to work in a codebase, including architecture preferences, file globs, style rules, and verification commands.
Where do generated Cursor rules go?
Save generated project rules in .cursor/rules at the repository root. Each rule should use the .mdc extension and include frontmatter with description, globs, and alwaysApply.
Should a Cursor rule always apply?
Use alwaysApply only for broad standards that are relevant to every file and prompt. Use globs for framework, folder, or workflow-specific rules.
What should I put in Cursor rules?
Good Cursor rules include project architecture, coding style, data boundaries, testing commands, review expectations, and any patterns the team wants repeated consistently.
Does this tool upload my project rules?
No. The generator runs in your browser and does not send your rule text to Tornic or a third-party service.