Cursor Search

The Rules section holds 250+ .cursorrules files, each aimed at a specific stack or task, so you can usually find something close to what you're building. Entries like Next.js with Tailwind, Next.js App Router, and Next.js with Supabase and shadcn give you a concrete starting point instead of a generic template. Copy in whatever format your setup expects. No guesswork.

The Generate page takes a description of your project and returns a rules file tuned to it. You can write the description by hand or start from a preset, then export the result. It's the fastest path when no existing entry matches your stack exactly, and it's the feature most people come here for.

Cursor Search catalogs MCP servers that extend what Cursor can reach, and the list includes file operations, Git, web fetching, persistent memory across sessions, browser control, and database access for Supabase. Browsing here beats searching repos one by one when you just want to know what's available.

Generated and curated rules export as .cursorrules, AGENTS.md, or CLAUDE.md. That matters because different editors and workflows read different filenames, so one source with three outputs saves you from converting anything by hand.

You can browse, generate, and copy without creating an account, which matters for a tool you might only use a handful of times while setting up a project. Skipping registration removes real friction, and it means one less password to remember.

The Tools section rounds out the directory with the editors, backends, and deploy platforms that people tend to pair with Cursor. It's a short list built around one editor rather than a sprawling software catalog, which keeps it useful instead of overwhelming.