Files
cursor__plugins/create-plugin/README.md
ericzakariasson 97128c02db Apply writing guide: sentence-case titles, remove em-dashes and semicolons
- Convert all H1 headings to sentence case across skills, rules, agents,
  commands, and READMEs (~65 headings)
- Replace em-dashes with colons in plugin.json descriptions and README
  taglines to match marketplace.json convention
- Replace semicolons with periods and restructure sentences across skills,
  rules, agents, and READMEs (~19 instances)

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-10 18:11:09 -08:00

47 lines
1.2 KiB
Markdown

# Create plugin
Meta workflows for creating Cursor plugins that are marketplace-ready.
## Installation
```bash
agent install create-plugin
```
## Components
### Skills
| Skill | Description |
|:------|:------------|
| `create-plugin-scaffold` | Scaffold a new plugin directory with manifest, components, and repository wiring |
| `review-plugin-submission` | Run a pre-submission quality check against marketplace expectations |
### Rules
| Rule | Description |
|:-----|:------------|
| `plugin-quality-gates` | Keep plugin manifests, component metadata, and paths valid and consistent |
### Agents
| Agent | Description |
|:------|:------------|
| `plugin-architect` | Design plugin structure and component mix based on a concrete use case |
### Commands
| Command | Description |
|:--------|:------------|
| `create-plugin` | Build a new plugin scaffold with the right files and metadata |
## Typical flow
1. Use `/create-plugin` with a plugin name, purpose, and target component types.
2. Generate or update `plugin.json`, then add rules/skills/agents/commands as needed.
3. Run `review-plugin-submission` before publishing or marketplace submission.
## License
MIT