Cursor Prompt Generator

Cursor works best with a ticket-style prompt: a clear goal, the context it can't see, numbered requirements, constraints and acceptance criteria it can check its own work against.

Every prompt is built from the same modular parts — role, task, context (your audience and details) and output format — then rendered in the style each AI follows best. Change the AI in the drop-down and the same request is rewritten instantly.

• @-mention the files and folders the change touches so Cursor loads the right context.
• Save recurring constraints as Project Rules so you don't repeat them.
• Ask the agent to write a plan first, then implement it step by step.

Choose a prompt type for your task; each comes with an expert role, context rules and an output format:

• Web app — for example “a habit-tracker web app”.

Example output for Cursor:

You are a senior full-stack engineer who writes clean, secure, tested, production-ready code.

## Goal
Build a habit-tracker web app.

## Context
- Users: people building daily routines
- Stack and constraints: streaks, daily reminders, dark mode, data saved locally
- Default stack if not specified: React + Tailwind CSS

## Requirements
1. The core workflow, working end to end
2. Responsive layout for mobile and desktop
3. Form validation with helpful error messages
4. Empty, loading and error states

## Constraints
- Clean, modern and accessible (WCAG AA contrast, keyboard friendly).
- Don't change unrelated code or public interfaces without asking.
- Handle errors and edge cases; never hard-code secrets.
- Add or update tests for the new behaviour.

## Acceptance criteria
- Every requirement above works end to end.
- Tests pass and the linter is clean.
- Finish with a short summary of the changes and any trade-offs.

If anything essential is missing, ask me up to 3 short clarifying questions before you start.