Skip to content

Commit c697bde

Browse files
ericzakariassoncursoragent
ericzakariasson
and
cursoragent
committed
Add create-plugin meta plugin for plugin authoring.
Introduce a dedicated meta plugin with scaffold and submission-review workflows so teams can create marketplace-ready Cursor plugins with consistent structure and metadata. Register the plugin in marketplace metadata and the root plugin index. Co-authored-by: Cursor <cursoragent@cursor.com>
1 parent 50f1097 commit c697bde

11 files changed

Lines changed: 286 additions & 19 deletions

File tree

‎.cursor-plugin/marketplace.json‎

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,73 +5,73 @@
55
"email": "plugins@cursor.com"
66
},
77
"metadata": {
8-
"description": "Official Cursor plugin marketplace \u2014 developer tools, framework rules, MCP integrations, and agent skills"
8+
"description": "Official Cursor plugin marketplace — developer tools, framework rules, MCP integrations, and agent skills"
99
},
1010
"plugins": [
1111
{
1212
"name": "frontend",
1313
"source": "frontend",
14-
"description": "Cursor plugin for frontend engineering workflows \u2014 React, TypeScript, accessibility, and performance"
14+
"description": "Cursor plugin for frontend engineering workflows — React, TypeScript, accessibility, and performance"
1515
},
1616
{
1717
"name": "design",
1818
"source": "design",
19-
"description": "Cursor plugin for product design workflows \u2014 UX specs, design systems, handoff, and iteration"
19+
"description": "Cursor plugin for product design workflows — UX specs, design systems, handoff, and iteration"
2020
},
2121
{
2222
"name": "data-science",
2323
"source": "data-science",
24-
"description": "Cursor plugin for data science workflows \u2014 analysis, modeling, experimentation, and reporting"
24+
"description": "Cursor plugin for analyst-first data science workflows — exploratory analysis, validation, and decision-ready reporting"
2525
},
2626
{
2727
"name": "ios",
2828
"source": "ios",
29-
"description": "Cursor plugin for iOS development \u2014 Swift, SwiftUI, architecture, and testing"
29+
"description": "Cursor plugin for iOS development — Swift, SwiftUI, architecture, and testing"
3030
},
3131
{
3232
"name": "android",
3333
"source": "android",
34-
"description": "Cursor plugin for Android development \u2014 Kotlin, Jetpack Compose, architecture, and testing"
34+
"description": "Cursor plugin for Android development — Kotlin, Jetpack Compose, architecture, and testing"
3535
},
3636
{
3737
"name": "planning",
3838
"source": "planning",
39-
"description": "Cursor plugin for software planning \u2014 scope, milestones, risk management, and execution plans"
39+
"description": "Cursor plugin for software planning — scope, milestones, risk management, and execution plans"
4040
},
4141
{
4242
"name": "code-review",
4343
"source": "code-review",
44-
"description": "Cursor plugin for code review workflows \u2014 correctness, security, regressions, and actionable feedback"
44+
"description": "Cursor plugin for code review workflows — correctness, security, regressions, and actionable feedback"
4545
},
4646
{
4747
"name": "web-browser",
4848
"source": "web-browser",
49-
"description": "Cursor plugin for browser debugging workflows \u2014 DevTools, network traces, and reproducible bug reports"
50-
},
51-
{
52-
"name": "teaching",
53-
"source": "teaching",
54-
"description": "Cursor plugin for teaching workflows \u2014 explain concepts, scaffold exercises, and assess understanding"
49+
"description": "Cursor plugin for browser debugging workflows — DevTools, network traces, and reproducible bug reports"
5550
},
5651
{
5752
"name": "documentation",
5853
"source": "documentation",
59-
"description": "Cursor plugin for technical documentation workflows \u2014 READMEs, API docs, architecture notes, and changelogs"
54+
"description": "Cursor plugin for technical documentation workflows — READMEs, API docs, architecture notes, and changelogs"
6055
},
6156
{
6257
"name": "presentation-pptx",
6358
"source": "presentation-pptx",
64-
"description": "Cursor plugin for presentation authoring \u2014 narrative design, slide outlines, and PPTX-ready content"
59+
"description": "Cursor plugin for presentation authoring — narrative design, slide outlines, and PPTX-ready content"
6560
},
6661
{
6762
"name": "learning",
6863
"source": "learning",
69-
"description": "Cursor plugin for learning workflows \u2014 skill mapping, practice plans, and feedback loops"
64+
"description": "Cursor plugin for learning workflows — skill mapping, practice plans, and feedback loops"
7065
},
7166
{
7267
"name": "cursor-dev-kit",
7368
"source": "cursor-dev-kit",
74-
"description": "Cursor Dev Kit \u2014 internal-style workflows used by Cursor developers for CI, code review, shipping, and testing"
69+
"description": "Cursor Dev Kit — internal-style workflows used by Cursor developers for CI, code review, shipping, and testing"
70+
},
71+
{
72+
"name": "create-plugin",
73+
"source": "create-plugin",
74+
"description": "Meta plugin for creating Cursor plugins with manifest scaffolding, component templates, and submission checks"
7575
}
7676
]
7777
}

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ Official Cursor plugins for popular developer tools, frameworks, and SaaS produc
1414
| [Planning](planning/) | Utilities | Scope, milestones, risk management, and execution planning |
1515
| [Code Review](code-review/) | Developer Tools | Correctness, security, regression checks, and actionable feedback |
1616
| [Web Browser](web-browser/) | Developer Tools | DevTools-driven debugging, network traces, and repro workflows |
17-
| [Teaching](teaching/) | Utilities | Concept explanations, exercises, and understanding checks |
1817
| [Documentation](documentation/) | Utilities | READMEs, API docs, architecture notes, and changelog writing |
1918
| [Presentation PPTX](presentation-pptx/) | Utilities | Narrative design, slide outlines, and PPTX-ready content |
2019
| [Learning](learning/) | Utilities | Skill maps, practice plans, and feedback loops |
2120
| [Cursor Dev Kit](cursor-dev-kit/) | Developer Tools | Internal-style workflows for CI, code review, shipping, and testing |
21+
| [Create Plugin](create-plugin/) | Developer Tools | Meta workflows for creating Cursor plugins with scaffolding and submission checks |
2222

