Cursor Rules Generator (MDC Format)

Highlights

Example output

---
description: "Core project conventions (always applied)"
alwaysApply: true
---

## Code Style

- Never use the `any` type in TypeScript. Prefer `unknown` with type narrowing.
- Use functional components exclusively. Manage state with hooks.

## Git Workflow

- All commit messages must follow Conventional Commits.

Frequently asked questions

• How is .cursorrules different from .cursor/rules/*.mdc? ▾

  .cursorrules is the legacy format that puts every rule into a single file. .cursor/rules/*.mdc is the recommended format starting with Cursor 0.45+. MDC adds frontmatter for alwaysApply / globs / description-based triggers, which saves tokens and makes scope explicit.
• Why split into core / stack / boundaries — three files? ▾

  Cursor's official docs recommend a multi-file, topic-based layout. core.mdc (alwaysApply) covers project-wide rules that always apply, stack.mdc (globs) targets file patterns like frontend or tests, and boundaries.mdc (description) is consulted only when needed — keeping each file's role distinct.
• Does this work on Cursor versions older than 0.45? ▾

  The .cursor/rules/*.mdc directory format is recognized only in Cursor 0.45+. If you are on an older version, update Cursor or temporarily port the content into .cursorrules. ConfigDeck outputs the recommended 0.45+ MDC format.
• Can I edit the MDC frontmatter fields myself? ▾

  Yes. alwaysApply / globs / description are all yours to tweak. ConfigDeck's Phase A produces the most common 3-file layout, and after that we recommend narrowing globs patterns to fit your project structure or adding extra .mdc files by hand.
• How do I migrate from an existing .cursorrules? ▾

  Move the content of your existing .cursorrules into ConfigDeck's Best Practices and Boundaries inputs and generate the 3-file MDC output. Then delete .cursorrules and commit only the .cursor/rules/ directory — the migration to the 0.45+ recommended layout is complete.