Something went wrong. Try again.
Cursor plugin specification and official plugins
Something went wrong. Try again.
789 B · 15 lines
12345678910111213141516---description: Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.alwaysApply: true---
# Plugin quality gates
When creating or editing Cursor plugins:
1. Ensure `.cursor-plugin/plugin.json` exists and includes a valid `name`.2. Keep paths relative and within the plugin directory (no absolute paths, no `..` traversal).3. Match declared component paths to real files and folders.4. Include YAML frontmatter for rules, skills, agents, and commands with required metadata.5. Keep plugin scope focused and document installation and usage in `README.md`.6. Save new plugins to `~/.cursor/plugins/local/<plugin-name>/` by default so they are immediately available to Cursor. Only use a different location when the user explicitly requests it.