2323
## Repository Structure
2424

‎create-plugin/.cursor-plugin/plugin.json‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
{
2+
"name": "create-plugin",
3+
"version": "1.0.0",
4+
"description": "Meta plugin for authoring Cursor plugins with manifest scaffolding, component templates, and marketplace-ready checks",
5+
"author": {
6+
"name": "Cursor",
7+
"email": "plugins@cursor.com"
8+
},
9+
"homepage": "https://github.com/cursor/plugins",
10+
"repository": "https://github.com/cursor/plugins",
11+
"license": "MIT",
12+
"keywords": [
13+
"create-plugin",
14+
"cursor-plugin",
15+
"marketplace",
16+
"plugin-authoring"
17+
],
18+
"category": "developer-tools",
19+
"tags": [
20+
"meta",
21+
"authoring",
22+
"templates"
23+
],
24+
"skills": "./skills/",
25+
"rules": "./rules/",
26+
"agents": "./agents/",
27+
"commands": "./commands/"
28+
}

‎create-plugin/CHANGELOG.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Changelog
2+
3+
## 1.0.0
4+
5+
- Initial release of the `create-plugin` meta plugin.
6+
- Added scaffolding and submission-review skills for Cursor plugin authoring.
7+
- Added a plugin architecture agent, quality-gate rule, and `create-plugin` command.

‎create-plugin/LICENSE‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2026 Cursor
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

‎create-plugin/README.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Create Plugin Plugin
2+
3+
Meta workflows for creating Cursor plugins that are marketplace-ready.
4+
5+
## Installation
6+
7+
```bash
8+
agent install create-plugin
9+
```
10+
11+
## Components
12+
13+
### Skills
14+
15+
| Skill | Description |
16+
|:------|:------------|
17+
| `create-plugin-scaffold` | Scaffold a new plugin directory with manifest, components, and repository wiring |
18+
| `review-plugin-submission` | Run a pre-submission quality check against marketplace expectations |
19+
20+
### Rules
21+
22+
| Rule | Description |
23+
|:-----|:------------|
24+
| `plugin-quality-gates` | Keep plugin manifests, component metadata, and paths valid and consistent |
25+
26+
### Agents
27+
28+
| Agent | Description |
29+
|:------|:------------|
30+
| `plugin-architect` | Design plugin structure and component mix based on a concrete use case |
31+
32+
### Commands
33+
34+
| Command | Description |
35+
|:--------|:------------|
36+
| `create-plugin` | Build a new plugin scaffold with the right files and metadata |
37+
38+
## Typical Flow
39+
40+
1. Use `/create-plugin` with a plugin name, purpose, and target component types.
41+
2. Generate or update `plugin.json`, then add rules/skills/agents/commands as needed.
42+
3. Run `review-plugin-submission` before publishing or marketplace submission.
43+
44+
## License
45+
46+
MIT

