Cursor IDE prompts, generated in 30 seconds.
Promptive writes prompts for Cursor Composer, Chat and Agent Mode. The master prompt includes the tech stack, folder tree, components, hooks, tests and a ready .cursorrules file. Pick your target model (Claude 3.5 Sonnet, GPT-4o, Gemini) — prompt structure adapts.
Cursor modes
- Composer (Cmd/Ctrl+I) — best for scaffolds and multi-file work
- Chat (Cmd/Ctrl+L) — single questions, small edits
- Agent Mode (Cmd/Ctrl+Shift+I) — autonomous multi-step actions
- .cursorrules — repo-level guidance applied to every request
How it works
- Open /new
- Pick "Cursor" as the target
- Describe the project: stack, style, features
- Receive a Markdown prompt + a ready .cursorrules
- Open Cursor Composer, paste, generate
FAQ
- How do I use Promptive prompts in Cursor?
- Copy the generated Markdown prompt and paste it into Cursor Composer (Cmd+I / Ctrl+I) or Chat (Cmd+L / Ctrl+L). Cursor Agent (Cmd+Shift+I) will act autonomously across multiple files.
- Which Cursor mode do you recommend?
- For a new project scaffold: Cursor Composer + a long Promptive prompt. For incremental changes: Chat + a shorter prompt. For multi-file edits: Agent Mode.
- Does it work with Claude 3.5 Sonnet in Cursor?
- Yes — Cursor lets you pick the model (Claude 3.5 Sonnet, GPT-4o, o1, Gemini 2.5 Pro). Promptive generates model-agnostic prompts, but you can pick the target model in the form.
- How is this different from writing a Cursor prompt manually?
- Cursor Composer works best when it receives a detailed prompt with tech stack, folder structure, design tokens, accessibility, tests. Writing that by hand takes 20–40 minutes. Promptive does it in 30 seconds.
- Does Promptive generate .cursorrules?
- Yes. The master prompt includes a .cursorrules section ready to drop into your repo — with TypeScript conventions, Tailwind config, testing patterns, commit style.
- How much does it cost?
- Free: 3/month. Pro: $9/mo (20 prompts). Max: $19/mo (100 prompts).