mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
prune-plugin-catalog
Rename the learning plugin slug to teaching across marketplace metadata and docs, and add the reused data-science avatar to continuous-learning while preserving plugin validation. Co-authored-by: Cursor <cursoragent@cursor.com>
Cursor plugins
Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.
Plugins
| Plugin | Category | Description |
|---|---|---|
| Teaching | Utilities | Skill maps, practice plans, and feedback loops |
| Continuous Learning | Developer Tools | Incremental transcript-driven AGENTS.md memory updates with high-signal bullet points |
| Cursor Team Kit | Developer Tools | Internal-style workflows for CI, code review, shipping, and testing |
| Create Plugin | Developer Tools | Meta workflows for creating Cursor plugins with scaffolding and submission checks |
| Ralph Loop | Developer Tools | Iterative self-referential AI loops using the Ralph Wiggum technique |
Repository structure
This is a multi-plugin marketplace repository. The root .cursor-plugin/marketplace.json lists all plugins, and each plugin has its own manifest:
plugins/
├── .cursor-plugin/
│ └── marketplace.json # Marketplace manifest (lists all plugins)
├── plugin-name/
│ ├── .cursor-plugin/
│ │ └── plugin.json # Per-plugin manifest
│ ├── skills/ # Agent skills (SKILL.md with frontmatter)
│ ├── rules/ # Cursor rules (.mdc files)
│ ├── mcp.json # MCP server definitions
│ ├── README.md
│ ├── CHANGELOG.md
│ └── LICENSE
└── ...
License
MIT
Description
thermo-nuclear-code-quality-review: Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality…; unslop: Cut AI tells from any writing. Must always apply.; deslop: Remove AI-generated code slop and clean up code style; typescript-best-practices: TypeScript best practices. Use when reading or editing any .ts or .tsx file.; how: Use for "how does X work", code walkthroughs before changing something, an…
Languages
TypeScript
94.1%
JavaScript
2.6%
Shell
2.4%
CSS
0.8%