How to Use Claude for Writing

Write a comprehensive article on {{topic}} for {{publication_type}}.

**Audience:** {{target_audience}}
**Word count:** {{word_count}} words
**Tone:** {{tone}} (e.g., authoritative but accessible, conversational, academic)

Structure:
1. Hook — Open with a compelling anecdote, surprising statistic, or provocative question
2. Context — Why this topic matters right now
3. Main argument — {{main_thesis}} supported by evidence and examples
4. Counterarguments — Address the strongest objection honestly
5. Practical takeaways — What the reader should do with this information
6. Closing — Circle back to the opening hook with a new perspective

Writing rules:
- Active voice, concrete nouns, strong verbs
- One idea per paragraph
- Use subheadings every 200-300 words
- Include at least 2 specific examples or case studies
- No filler phrases ("In today's fast-paced world", "It's important to note")

Edit the following draft for {{editing_focus}}:

---
{{draft_text}}
---

Editing instructions:
1. **Clarity** — Rewrite any sentence that requires more than one read to understand
2. **Conciseness** — Cut filler words, redundant phrases, and unnecessary qualifiers. Target a {{percentage}}% reduction in word count
3. **Flow** — Ensure each paragraph transitions logically to the next
4. **Voice** — Maintain the author's voice — do not make it sound like AI wrote it
5. **Fact flags** — Mark any claims that should be verified with [VERIFY: reason]

Return the edited version with:
- Track-changes style: show deletions in ~~strikethrough~~ and additions in **bold**
- A summary of the top 5 most impactful changes you made and why
- One suggestion for structural reorganization (if applicable)

Here is a sample of writing whose style I want you to match:

---
{{writing_sample}}
---

Analyze this writing style along these dimensions:
- Sentence length and rhythm (short/punchy, long/flowing, mixed)
- Vocabulary level (simple, technical, literary)
- Use of metaphor and figurative language
- Paragraph structure and length
- How the author handles transitions
- Distinctive quirks or patterns

Now write {{content_description}} in this exact style. The topic is {{topic}}.

Important: Match the STYLE, not the content or opinions. The new piece should sound like the same author wrote it but on a completely different subject.

I have research from multiple sources on {{research_topic}}. Synthesize them into a coherent narrative.

**Source 1:** {{source_1_summary}}
**Source 2:** {{source_2_summary}}
**Source 3:** {{source_3_summary}}
{{additional_sources}}

Write a {{output_type}} that:
1. Identifies the key themes that appear across multiple sources
2. Notes where sources agree and where they contradict each other
3. Highlights the strongest evidence and most compelling arguments from any source
4. Identifies gaps — what questions do these sources leave unanswered?
5. Synthesizes a balanced conclusion that accounts for the full evidence base

Do NOT just summarize each source sequentially. Organize by theme, weaving sources together. Cite sources by number (Source 1, Source 2, etc.) inline.

Write a {{fiction_type}} ({{word_count}} words) with these elements:

**Setting:** {{setting}}
**Main character:** {{character_description}}
**Central conflict:** {{conflict}}
**Tone/mood:** {{tone}}
**Theme (subtle, not stated):** {{theme}}

Writing guidelines:
- Show, don't tell — convey emotion through action and dialogue, not narration
- Open in media res — start in the middle of something happening
- Use sensory details (at least 3 senses per scene)
- Dialogue should reveal character — each person should sound distinct
- End with resonance, not resolution — leave the reader thinking
- No cliches: avoid "a chill ran down their spine," "little did they know," "the silence was deafening"

Write the complete piece, not an outline or a first chapter.

Write technical documentation for {{subject}} targeting {{audience_level}} developers.

**What it does:** {{description}}
**Key concepts they need to understand:** {{concepts}}

Document structure:
1. **Quick Start** — Get something working in under 5 minutes (show the minimal viable example)
2. **Core Concepts** — Explain the mental model. Use diagrams described in text if helpful
3. **API Reference** — Every public method/endpoint with parameters, return values, and examples
4. **Common Patterns** — The 3-5 most common use cases with complete code examples
5. **Troubleshooting** — The 5 most common errors and how to fix them
6. **Migration Guide** — If upgrading from {{previous_version}}, what changed and how to update

Writing rules:
- Lead with code, follow with explanation (developers read code first)
- Every code example must be complete and runnable — no "..." or "// add your code here"
- Use second person ("you") not third person ("the developer")
- Keep sentences under 25 words
- Bold key terms on first use