Claude Prompts
Official siteAnthropic's AI assistant excelling at nuanced writing, analysis, and long-context tasks.
Claude AI Prompt for Business Proposal Writing
Freelancers, agency owners, sales teams, and consultants use this prompt to draft winning client proposals in minutes instead of hours. It produces a complete, persuasive document structured around proven conversion principles rather than a generic template. The detailed role assignment and section-by-section guidance outperform a one-line prompt by ensuring client-focused language, quantified value, and a clear call to action — the elements that actually close deals. It also prompts Claude to gather missing context first, preventing vague, off-target output.
You are an expert business development consultant and proposal writer with 15+ years of experience winning competitive bids across industries including technology, professional services, marketing, and consulting. Your task is to write a persuasive, well-structured business proposal that converts prospects into clients. Before writing, ask me for any missing details, then incorporate the following information I provide: - My company name, services/products, and unique value proposition - The client/prospect name, industry, and their core problem or goal - Project scope, deliverables, and timeline - Pricing model and budget range - Any specific requirements, RFP criteria, or competitive context Structure the proposal with these sections: 1. **Executive Summary** — A compelling 150-word overview that frames the client's problem and positions our solution as the obvious choice. 2. **Understanding of Needs** — Demonstrate deep insight into the client's challenges, restating their pain points in their language. 3. **Proposed Solution** — Detail our approach, methodology, and deliverables with clear benefits tied to outcomes (not just features). 4. **Timeline & Milestones** — A phased breakdown with realistic dates. 5. **Pricing & Investment** — Present costs as value-justified investments, with tiered options if relevant. 6. **Why Choose Us** — Credibility builders: relevant experience, proof points, and differentiators. 7. **Next Steps & Call to Action** — A clear, low-friction path to approval. Tone requirements: confident but not arrogant, client-centric (use 'you' more than 'we'), professional yet warm, free of jargon and filler. Use short paragraphs, bullet points, and bold key phrases for scannability. Quantify benefits wherever possible (ROI, time saved, revenue gained). Format the output in clean Markdown ready to paste into a document. After the draft, suggest 3 ways to strengthen the proposal further. Keep total length between 800–1,200 words unless I specify otherwise.
Python Bug Hunter & Explainer
Debug any Python error with a clear explanation of root cause, fix, and prevention strategies — faster than Stack Overflow.
You are an expert Python debugger and educator. I have a bug in my code that I cannot figure out. Python version: [VERSION] Framework (if any): [DJANGO/FLASK/FASTAPI/etc.] Error message I'm seeing: ``` [PASTE ERROR MESSAGE HERE] ``` My code: ```python [PASTE YOUR CODE] ``` What I expected to happen: [DESCRIBE EXPECTED BEHAVIOR] What actually happens: [DESCRIBE ACTUAL BEHAVIOR] Please: 1. Identify the root cause (not just symptoms) 2. Explain WHY this causes the error 3. Show the corrected code 4. Explain what you changed and why 5. Suggest 2 ways I could have caught this bug earlier (better logging, type hints, tests)
Senior Code Reviewer Prompt
Get a thorough senior-level code review covering bugs, security, performance, and architecture — before pushing to production.
Act as a senior software engineer with 15 years of experience conducting code reviews. Review the following code with the same rigor you'd apply to production code at a top tech company. Language/Framework: [LANGUAGE] Code purpose: [WHAT IT DOES] [PASTE YOUR CODE] Review it for: 1. **Bugs & Logic Errors**: Anything that will break 2. **Security Vulnerabilities**: SQL injection, XSS, auth issues, etc. 3. **Performance**: N+1 queries, memory leaks, unnecessary loops 4. **Readability**: Naming, complexity, missing comments where needed 5. **Architecture**: Separation of concerns, SOLID principles 6. **Edge Cases**: What happens with null, empty, extreme inputs 7. **Testing**: What test cases are missing For each issue: severity (Critical/High/Medium/Low), explanation, and corrected code snippet.
Tips for Claude
Be Specific
The more detail you add — lighting, camera angle, style references — the better your results.
Test Variations
Small changes to wording can produce dramatically different outputs. Save prompts that work.
Use Negative Prompts
Excluding unwanted elements (blur, watermarks, cartoons) improves quality significantly.