‎create-plugin/agents/plugin-architect.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: plugin-architect
3+
description: Plugin architecture specialist. Use when deciding the right component mix, structure, and metadata for a new Cursor plugin.
4+
model: inherit
5+
readonly: true
6+
---
7+
8+
# Plugin Architect
9+
10+
Design focused, maintainable Cursor plugins with the smallest viable component set.
11+
12+
## Trigger
13+
14+
Use when planning a new plugin or refactoring an existing plugin's structure.
15+
16+
## Workflow
17+
18+
1. Clarify plugin goal, users, and expected outcomes.
19+
2. Recommend component mix (`rules`, `skills`, `agents`, `commands`, `hooks`, `mcpServers`) based on need.
20+
3. Propose directory layout and manifest shape.
21+
4. Flag potential discoverability or metadata issues early.
22+
5. Return a concrete implementation checklist.
23+
24+
## Output
25+
26+
- Recommended plugin architecture
27+
- Manifest and component decisions with rationale
28+
- Minimal implementation checklist

‎create-plugin/commands/create-plugin.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: create-plugin
3+
description: Scaffold a new Cursor plugin with manifest, component files, and marketplace wiring when needed
4+
---
5+
6+
# Create Plugin
7+
8+
Create a new plugin scaffold using this flow:
9+
10+
1. Gather inputs:
11+
- Plugin name (kebab-case)
12+
- Description and target users
13+
- Components to include (`rules`, `skills`, `agents`, `commands`, `hooks`, `mcpServers`)
14+
2. Create required files:
15+
- `.cursor-plugin/plugin.json`
16+
- `README.md`
17+
- `LICENSE`
18+
3. Add selected component folders and starter files with frontmatter.
19+
4. In multi-plugin repositories, update `.cursor-plugin/marketplace.json` with a new plugin entry.
20+
5. Return a summary of created files and any remaining manual setup.

‎create-plugin/rules/plugin-quality-gates.mdc‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
description: Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.
3+
alwaysApply: true
4+
---
5+
6+
# Plugin Quality Gates
7+
8+
When creating or editing Cursor plugins:
9+
10+
1. Ensure `.cursor-plugin/plugin.json` exists and includes a valid `name`.
11+
2. Keep paths relative and within the plugin directory (no absolute paths, no `..` traversal).
12+
3. Match declared component paths to real files and folders.
13+
4. Include YAML frontmatter for rules, skills, agents, and commands with required metadata.
14+
5. Keep plugin scope focused and document installation and usage in `README.md`.

‎create-plugin/skills/create-plugin-scaffold/SKILL.md‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: create-plugin-scaffold
3+
description: Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.
4+
---
5+
6+
# Create Plugin Scaffold
7+
8+
## Trigger
9+
10+
You need to create a new Cursor plugin from scratch and make it ready for local use or marketplace submission.
11+
12+
## Required Inputs
13+
14+
- Plugin name (lowercase kebab-case)
15+
- Plugin purpose and target users
16+
- Component set to include (`rules`, `skills`, `agents`, `commands`, `hooks`, `mcpServers`)
17+
- Repository style (`single-plugin` or `multi-plugin marketplace`)
18+
19+
## Workflow
20+
21+
1. Validate plugin name format: lowercase kebab-case, starts and ends with an alphanumeric character.
22+
2. Create base files:
23+
- `.cursor-plugin/plugin.json`
24+
- `README.md`
25+
- `LICENSE`
26+
- optional `CHANGELOG.md`
27+
3. Populate `plugin.json`:
28+
- Required: `name`
29+
- Recommended: `version`, `description`, `author`, `license`, `keywords`
30+
- Add explicit component paths only when non-default discovery is needed.
31+
4. Create component files with valid frontmatter:
32+
- Rules: `.mdc` with `description`, `alwaysApply`, optional `globs`
33+
- Skills: `skills/<skill-name>/SKILL.md` with `name`, `description`
34+
- Agents: `agents/*.md` with `name`, `description`
35+
- Commands: `commands/*.(md|txt)` with `name`, `description`
36+
5. If repository uses `.cursor-plugin/marketplace.json`, add plugin entry:
37+
- `name`
38+
- `source`
39+
- optional metadata (`description`, `keywords`, `category`, `tags`)
40+
6. Ensure all manifest paths are relative, valid, and do not use absolute paths or parent traversal.
41+
42+
## Guardrails
43+
44+
- Keep the plugin focused on one use case.
45+
- Prefer concise, actionable skill and rule text over long prose.
46+
- Do not reference files that do not exist.
47+
- Use folder discovery defaults unless custom paths are required.
48+
49+
## Output
50+
51+
- Created file tree for the plugin
52+
- Final `plugin.json`
53+
- Marketplace entry (if applicable)
54+
- Short validation report of required fields and component metadata

0 commit comments

Comments
 (0)