Bible Network Crypto DeFi Onchain RWA AI Agent Stablecoin Chain SAFU CryptoTax DeFAI AGI Claude Me Claude Skill Claude Design Claude Cowork
Independent Media
Not affiliated with any project
Let Claude Do the Work, Not Just Answer
claudecowork-me.com
LATEST
Recruitment Screening Workflow: Using Claude to Compress Two Days of Resume Screening Into Half a Day  ·  Claude × Google Calendar: Let AI See the Full Picture of Your Schedule — From Being Driven by Your Calendar to Actively Owning Your Time  ·  Claude Workplace Features in 2026: MCP Matures, Memory Deepens — Time to Upgrade How You Work  ·  Performance Self-Review Scene: Why You Never Know How to Write It Each Year — and How Claude Helps You Make Your Results Visible  ·  Difficult Conversation Email Scene: Bad News, Apologies, Refusals — Let Claude Help You Find That Hardest-to-Master Tone  ·  Building a Personal Knowledge Management System with Claude: Stop Letting What You Read Disappear
Glossary · prompt-techniques

Output Format

prompt-techniques 新手

30-Second Version · For the impatient
Explicitly telling Claude in your prompt what your answer should look like — including format (bullets, table, paragraph), length (word count, point caps), and structure (which sections to include). This is the single biggest variable affecting how immediately usable Claude's output is. More specific specification = more directly usable output.
Full Explanation +
01 · What is this?

How do I decide which output format to use? Is there a decision logic?

Output format choice fundamentally depends on where this output will ultimately go and who will read it. Here's a simple decision matrix:

Pasting into email or messaging → Paragraph. Email readers expect flowing text; sudden bullet lists can feel impersonal or overly formal.

Pasting into presentation slides → Bullet points. One sentence per point, verb-first, visually scannable.

Comparing options or making decisions → Table. Comparing three approaches' pros and cons, contrasting two options' metrics — tables make differences immediately visible.

Instructing someone to follow steps → Numbered list. Sequential steps need numbering so recipients know what order to follow.

Quick read, key points for a busy manager → Executive summary format: 3–5 bullet points, 1–2 sentences each.

Formal external report or proposal → Paragraph with H3 headings. Headings let readers navigate quickly; paragraphs let content breathe completely.

A useful thinking question: 'After I review this output, how much reformatting work does it need before I can use it?' If the answer is '10 minutes of restructuring,' your format specification needs to be more precise.

02 · Why does it exist?

I wrote 'please be concise' in my prompt but Claude still gave me a very long response. Why?

'Please be concise' is the most commonly misused output format instruction, because 'concise' means different things to different people. For you, concise might be 100 words; for Claude, concise might be 500 words — default assumptions may differ by 5x.

The fix: replace subjective adjectives with objective numbers

❌ Unclear instructions:

  • 'Please be concise'
  • 'Please keep it short'
  • 'Just tell me the key points'
  • 'Don't make it too long'

✅ Clear instructions:

  • 'Max 3 key points, one sentence each'
  • 'Under 150 words'
  • 'One paragraph, no more than 5 sentences'
  • 'Summarize this decision in one sentence'

Another common issue: you said 'concise,' but your question itself implies a need for a long answer (e.g., 'please comprehensively analyze the opportunities and challenges in this market'). Claude can't fully satisfy both 'be concise' and 'comprehensive analysis' simultaneously — it typically leans toward meeting the question's stated scope. If you genuinely need a short version, explicitly say 'just the single most important point' or 'summarize the key conclusion in two sentences.'

03 · How does it affect your decisions?

Can I request 'don't use a specific format' at the same time as specifying a format?

Absolutely — and this is often more effective than 'use format X' alone, because it eliminates Claude's most likely default tendencies. Common negative format instructions:

'Don't use bullet points — write in complete paragraphs': When faced with multi-point tasks, Claude defaults to bullet points. If you need flowing, readable paragraphs (for an article or email), explicitly saying 'no bullets' is very effective.

'No intro paragraph — start directly with content': Claude frequently adds an intro before the actual answer ('Here is my analysis of this question...'). If you don't want this, say 'no intro, start directly with the first point.'

'No closing summary': If your output will be directly edited for use, Claude's closing summary paragraph is unnecessary overhead. 'No closing summary' keeps output cleaner.

'No bold' or 'no Markdown formatting at all': If you're pasting output into a platform that doesn't support Markdown (some CRM systems, SMS), say 'plain text output, no formatting symbols.'

Negative and positive format instructions can and often should be combined for output that truly meets your needs: 'use paragraphs, no bullets; no intro; max 200 words' — these three together are far more precise than any one alone.

04 · What should you do?

If I want Claude to output according to a fixed template, what's the best approach?

Method 1: Include the template directly in your prompt (most straightforward) In your prompt, say: 'Please output in the following template format, replacing the [placeholder] parts with the corresponding content:

[Client Name] Weekly Summary — [Date]

This week's highlights:
- [Point 1]
- [Point 2]
- [Point 3]

Next week's plan: [Next week's focus]

