***
### 6. Use Examples
Examples are one of the strongest ways to steer Claude’s tone, structure, and formatting. If the output needs to look a certain way, show Claude what “good” looks like.
**Tip:**
Use 3–5 short examples when consistency matters. Keep them high quality, clearly relevant, and aligned to the exact output you want.
<examples>
<example>
Input: Summarize this report for
executives.
Output: 3 short bullets, plain
language, no jargon.
</example>
<example>
Input: Summarize this issue update
for leadership.
Output: 3 bullets plus 1 risk
note, concise and factual.
</example>
</examples>
***
### 7. Use Claude’s “Thinking” Mode
Claude 4 can pause and reflect before giving its final output. This makes it especially strong for reviewing documents or complex reasoning.
**Prompt idea:**
```
After reading the report, reflect on the key themes before writing the summary. Double-check that the final version is clear, jargon-free, and under 300 words.
```
This approach works well for:
* Reviewing lengthy reports before drafting summaries
* Iterating on a first draft for clarity
* Comparing multiple sources and extracting common themes
***
### 8. Prompt Well for Long Documents
For long-context tasks, structure matters. Put long documents near the top, place the main question near the end, and tell Claude how to process the material.
* If you have multiple documents, label them clearly.
* Ask Claude to quote or extract the most relevant passages first when accuracy matters.
* Tell Claude exactly what to synthesize, compare, or prioritize
***
### 9. Run Through a Quick Checklist
Before sending your prompt, ask yourself:
* Did I specify the purpose, audience, workflow, and success criteria?
* Did I clearly state what to include and what to avoid?
* Did I break complex instructions into steps?
* Did I add quality modifiers (“concise,” “executive-ready,” etc.)?
* Do I want Claude to reflect before finalizing the output?
This five-second check can turn a weak summary into a strong one.
***
### 10. Task-Oriented Prompt Template
Use this when you need Claude to produce a clear, finished output.
```
Context: [Where this will be used, who the audience is]
Task: [Exactly what you want Claude to do; add modifiers like “executive-friendly,” “concise,” etc.]
Steps:
1. [Step one]
2. [Step two]
3. [Step three]
Constraints: [Tone, format, length, what to avoid]
Optional: Ask Claude to reflect and refine before finalizing
```
**Example:**
```
Context: Board presentation for executives with no technical background
Task: Summarize this 20-page market research report into 3 clear slides
Steps:
1. Identify the 3 most important findings
2. Remove all technical jargon
3. Keep each slide under 40 words
Constraints: Output only the 3 slides, no introduction or conclusion
```
***
### 11. Instruction and Reason Template
When formatting or rules matter, tell Claude the **reason**. It follows rules more reliably when it understands the “why.”
```
Task: Do not use ellipses (…) in your response
Reason: The text will be read aloud by a text-to-speech system, which cannot pronounce ellipses
```
This is useful for tone, formatting, or compliance requirements.
***
### 12) Step-by-Step Workflow Template
For multi-step work (like processing or transforming documents), give Claude a workflow.
```
Task: [Overall goal]
Instructions:
1. [Step one]
2. [Step two]
3. [Step three]
Final Output: [Exact format you want]
```
**Example:**
```
Task: Process customer survey responses for quarterly review
Instructions:
1. Anonymize all personal information (names, emails, phone numbers)
2. Extract the top 5 recurring themes
3. Summarize each theme in 2 sentences
Final Output: Show only the anonymized themes, formatted as bullet points
```
***
### 13) Prompt Templates by Use Case
**General Task Prompt**
```
Context: [Where this will be used and who the audience is].
Task: [Exactly what you want Claude to do; use verbs like “summarize,” “analyze,” or “draft”].
Instructions:
1. [Step one]
2. [Step two]
3. [Step three]
Constraints: [Tone, format, length, what to avoid].
Optional: Ask Claude to reflect or double-check reasoning before finalizing.
```
**Analyze a Dataset**
```
Context: Internal performance review meeting for Q3. Executives need clear, high-level insights from the dataset without technical details.
Task: Analyze this dataset and summarize 3–5 main insights for the management team.
Instructions:
1. Review the dataset carefully and note emerging trends or outliers.
2. Identify 3–5 findings that would matter most to business leaders.
3. Present the insights clearly in bullet form, followed by one recommendation section.
Constraints: Keep under 250 words. Avoid statistical jargon. Focus on clarity and business relevance. Do not infer or make baseless claims.
Optional: Reflect before writing — “Which of these insights most affect decision-making?”
```
**Summarize Emails and Recommend Next Steps**
Context: You’re creating a management summary from a long email thread between departments. It will be used to clarify alignment and next actions.
Task: Summarize the thread and list clear decisions and next steps.
Instructions:
1. Extract key discussion points and identify who said what.
2. Highlight confirmed decisions.
3. Suggest next steps with owners and deadlines.
4. Write one sentence summarizing the overall tone or urgency.
Constraints: Keep factual, under 200 words. Avoid assumptions or emotional tone.
Optional: Reflect before finishing — “Did I capture all the critical follow-ups?”
**Act as a Sales Assistant**
```
Context: You’re helping draft a follow-up message to a potential client after a demo. The message will be sent by the sales team.
Task: Write a personalized and professional follow-up email.
Instructions:
1. Open with a friendly acknowledgment of the demo.
2. Summarize 1–2 key benefits discussed, tailored to the client’s industry.
3. Include a clear call-to-action for next steps (e.g., a short call or proposal).
Constraints: Limit to 120 words. Keep tone warm but professional. Avoid pushiness or generic phrasing.
Optional: Reflect before sending — “Does this sound genuinely helpful, not salesy?”
```
***
### 14) Claude 4.6 Tips
1. **Control verbosity more deliberately:** Claude 4.6 is generally more concise, direct, and efficient than older Claude models. If you want status updates, summaries after tool calls, or more visible reasoning steps, ask for them explicitly.
2. **Guard against overengineering:** Claude Opus 4.6 can sometimes overbuild by adding extra files, abstractions, flexibility, or polish that was not requested. Add constraints like “keep the solution minimal” or “do not add extra structure unless required.”
3. **Be explicit when you want action, not suggestions:** Claude 4.6 may follow your wording literally. If you ask it to “suggest edits,” it may only propose changes.
4. **Use Positive Steering**: Tell Claude what to do rather than what not to do (e.g., "Use flowing prose" instead of "Do not use bullet points").
***
#### Final Tip
With Claude, **clarity beats cleverness**. Don’t just say “summarize”. Tell it how long, for whom, and in what format. That’s how you turn a 20-page report into something useful in minutes.
{% hint style="info" %}
Learn more about Claude Prompt Engineering in the [Claude Docs](https://docs.claude.com/en/docs/build-with-claude/prompt-engineering/overview)
{% endhint %}