@@ -0,0 +1,24 @@
+{
+  "name": "cursor-plugin-starters",
+  "owner": {
+    "name": "Your Org",
+    "email": "plugins@example.com"
+  },
+  "metadata": {
+    "description": "Starter marketplace template for Cursor plugins",
+    "version": "0.1.0",
+    "pluginRoot": "plugins"
+  },
+  "plugins": [
+    {
+      "name": "starter-simple",
+      "source": "./plugins/starter-simple",
+      "description": "Minimal plugin with rules and skills only"
+    },
+    {
+      "name": "starter-advanced",
+      "source": "./plugins/starter-advanced",
+      "description": "Full-featured plugin with rules, skills, agents, commands, hooks, and MCP"
+    }
+  ]
+}
@@ -0,0 +1 @@
+plans/
@@ -0,0 +1,14 @@
+# Environment and secrets
+.env
+.env.*
+!.env.example
+
+# OS and editor
+.DS_Store
+*.swp
+*.swo
+
+# Logs and temp
+*.log
+tmp/
+temp/
@@ -0,0 +1,34 @@
+# Cursor plugin template
+
+Build and publish Cursor Marketplace plugins from a single repo.
+
+Two starter plugins are included:
+
+- **starter-simple**: rules and skills only
+- **starter-advanced**: rules, skills, agents, commands, hooks, MCP, and scripts
+
+## Getting started
+
+[Use this template](https://github.com/cursor/plugin-template/generate) to create a new repository, then customize:
+
+1. `.cursor-plugin/marketplace.json`: set marketplace `name`, `owner`, and `metadata`.
+2. `plugins/*/.cursor-plugin/plugin.json`: set `name` (lowercase kebab-case), `displayName`, `author`, `description`, `keywords`, `license`, and `version`.
+3. Replace placeholder rules, skills, agents, commands, hooks, scripts, and logos.
+
+To add more plugins, see `docs/add-a-plugin.md`.
+
+## Single plugin vs multi-plugin
+
+This template defaults to **multi-plugin** (multiple plugins in one repo).
+
+For a **single plugin**, move your plugin folder contents to the repository root, keep one `.cursor-plugin/plugin.json`, and remove `.cursor-plugin/marketplace.json`.
+
+## Submission checklist
+
+- Each plugin has a valid `.cursor-plugin/plugin.json`.
+- Plugin names are unique, lowercase, and kebab-case.
+- `.cursor-plugin/marketplace.json` entries map to real plugin folders.
+- All frontmatter metadata is present in rule, skill, agent, and command files.
+- Logos are committed and referenced with relative paths.
+- `node scripts/validate-template.mjs` passes.
+- Repository link is ready for submission to the Cursor team (Slack or `kniparko@anysphere.com`).
@@ -0,0 +1,75 @@
+# Add a plugin
+
+Add a new plugin under `plugins/` and register it in `.cursor-plugin/marketplace.json`.
+
+## 1. Create plugin directory
+
+Create a new folder:
+
+```text
+plugins/my-new-plugin/
+```
+
+Add the required manifest:
+
+```text
+plugins/my-new-plugin/.cursor-plugin/plugin.json
+```
+
+Example manifest:
+
+```json
+{
+  "name": "my-new-plugin",
+  "displayName": "My New Plugin",
+  "version": "0.1.0",
+  "description": "Describe what this plugin does",
+  "author": {
+    "name": "Your Org"
+  },
+  "logo": "assets/logo.svg"
+}
+```
+
+## 2. Add plugin components
+
+Add only the components you need:
+
+- `rules/` with `.mdc` files (YAML frontmatter required)
+- `skills/<skill-name>/SKILL.md` (YAML frontmatter required)
+- `agents/*.md` (YAML frontmatter required)
+- `commands/*.(md|mdc|markdown|txt)` (frontmatter recommended)
+- `hooks/hooks.json` and `scripts/*` for automation hooks
+- `mcp.json` for MCP server definitions
+- `assets/logo.svg` for marketplace display
+
+## 3. Register in marketplace manifest
+
+Edit `.cursor-plugin/marketplace.json` and append a new entry:
+
+```json
+{
+  "name": "my-new-plugin",
+  "source": "./plugins/my-new-plugin",
+  "description": "Describe your plugin"
+}
+```
+
+`source` is the relative path from the repository root to the plugin folder.
+
+## 4. Validate
+
+```bash
+node scripts/validate-template.mjs
+```
+
+Fix all reported errors before committing.
+
+## 5. Common pitfalls
+
+- Plugin `name` not kebab-case.
+- `source` path in marketplace manifest does not match folder name.
+- Missing `.cursor-plugin/plugin.json` in plugin folder.
+- Missing frontmatter keys (`name`, `description`) in skills, agents, or commands.
+- Rule files missing frontmatter `description`.
+- Broken relative paths for `logo`, `hooks`, or `mcpServers` in manifest files.
@@ -0,0 +1,13 @@
+{
+  "name": "starter-advanced",
+  "displayName": "Advanced Starter",
+  "version": "0.1.0",
+  "description": "Full-featured Cursor plugin starter with rules, skills, agents, commands, hooks, and MCP.",
+  "author": {
+    "name": "Your Org",
+    "email": "plugins@example.com"
+  },
+  "license": "MIT",
+  "keywords": ["cursor", "plugin", "rules", "skills", "agents", "commands", "hooks", "mcp"],
+  "logo": "assets/logo.svg"
+}
@@ -0,0 +1,13 @@
+# starter-advanced
+
+Full-featured Cursor plugin starter.
+
+## Included
+
+- `rules/`: coding standards and review checklist
+- `skills/code-reviewer/`: code review skill
+- `agents/`: security reviewer agent
+- `commands/`: deploy-staging command
+- `hooks/hooks.json`: hook definitions
+- `scripts/`: hook script placeholders
+- `mcp.json`: MCP server config
@@ -0,0 +1,16 @@
+---
+name: security-reviewer
+description: Security-focused reviewer that checks for common vulnerabilities and unsafe defaults.
+---
+
+# Security reviewer
+
+You are a security-focused reviewer. Prioritize concrete, high-impact findings.
+
+## Review focus
+
+1. Injection risks in SQL, shell commands, and rendered HTML content.
+2. Sensitive data handling (tokens, credentials, personal data).
+3. Authentication and authorization checks on privileged operations.
+4. Safe defaults in configuration and network-facing behavior.
+5. Dependency and supply-chain hygiene where relevant.
@@ -0,0 +1,11 @@
+---
+name: deploy-staging
+description: Deploy the current branch to the staging environment after validation.
+---
+
+# Deploy to staging
+
+1. Run project validation checks and tests.
+2. Build artifacts for the target environment.
+3. Publish or deploy to staging.
+4. Run smoke checks and report status.