The art of prompting
with Claude Code

You are a senior React/Next.js/TypeScript developer.

Create a React component that [COMPONENT DESCRIPTION].

Technical context:
- Framework: Next.js 14 (App Router)
- Language: TypeScript (strict mode)
- Styling: Tailwind CSS
- State management: [zustand / React Context / none]

Functional specifications:
- [Feature 1]
- [Feature 2]
- [Feature 3]

Constraints:
- Responsive mobile-first
- Accessible (ARIA, focus management)
- Performance optimized (memo, lazy loading if needed)
- Error handling and loading states

Generate the complete code with:
1. The main component
2. TypeScript types/interfaces
3. A usage example
4. Unit tests (Vitest + Testing Library)

You are a senior technical writer.

Write the technical documentation for [PROJECT/MODULE NAME].

Target audience: [junior developers / internal team / open-source]

Expected structure:
1. Overview (2-3 sentences)
2. Installation and prerequisites
3. Configuration
4. Quick Start guide
5. API Reference (each function with parameters, return, example)
6. Advanced usage examples
7. FAQ and troubleshooting

Conventions:
- Code examples in [TypeScript/Python/etc.]
- All snippets must be copyable and functional
- Use admonitions (note, warning, tip) when relevant
- Include a navigable table of contents at the beginning

You are a senior DevOps/SRE engineer.

Create a script that automates [TASK DESCRIPTION].

Environment:
- OS: [Linux/macOS/Windows]
- Language: [Bash/Python/Node.js]
- Available tools: [Docker, GitHub Actions, etc.]

Expected behavior:
1. [Step 1 of the process]
2. [Step 2 of the process]
3. [Step 3 of the process]

Requirements:
- Robust error handling (exit codes, try/catch)
- Logging with levels (info, warn, error)
- Dry-run mode for testing without executing
- Configurable variables via .env or CLI arguments
- Idempotent (can be re-run without side effects)

Generate:
1. The complete commented script
2. The .env.example file
3. The usage README
4. A cron/schedule example if relevant

You are a senior data analyst expert in Python.

Analyze this CSV dataset and [ANALYSIS OBJECTIVE].

Data information:
- Source: [source description]
- Main columns: [col1, col2, col3, ...]
- Volume: [approximate number of rows]
- Period: [time range of data]

Requested analysis:
1. Exploration: descriptive statistics, missing values, distributions
2. Cleaning: outlier handling, normalization, encoding
3. Analysis: [correlations / trends / segmentation / prediction]
4. Visualization: relevant charts with matplotlib/seaborn

Output format:
- Complete Python code (pandas, numpy, matplotlib)
- Comments explaining each step
- Interpretation of results in non-technical language
- Recommendations based on insights

You are a senior web writer specializing in [DOMAIN].

Write a blog post about [TOPIC].

Parameters:
- Tone: [professional / casual / educational]
- Length: [800-1200 words]
- Target audience: [typical reader description]
- Objective: [inform / persuade / tutorial]

Structure:
1. Catchy title (max 60 characters)
2. Introduction with hook (problem/question)
3. 3-5 sections with H2 subheadings
4. Concrete examples and data
5. Conclusion with call-to-action

SEO:
- Main keyword: [keyword]
- Secondary keywords: [keyword-2, keyword-3]
- Meta description (max 155 characters)
- Internal link suggestions

Constraints:
- No unnecessary jargon
- Short sentences (max 20 words)
- One paragraph = one idea
- Include bullet lists for readability

# Etape 1 : Analyse
"Analyse ce codebase et identifie les problemes de performance.
Liste chaque probleme avec : fichier, ligne, severite, description."

# Etape 2 : Priorisation (utilise la sortie de l'etape 1)
"A partir de cette liste de problemes, cree un plan d'action priorise.
Criteres : impact utilisateur, complexite de correction, risque de regression."

# Etape 3 : Implementation (utilise la sortie de l'etape 2)
"Implemente la correction du probleme #1 : [description].
Genere le code corrige, les tests de non-regression, et un benchmark avant/apres."

# Etape 4 : Validation
"Revois les corrections appliquees. Verifie qu'elles ne cassent rien
et que les tests passent. Suggere des ameliorations supplementaires si pertinent."

# Dans votre CLAUDE.md, definissez des agents specialises :

## Agents disponibles

| Agent          | Role                        | Quand l'utiliser              |
|----------------|-----------------------------|-------------------------------|
| planner        | Planification               | Avant toute feature complexe  |
| tdd-guide      | Test-Driven Development     | Nouvelles features, bug fixes |
| code-reviewer  | Revue de code               | Apres chaque implementation   |
| security-check | Analyse de securite         | Avant chaque commit           |
| architect      | Decisions d'architecture    | Choix techniques importants   |
# Exemple d'utilisation dans un prompt :

"Utilise l'agent planner pour decomposer cette feature en taches.
Puis lance en parallele :
- Agent 1 (tdd-guide) : ecrit les tests pour le module auth
- Agent 2 (tdd-guide) : ecrit les tests pour le module API
- Agent 3 (security-check) : analyse les implications securite

Une fois les tests ecrits, implemente le code pour les faire passer."

# Workflow complet : nouvelle feature du planning a la production

## Phase 1 : Recherche et planification
"Recherche les implementations existantes de [feature] sur GitHub.
Evalue les 3 meilleures options selon : securite, extensibilite, pertinence.
Genere un plan d'implementation detaille avec phases et risques."

## Phase 2 : TDD (Test-Driven Development)
"En suivant le plan, ecris d'abord les tests (RED).
Pour chaque module :
1. Ecris le test → verifie qu'il echoue
2. Ecris l'implementation minimale → verifie qu'il passe (GREEN)
3. Refactorise → verifie que tout passe toujours (REFACTOR)"

## Phase 3 : Revue et securite
"Lance en parallele :
- Code review : qualite, patterns, maintenabilite
- Security review : injections, auth, secrets, XSS
- Performance review : N+1, memory leaks, bundle size
Corrige les issues CRITICAL et HIGH avant de continuer."

## Phase 4 : Integration et deploiement
"Cree la PR avec un resume complet des changements.
Verifie que le CI passe. Deploie en staging pour validation."