These prompts are designed for Cursor's actual features: the inline editor (Cmd+K), the chat panel (Cmd+L), @ references (files, docs, symbols), .cursorrules, and the composer for larger tasks. Where you'd paste your code or context, I've used {{clipboard}}. If you want to cover similar tasks. Since Cursor runs on Claude under the hood, you may also find our guide covers the differences in how you'd structure prompts for Copilot's completion-first approach.
Code Generation
23. Generate a CRUD API
Generate a complete CRUD API for this data model:
{{clipboard}}
Include: route definitions, controller functions, input validation (using the validation library in this project), database queries (using the ORM in this project), and error handling. Match the patterns in @[existing_controller].
24. Generate a React form
Generate a React form for this data model:
{{clipboard}}
Include: field validation (with error messages), loading state during submit, success/error feedback, and TypeScript types. Match the component patterns in this project.
25. Generate a database migration
Generate a database migration for this schema change:
{{clipboard}}
Include: the up migration, the down migration (rollback), and a comment explaining what this changes and why. Check for any data migration needs — not just schema changes.
Productivity & Meta-Prompts
26. Generate commit messages from staged changes
Write a conventional commit message for these changes:
{{clipboard}}
Format: type(scope): description. Body: explain WHY this change was made (not what). If it's a breaking change, add a footer.
27. Explain a decision for the team
Write a brief Slack/PR comment explaining this technical decision:
{{clipboard}}
Target audience: other engineers who didn't write this code. Cover: what was chosen, why this approach over alternatives, and any important caveats or follow-up work.
28. Write a TODO comment
Write a TODO comment for this incomplete or suboptimal code:
{{clipboard}}
The TODO should: explain what needs to be done, why it was left incomplete, what the desired end state is, and any context that will help whoever picks this up later.
29. Generate mock data
Generate mock data for this TypeScript type/interface:
{{clipboard}}
Create 5 realistic records. Use real-looking values — not "foo", "bar", "test1". Cover edge cases: include a record with optional fields missing, one with boundary values, and one with special characters where strings are involved.
30. Write a technical decision summary
We spent 2 hours deciding on this:
{{clipboard}}
Write a short decision summary (1 page) that captures: the problem, the options we evaluated, why we chose what we chose, and what we'd revisit if circumstances change. This will live in our docs.
Skills That Sync Beyond Cursor
Save these prompts as skills in Promptzy and they automatically stores them as Markdown and lets you paste any of them anywhere with Cmd+Shift+P. Since you're already working in Markdown all day, Promptzy's built-in Markdown editor with line numbers and search is a natural complement -- edit prompts and .md files in a distraction-free interface without leaving the app. For a detailed look at how this compares to other launchers, see
SOCIAL SHARE CARD GENERATOR