plugin-quality-gates
Keeps plugin manifests, paths and component metadata valid while a plugin is being written.
- Kind
- Rules
- Works with
- Cursor
- Source
- cursor/plugins @ 9580c23696ac
- Path
- create-plugin/rules/plugin-quality-gates.mdc
- License
- MIT
- Jobs
- Guardrails
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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.