article-summarizer

Core Rules

1. Only paste one URL, or the message focuses on summarization intent and includes a URL: Use the web scraping tool provided by the environment (such as

   WebFetch

   ) to obtain the readable body text of the URL
2. Directly paste a Markdown article: Use the pasted content directly

Summary Length

• Default: Retain approximately 50–70% of the readable word count of the original text (concise but retains the argument context; not "cut down to 30%")
• If the user requests "shorter", "more detailed", etc., subsequent responses should be adjusted accordingly

Translation and Language

• English → Present the full context in Traditional Chinese (see below for proper noun rules)
• Simplified Chinese → Traditional Chinese, using terms close to Taiwanese usage
• Other languages (such as Japanese, Korean, etc.) → Write the summary in Traditional Chinese; direct quotes, proper nouns, book titles, etc., can retain the original text
• Maintain the original text's tone, rhythm, and writing style (humorous, formal, colloquial, ironic, etc.) when translating or paraphrasing, and try to echo the original paragraph structure and presentation style. Do not flatten it into a standard tone for the sake of conciseness
• Retain the original English for proper nouns, do not force translation: technical terms, product/company names, package names, commonly used English terms such as HTML/CSS/JS, etc.

Presentation Method (No Mandatory Template)

• Default: Output the summary or paraphrase mainly in coherent paragraphs, retaining the author's original layout feel (paragraph breaks, order, emphasis). Do not force-fit fixed templates such as fixed titles, one-sentence conclusions, or full bullet points
• Bullet Points: Only switch to bullet points when the user clearly requests bullet points, itemization, key points sorting, bullets, etc.; when itemizing, still try to maintain the original author's tone and term choices
• Source: If necessary, briefly note the URL or "full text provided by the user" at the beginning; there is no need to specify an independent block format
• If code snippets need to be included, follow the "Code Handling" below; code blocks can be inserted after relevant paragraphs, and there is no need to create a separate standard section

Code Handling

• If the article contains code examples, include fragments directly related to the explanation when summarizing
• Do not translate the code, keep it as is
• The selected fragments should echo the summary text to help understand the core concept

Parallel Multiple Articles