**Use this when you want the agent to draft your persistent project instructions:**
"Help me write a system prompt file for this project.
Tool target: [Cursor / Claude Code / both]
Project summary: [what the app does]
Stack: [frameworks, languages, key services]
Repo conventions: [folders, naming, testing, styling, data access]
Constraints: [things the agent must never do]
Current phase: [what is already built and what is in progress]
Return:
1. A concise `.cursorrules` or `CLAUDE.md`
2. A short list of rules I should not include because they are too vague, too stale, or too noisy
3. A maintenance checklist for keeping this file current as the project changes."System Prompts — .cursorrules and CLAUDE.md Explained
Write system prompts that give AI persistent context about your project and preferences.
Prompt FAQ
Questions to answer before you paste it
When should I use the System Prompts — .cursorrules and CLAUDE.md Explained prompt?
Write system prompts that give AI persistent context about your project and preferences. Use it when you need a safer starting point than a blank prompt and you want the agent to stay inside explicit constraints.
Should I paste this prompt exactly as written?
No. Treat it as a safe starter. Replace the task, files, constraints, and verification details with your actual context before you run it.
What should I do after the agent answers?
Read the diff, run the checks, and stop after one reviewable step. If you need deeper context, open the lesson that explains the reasoning behind the prompt.
Related prompts worth copying next
Bolt.new and Lovable — Instant Full-Stack Apps
Build complete web applications from a text prompt with Bolt.new and Lovable.
Open prompt pageBreaking Big Ideas into Small Tasks — The Decomposition Pattern
Learn why small, focused prompts produce better code than trying to build everything at once.
Open prompt pageChain-of-Thought — Making AI Think Step by Step
Use chain-of-thought prompting to get AI to reason through complex coding problems.
Open prompt page