article-summarizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

核心規則

Core Rules

當使用者符合以下任一情況時，執行摘要流程：

僅貼上一個 URL，或訊息以摘要意圖為主並含 URL：使用環境提供的網頁抓取工具（例如
```
WebFetch
```
）取得該 URL 的可讀正文
直接貼上 Markdown 文章：直接使用貼上的內容

然後依下方翻譯、長度與呈現方式生成回覆。

Execute the summarization process when the user meets any of the following conditions:

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
Directly paste a Markdown article: Use the pasted content directly

Then generate the response based on the translation, length, and presentation methods below.

摘要長度

Summary Length

預設：保留約原文可讀字數的 50–70%（精簡但保留論證脈絡；不是「刪到剩 30%」）
使用者若要求「更短」「更詳細」等，後續回覆應配合調整

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

英文 → 全文脈絡以繁體中文表述（專有名詞規則見下）
簡體中文 → 繁體中文，用語貼近台灣習慣
其他語言（如日、韓等）→ 以繁體中文撰寫摘要；直接引述、專有名詞、書名等可保留原文
翻譯或重述時維持原文語氣、節奏與寫作風格（幽默、正式、口語、反諷等），並盡量呼應原文的段落結構與鋪陳方式，不要為了精簡而抹平成制式口吻
專有名詞保留英文原文，不硬翻：技術術語、產品／公司名、套件名、HTML/CSS/JS 等慣用英文詞等

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)

預設：以連貫段落為主輸出摘要或譯述，保留作者原本的排版感（分段、先後順序、輕重），不要用固定標題／一句話結論／全篇條列等範本硬套
列點：僅在使用者明確表示要列點、條列、重點整理、bullet 等時，才改為條列式；條列時仍盡量維持原作的語氣與用語選擇
來源：必要時可在開頭簡短註明 URL 或「使用者提供之全文」即可，不必規定獨立區塊格式
若需附上程式碼片段，仍依下方「程式碼處理」；程式碼區塊可穿插在相關段落之後，不必另立制式章節

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

使用者在同一段對話當中可能多次提供不同文章連結；各篇彼此無關時，不要把前一篇的上下文套用到當前這篇（不混用論點、不預設讀者還記得上一篇細節）。

Users may provide links to different articles multiple times within the same conversation; when the articles are unrelated to each other, do not apply the context of the previous article to the current one (do not mix arguments, do not assume the reader still remembers the details of the previous article)