Support needed: [If any; otherwise write "None"]

'

When you give Claude the template structure directly, output almost perfectly follows that structure.

Method 2: Show Claude a good example (most natural) Say 'Please organize this new data using the format and style of the following report: [attach example report].' Claude automatically learns the example's structure without you specifying each element.

Method 3: Put the template in the System Prompt (lowest ongoing effort, best for long-term reuse) If you'll use this template repeatedly, put it in the Claude Projects System Prompt. After that, whenever you request output in that Project, just say 'please use our standard format' and Claude automatically applies your pre-configured template.

Real-World Example +

Ms. Xu is a content editor at a tech media company. Every week she needs to condense a 3,000-word market research report into three different versions: a one-page executive summary for management (bullets, under 100 words), an article introduction for readers (paragraph, 200 words), and social media posts (3 tweets, each under 280 characters).

First attempt: paste the report into Claude and ask 'please help me create several versions of this report.' Claude gave her one version that sat somewhere between her three needs — not fully meeting any of them, requiring separate revision for each.

Adjusted approach: she designed three separate prompts, each with explicit output format specifications:

Version 1 (executive summary): 'Please condense the following report into a one-page executive summary for senior management. Format: bullet points, max 5 points, one sentence each, verb-first. Total under 100 words. No intro — start directly with the first point.'

Version 2 (article introduction): 'Please rewrite the following report as an article opening paragraph. Format: pure paragraphs, no bullets. Length: under 200 words, 3–4 sentences. Tone: spark reader curiosity, raise the report's core question — don't give conclusions (conclusions come later in the article).'

Version 3 (social posts): 'Please rewrite the core insights from the following report as 3 tweets. Each tweet: under 280 characters, independently readable (not dependent on the others), opens with a data point or counterintuitive observation. No hashtags.'

These three specified prompts reduced her time from report to three finished formats from 45 minutes to under 10 minutes, with each version immediately usable without significant editing.

Diagram
輸出格式三個維度:格式 × 長度 × 結構以三欄圖展示輸出格式指定的三個核心維度,每個維度的常用選項,以及如何根據使用情境選擇最適合的格式組合。Output Format — 3 Dimensions to Specify① FormatWhat shape is the output?Bullet pointsBest for: slides, quick scan, action itemsParagraph (narrative)Best for: emails, reports, client-facingTableBest for: comparisons, multi-variable dataNumbered listBest for: steps, ranked options, proceduresQ&A / FAQ formatBest for: briefing docs, onboarding materialPrompt example:"Output as a table with 3 columns"② LengthHow much output?Point/item count cap"Max 5 bullet points" "3–5 items"Word / character count"Under 200 words" "100–150 characters"Per-item length"Each point: one sentence only"Relative length signal"Executive summary level" "Tweet length"Prompt example:"Max 5 points, 1 sentence each"③ StructureWhich sections, in what order?"First X, then Y, finally Z""Separate section for risks""End with action items""No intro paragraph, start with content""Use these exact headings: [A] [B] [C]"Prompt example:"3 sections: summary / risks / next steps"Combined example: "5 bullet points · one sentence each · sections: problem / solution / risk"Specify all 3 dimensions → output is immediately usable, no reformatting neededClaude Cowork Me · claudecowork-me.com
Feel free to share. Please credit the source.
Common Misconceptions +
✕ Misconception 1
× Misconception 1: Format specification is just about 'aesthetics' — if the content is right, format doesn't matter. Format specification affects not just aesthetics but output usability. The same content as a 500-word paragraph requires time to break down into a usable form; the same content as five bullet points you need can be pasted directly. Well-formatted output brings downstream usage time close to zero; poorly formatted output needs 5–15 minutes of restructuring. In high-frequency workflows, this time difference is significant.
✕ Misconception 2
× Misconception 2: Once you specify a format, Claude will always fully comply. Claude generally follows format requirements well, but with very long or complex tasks, it may 'forget' format specifications mid-output — especially length limits (it may start following them but gradually produce more). If output length matters to you, state it at the prompt start and reinforce at the end: 'Reminder: total output must not exceed 5 points, one sentence each.' Follow-up instructions also work: 'Output is too long — compress to within 5 key points.'
The Missing Link +
Direct Impact

The core trade-off: control vs. flexibility.

The more specific your format specification, the more control you have over output — but also the less flexibility Claude has. Extremely rigid format constraints (e.g., 'must be a table, three columns, max 20 words per cell') may prevent Claude from fully expressing content that would be better served by paragraphs.

The other trade-off is upfront format design time vs. usage time saved. Designing good format instructions requires first thinking through 'how will this output be used' — itself taking a few minutes of upfront thinking. For one-off tasks, this investment may not be worth it; for recurring tasks, a well-designed format instruction can be reused indefinitely with very high ROI.

Best practice: for repetitive tasks, specify format to the precision you need; for exploratory conversations, let Claude choose format freely, then use follow-up instructions for adjustments ('change format to bullet points').

Ask a Question
Please enter at least 10 characters
More Related Topics