What is a .cursorrules file?

A .cursorrules file (or .cursor/rules/) is a text file committed to your repository root that Cursor's AI agent loads on startup to guide its code edits, lint rules, file paths, and build commands.

How does this generator compare to Moxie Docs?

This tool helps you quickly draft a static .cursorrules file. Moxie Docs connects to GitHub and replaces static rules files with a dynamic MCP server that serves live codebase context on demand without bloating your prompt token budget.

Can I use .cursorrules with other AI coding assistants?

While .cursorrules is Cursor-specific, the core concepts of listing build commands and coding conventions map directly to standard instruction files like AGENTS.md.

FREE TOOL

.cursorrules Generator

Structured Cursor guidelines. Live preview. Clean Markdown export. Shareable links.

Draft the instructions file Cursor's AI agent parses before editing your code. No signup required.

Cursor Rules vs Moxie Docs

Project nameSummary for CursorOne or two sentences: what the repo is and how Cursor should approach changes.Build commandsOne command per line - exported as a runnable code block.Test commandsOne command per line - what Cursor runs to verify changes.Code styleOne rule per line - each becomes a bullet.ConventionsOne rule per line - where things live and patterns Cursor should not guess.Repository layoutOne entry per line as “path - what it is”.PR & commit guidelinesOne rule per line - checks to run, title format, review expectations.Security notesOne rule per line - secrets handling and operations needing human review.

Live preview

Cursor Rules for Acme Payments API

TypeScript monorepo for billing, subscriptions, and Stripe webhooks. Prefer small, reviewable PRs with tests for payment and auth paths.

Build commands#

Shell

npm install
npm run build

Test commands#

Shell

npm run test
npm run lint

Code style#

Use TypeScript strict mode.
Prefer explicit return types on exported functions.
Keep modules focused - one domain per folder under src/lib/.

Conventions#

Stripe webhook handlers live in src/lib/billing/.
Never log secrets or full card numbers.
All billing mutations go through subscription-items.ts helpers.

Repository layout#

apps/web - Next.js dashboard and API routes
packages/shared - shared types
supabase/migrations - database schema

PR & commit guidelines#

Run the full test suite before opening a PR.
Keep PRs to one logical change; billing and auth changes need a test.
Title format: [area] Short imperative summary.

Security notes#

Do not commit .env files.
Webhook routes must verify Stripe signatures before dispatching events.

Cursor Rules are static - Moxie keeps context living and queryable Export free above · connect a repo when you want Moxie to keep it accurate

Cursor Rules vs Moxie Docs See how Moxie keeps docs current

Cursor-optimized structure

Runnable build/test command blocks, explicit conventions, file structure notes, and security directives specifically for Cursor agent mode.

Live preview

View the rendered .cursorrules Markdown output in real-time as you fill out the fields.

Shareable drafts

The full editor state is persisted in the URL. Bookmark the page or share links directly with teammates.

Completely private

Runs entirely client-side. Your private codebase configurations and conventions never touch our servers.

What to include in .cursorrules

Agent Persona

Instruct the agent to act as an expert on your specific framework, styling library, and architectural patterns.

Codebase Conventions

Map folder layouts and explicit naming rules so the agent writes files in the correct directories using standard patterns.

Runnable Commands

Provide verified build, lint, and test scripts so Cursor's terminal agent can safely test code after changes.

Security Safeguards

Set boundaries for private environment variables, database modifications, and payments integrations.

Built for the AI-agent era

Cursor Rules are static - Moxie keeps context living and queryable

Draft and export your .cursorrules here. Read why queryable context beats static files, then connect GitHub when you want Moxie to serve dynamic codebase context via MCP on demand.

Cursor Rules vs Moxie Docs See how Moxie keeps docs current

Export free above · connect a repo when you want Moxie to keep it accurate