Add Example Prompts to CLAUDE.md So Your Team Gets Consistent Results

Every team discovers their own "best prompts" through trial and error. Instead of keeping that knowledge in people's heads, put it in CLAUDE.md where everyone benefits.

<!-- In your CLAUDE.md -->

When working on this project, here are the best ways to ask for common tasks:

**Adding a new API endpoint:**
"Create a new API endpoint for [resource]. Follow the pattern in 
UserController — use a Form Request for validation, an API Resource 
for the response, and add a feature test."

**Fixing a bug:**
"Read the failing test at [path], understand what it expects, 
find why the code doesn't match, and fix it. Run the test after."

**Adding a database change:**
"Create a migration for [change]. Update the model with relationships 
and casts. Update the factory. Run migrate and test."

Claude reads these examples and applies them when developers make similar requests — even if they phrase it differently. The examples establish the workflow, not just the code style.

This is different from other CLAUDE.md patterns:

• Domain glossary — defines what terms mean
• Persona — controls how Claude communicates
• Scoped rules — sets constraints per directory
• Example prompts — shows Claude how to approach common tasks

Useful examples to include:

**Code review checklist:**
"When reviewing code, check: error handling, input validation, 
SQL injection, proper authorization, test coverage, and naming 
conventions. Report issues by severity."

**Creating a new feature:**
"Always create in this order: migration, model, controller, 
routes, form request, API resource, then tests. Run tests 
after each file."

**Debugging workflow:**
"When debugging, first reproduce the issue with a failing test. 
Then fix the code. Never modify the test to make it pass — 
fix the implementation."

New team members immediately get the benefit of the team's accumulated prompt-engineering knowledge. No onboarding sessions needed — the patterns are right there in the project.

The best prompts shouldn't live in one developer's memory — put them in CLAUDE.md so the whole team gets consistent, high-quality results.

via Claude Code