Cursor rule library

Personal library of reusable Cursor project rules (.mdc files). Copy individual rules into a project as needed.

Layout

rules/           # Source .mdc rules

Use a rule in a project

Copy the rule file into the project’s .cursor/rules/ directory:

mkdir -p .cursor/rules
cp ~/projects/cursor-rules/rules/production-quality.mdc .cursor/rules/

Available rules

Rule	Applies	Purpose
production-quality	Always	Production-ready, sustainable code — no hacks or temporary fixes
typescript-best-practices	Agent decides	TypeScript typing, errors, modules, and control-flow standards
php-best-practices	Agent decides	PHP 8.2+, PSR-12, typing, security, and structure standards
react-best-practices	Agent decides	React components, hooks, state, effects, keys, and a11y standards
wordpress-plugin-best-practices	Agent-requested	WP plugin security, hooks, lifecycle, Settings/REST, enqueue, i18n
wordpress-theme-best-practices	Agent-requested	WP theme templates, theme.json, enqueue, classic/block, a11y, i18n
handoff-document	Agent decides	Read and maintain HANDOFF.md for project continuity across sessions
github-workflows-best-practices	Agent decides	GitHub Actions craft, CI caching, and keeping workflows synced with related project changes

Add a new rule

1. Create rules/<name>.mdc with YAML frontmatter (description, alwaysApply: false, and no globs) and a concise markdown body (aim for under ~50 lines).
2. Document it under Available rules above.
3. Commit it here.
4. Copy it into a project’s .cursor/rules/ when you need it.