PROMPTS.md explained
What is PROMPTS.md?
PROMPTS.md is a Markdown file that collects reusable AI prompts and prompt patterns so a team can reuse what works instead of rewriting prompts each time.
PROMPTS.md meaning
`PROMPTS.md` is a project file that stores prompts your team uses with AI tools: code review prompts, refactor instructions, documentation generators, test writers, and more. Instead of everyone crafting prompts from scratch, the best versions live in one Markdown file that is shared and version controlled.
What to put in PROMPTS.md
- Named, reusable prompts grouped by task
- Short notes on when to use each prompt
- Placeholders for inputs the user fills in
- Examples of good and bad outputs
- Links to related AGENTS.md or CLAUDE.md rules
# Prompts
## Code review
Review this diff for bugs, edge cases, and clarity.
Return findings as a short list.
## Write tests
Write unit tests for {file}. Cover edge cases. Why centralize prompts
- Consistency: everyone uses the prompt that works
- Quality: refine prompts in one place over time
- Onboarding: new team members reuse proven patterns
- Version control: prompt changes are reviewable like code
PROMPTS.md and AI workflows
As teams rely more on AI tools, prompts become shared assets, much like code snippets. A PROMPTS.md keeps that knowledge from living only in chat histories. It pairs well with a clear set of agent instruction files that tell the AI how your project works. For more on AI Markdown workflows, see how to use Markdown files with AI.
Edit PROMPTS.md with a preview
Draft and organize prompts in the Markdown Docs online editor, or download Markdown Docs to edit PROMPTS.md on Windows. See more common .md files for AI projects.
Related references
- Markdown Docs: how to use Markdown with AI related AI Markdown workflows.
FAQ
Is PROMPTS.md an official standard?
No. It is a practical convention for storing reusable AI prompts in a project, not an official specification.
What should I store in PROMPTS.md?
Named, reusable prompts grouped by task, with notes on when to use each and placeholders for inputs.
Why keep prompts in version control?
So prompt improvements are shared, reviewable, and consistent across the team instead of trapped in individual chat histories.
How is PROMPTS.md different from AGENTS.md?
AGENTS.md tells an agent how to work in the project. PROMPTS.md stores reusable prompts people send to AI tools.