First clicks
Cursor Docs
The official capability map for how Cursor wants to be used.
Why check it out: This is the official mental model for how Cursor wants to be used before community conventions start piling on.
First clicks
Start here
If you only want the shortest route to understanding how Cursor setups actually get shaped, start with the official surface plus the two main convention layers.
First clicks
awesome-cursorrules
📄 A curated list of awesome .cursorrules files.
Why check it out: Rules are where a lot of real Cursor behavior gets standardized in practice.
First clicks
awesome-cursor-skills
A curated list of practical Cursor-native skills and plugins.
Why check it out: Skills show the reusable workflow layer people add when rules alone are not enough.
Daily use
Most practical
These are the projects most likely to make a real setup better immediately, without requiring you to redesign your whole stack.
Daily use
specstory
SpecStory automatically saves every Cursor chat and composer session to your local project's .specstory directory.
Why check it out: Conversation capture becomes useful fast once Cursor work stops being disposable.
Daily use
context7
Context7 MCP Server -- Up-to-date documentation for LLMs and AI code editors.
Why check it out: Fresh docs/context retrieval solves a very common day-to-day failure mode.
Daily use
CursorLens
An open-source dashboard for Cursor.sh IDE. Log AI code generations, track usage, and control AI models (including local ones). Run locally or use upcoming hosted version.
Why check it out: Lightweight observability helps you understand what the editor is actually doing.
Bigger systems
Most ambitious
These point toward the branch where Cursor becomes part of a larger operating environment rather than just an editor tab.
Bigger systems
Cursor Marketplace
The official plugin and automation surface for extending Cursor.
Why check it out: This is the main official extension surface where the ecosystem starts compounding.
Bigger systems
MCP Docs
Official explanation of how Cursor plugs into outside tools through MCP.
Why check it out: MCP is the bridge from editor-native workflows into connected tools and services.
Bigger systems
Cloud Agent Docs
Official docs for Cursor's remote and cloud execution path.
Why check it out: Remote execution changes the shape of what Cursor can become inside a team workflow.
Interesting edges
Most weird
Not the first tools to install, but good examples of where the ecosystem starts getting more experimental or sideways.
Interesting edges
browser-tools-mcp
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Why check it out: A browser control bridge shows how far people push Cursor beyond plain code editing.
Interesting edges
curxy
Simple proxy worker for using ollama in cursor.
Why check it out: A proxy layer is a good signal that people are bending Cursor around model and traffic constraints.
Interesting edges
stagewise
stagewise is a browser toolbar that connects your frontend UI to your code ai agents in your code editor.
Why check it out: Bridging app runtime behavior back into the coding loop is a very specific but revealing direction.
Reusable patterns
Best for stealing ideas
These are good to browse when you want patterns you can remix into your own editor, extension, or team workflow.
Reusable patterns
agentskill.sh
Browse and install 44k+ skills for Cursor, Claude Code, Codex with security scanning. Use /learn command for one-click install.
Why check it out: A directory and distribution layer is useful even if you never copy its exact implementation.
Reusable patterns
smithery.ai
Smithery is a platform to help developers find and ship language model extensions compatible with the Model Context Protocol Specification.
Why check it out: Tool discovery and packaging patterns here generalize well beyond Cursor.
Reusable patterns
CLI Docs
Official docs for using Cursor through CLI and headless entry points.
Why check it out: CLI surfaces often reveal the cleanest separable abstractions in the product.