Claude Prompt Templates

<context>
I'm designing the architecture for a new project and need expert guidance.
</context>

<project_requirements>
- Type: [web app / mobile app / API / library / etc.]
- Scale: [expected users/requests]
- Key Features: [list main features]
- Constraints: [budget, team size, timeline, existing systems]
</project_requirements>

<task>
Please provide architectural recommendations:

1. **Proposed Architecture** - High-level system design
2. **Technology Stack** - Languages, frameworks, databases, and why
3. **Key Design Decisions** - Trade-offs and reasoning
4. **Potential Challenges** - Risks and mitigation strategies
5. **Scalability Plan** - How to grow the system
</task>

<task>
Help me implement this feature: [FEATURE DESCRIPTION]
</task>

<context>
- Project Type: [e.g., Next.js web app]
- Existing Stack: [technologies in use]
- Relevant Files: [key files involved]
</context>

<requirements>
- [Specific requirement 1]
- [Specific requirement 2]
- [Specific requirement 3]
</requirements>

<output_format>
1. Implementation approach overview
2. Step-by-step implementation with code
3. Testing recommendations
4. Edge cases to consider
</output_format>

<role>
You are a security expert reviewing code for vulnerabilities.
</role>

<code_to_review>
```
[PASTE YOUR CODE HERE]
```
</code_to_review>

<review_checklist>
Check for:
- Injection attacks (SQL, XSS, command injection)
- Authentication/authorization flaws
- Sensitive data exposure
- Input validation issues
- Cryptography weaknesses
- Error handling that leaks information
- Dependency vulnerabilities
</review_checklist>

<output>
For each vulnerability found:
1. Location in code
2. Severity (Critical/High/Medium/Low)
3. Attack scenario
4. Recommended fix with code example
</output>

<document>
[PASTE DOCUMENT OR DESCRIBE IT]
</document>

<analysis_request>
Analyze this document and provide:

1. **Executive Summary** (3-5 sentences)
2. **Key Points** - Main arguments or findings
3. **Critical Analysis**
   - Strengths of the content
   - Potential weaknesses or gaps
   - Assumptions made
4. **Implications** - What does this mean for [CONTEXT]?
5. **Questions Raised** - What remains unclear or needs follow-up?
</analysis_request>

<argument>
[PASTE THE ARGUMENT OR CLAIM TO EVALUATE]
</argument>

<evaluation_criteria>
Evaluate this argument considering:

1. **Logical Structure**
   - Is the reasoning valid?
   - Are there logical fallacies?

2. **Evidence Quality**
   - What evidence is provided?
   - Is the evidence reliable and relevant?

3. **Assumptions**
   - What assumptions are made?
   - Are they reasonable?

4. **Counter-arguments**
   - What are the strongest objections?
   - How well does the argument address them?

5. **Conclusion**
   - Overall strength rating (1-10)
   - What would make this argument stronger?
</evaluation_criteria>

<scenario>
[DESCRIBE THE ETHICAL DILEMMA OR DECISION]
</scenario>

<stakeholders>
Who is affected: [LIST STAKEHOLDERS]
</stakeholders>

<analysis_framework>
Analyze from multiple ethical perspectives:

1. **Consequentialist View**
   - What are the likely outcomes?
   - Who benefits/suffers?

2. **Deontological View**
   - What duties or rights are involved?
   - Are any being violated?

3. **Virtue Ethics**
   - What would a person of good character do?
   - What virtues are relevant?

4. **Practical Considerations**
   - Legal implications
   - Precedent effects

5. **Balanced Recommendation**
   - Suggested course of action with reasoning
</analysis_framework>

<subject>
Topic to document: [YOUR SUBJECT]
</subject>

<audience>
Who will read this: [TECHNICAL LEVEL AND ROLE]
</audience>

<documentation_requirements>
Create technical documentation including:

1. **Overview** - What is it and why use it?
2. **Prerequisites** - What's needed to get started
3. **Quick Start** - Minimal steps to basic usage
4. **Detailed Guide** - In-depth explanation with examples
5. **API Reference** (if applicable) - Parameters, returns, examples
6. **Troubleshooting** - Common issues and solutions
7. **Best Practices** - Recommended patterns

Use code examples where appropriate.
</documentation_requirements>

<proposal_context>
Purpose: [What you're proposing]
Audience: [Who will approve this]
Constraints: [Budget, timeline, resources]
</proposal_context>

<proposal_structure>
Draft a proposal with:

1. **Executive Summary** - Key points in 1 paragraph
2. **Problem Statement** - What issue are we solving?
3. **Proposed Solution** - What are we doing?
4. **Approach** - How will we do it?
5. **Expected Outcomes** - What will success look like?
6. **Resources Required** - What do we need?
7. **Timeline** - Key milestones
8. **Risks & Mitigation** - What could go wrong?
9. **Call to Action** - What do you need from them?

Tone: Professional, confident, evidence-based
</proposal_structure>

<learning_topic>
I want to understand: [TOPIC]
</learning_topic>

<current_knowledge>
What I already know: [YOUR CURRENT UNDERSTANDING]
</current_knowledge>

<instruction>
Act as a Socratic tutor. Instead of explaining directly:
1. Ask me guiding questions that help me discover the answer
2. Respond to my answers with follow-up questions
3. If I'm stuck, provide hints rather than answers
4. Only explain directly if I'm completely lost
5. Help me build understanding from first principles

Start with your first question.
</instruction>

<concept>
Explain: [CONCEPT]
</concept>

<audience_levels>
Explain this concept for four different audiences:

**1. A 10-year-old**
- Use simple words and familiar analogies
- Focus on the core idea only

**2. A high school student**
- Add more detail and proper terminology
- Include real-world examples

**3. A college undergraduate**
- Include technical details
- Discuss edge cases and nuances

**4. An expert peer**
- Assume full background knowledge
- Discuss cutting-edge developments and open questions
</audience_levels>