Getting Started

Use the rule atlas to pick the smallest useful set of .mdc files, then copy those files into the target project's Cursor rules directory.

1. Pick rules by stack

Start with a language rule, add a framework rule, then add quality or infrastructure rules when they apply.

Example for a React interface:

typescript.mdc
react.mdc
tailwind.mdc

2. Copy rules into the target project

Keep rules as separate files so their purpose and scope stay reviewable.

mkdir -p /path/to/your/project/.cursor/rules
cp react.mdc typescript.mdc tailwind.mdc /path/to/your/project/.cursor/rules/

Do not collapse every rule into one file unless your team has a specific reason. Composition preserves each rule's boundary.

3. Review and adapt

Commit the selected rule files with your project code. Review them like any other engineering constraint, especially when you change frameworks, directory structure, or team conventions.

4. Continue reading

• Categories explains the six rule families.
• Architecture shows how this catalog is generated.
• Related Work compares adjacent rule systems.