This guide assumes you've used Claude before. If you're new, start with the Claude beginner guide first.
TECHNIQUE 1: SYSTEM PROMPTS (THE BIGGEST UPGRADE)
A system prompt tells Claude who it is before the conversation starts. In Claude Projects, this is the "Project Instructions" field. In the API, it's the system parameter.
Example system prompt for a writing assistant: "You are a direct-response copywriter specialising in B2B SaaS. You write in a clear, confident, no-jargon style. You always ask for the audience and the desired action before writing copy. When reviewing drafts, you lead with what's working before suggesting improvements. You never use the word 'delve'."
The more specific your system prompt, the better Claude performs on repeated tasks.
TECHNIQUE 2: EXPLOITING THE LONG CONTEXT WINDOW
Claude's 200K token context window is its biggest differentiator. Use it:
- Paste entire codebases: "Here is my entire project. Identify the most likely source of the performance issues I'm seeing."
- Upload full books: "Here is a 300-page business book. Summarise the 20 most actionable insights."
- Analyse long threads: Paste entire email chains, Slack threads, or support tickets.
- Compare documents: "Here are two contracts. Identify every clause where they differ and flag anything unusual."
TECHNIQUE 3: CHAIN OF THOUGHT
For complex reasoning, ask Claude to think step by step before answering:
"Before answering, think through this problem step by step. Show your reasoning, then give your conclusion: [PROBLEM]"
Or: "Work through this decision methodically. First identify all the relevant factors, then weigh them, then give a recommendation: [DECISION]"
TECHNIQUE 4: STRUCTURED OUTPUT
When you need data in a specific format:
"Return your response as a JSON object with these fields: name, description, pros (array), cons (array), rating (1-10)."
"Format your output as a markdown table with columns: Tool | Use Case | Price | Rating"
"Give me a numbered list of exactly 10 items. Each item: bold title, then a one-sentence description."
TECHNIQUE 5: ROLE + EXPERTISE STACKING
Stack multiple roles for complex analysis:
"You are simultaneously: a seasoned CFO reviewing for financial risk, a lawyer reviewing for legal exposure, and a customer success manager reviewing for customer impact. Review this policy change from all three perspectives simultaneously."
TECHNIQUE 6: ADVERSARIAL REVIEW
Use Claude to steelman the opposing view:
"Here's my business plan: [PASTE]. Now argue against it as a skeptical investor who has seen many similar plans fail. Be specific and harsh."
"Here's the decision I'm leaning toward: [DECISION]. Give me the strongest possible case for the opposite choice."
TECHNIQUE 7: ITERATIVE REFINEMENT
Instead of re-prompting from scratch, iterate:
First draft: "Write a first draft of [CONTENT]. Focus on getting the ideas out. Don't worry about polish." Refine: "Keep the structure but make it 40% shorter and more direct." Final: "Final pass: fix any awkward sentences and make the opening line more compelling."
TECHNIQUE 8: CUSTOM FORMATTING RULES
Tell Claude exactly how to format every response in your project:
"When I ask you to review writing, always structure your feedback as: STRENGTHS (3 bullet points), IMPROVEMENTS (3 specific suggestions with examples), PRIORITY (which one change would make the biggest difference)."
Downloaded from DavideGPT.ai — Follow @DavideGPT for daily AI tips