Back to Details

english-proofreading

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

English Proofreading Skill

英文校对技能

Before answering the user's actual question, display a correction block that shows grammar fixes and natural native-speaker rephrasing of their English.
在回答用户的实际问题之前，先展示一个校对模块，其中包含对用户英文文本的语法修正和母语使用者的自然表述优化。

When to trigger

触发时机

Trigger whenever the user's message contains English prose — sentences, questions, or paragraphs — regardless of whether the rest of the message is in Korean. Skip only if the English content is limited to:
  • Single isolated words or short noun phrases (e.g., "React", "CI/CD pipeline")
  • Code, commands, or file paths
  • Proper nouns or brand names
当用户的消息中包含英文篇章内容（句子、问题或段落）时，无论消息其余部分是否为韩文，均触发该技能。仅在以下情况跳过校对：
  • 单个孤立单词或简短名词短语（例如："React", "CI/CD pipeline"）
  • 代码、命令或文件路径
  • 专有名词或品牌名称

Output format

输出格式

Always prepend the following block before the substantive answer. Use this exact structure:
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | {user's original English sentence(s)} |
| **Corrected** | {grammar-fixed version} |
| **Natural** | {how a native speaker would phrase it} |

💡 **Notes:** {brief explanation of key changes — 1–3 bullet points, in Korean}

---
Then continue with the normal answer below the horizontal rule.
务必在给出实质性回答之前添加以下模块。请严格使用此格式：
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | {用户的原始英文句子} |
| **Corrected** | {语法修正后的版本} |
| **Natural** | {母语使用者的自然表述} |

💡 **Notes:** {关键修改的简要说明——1-3个要点，用韩文撰写}

---
然后在水平分隔线下方继续给出正常回答。

Correction guidelines

校对准则

Corrected column

修正列

  • Fix grammar errors only: subject-verb agreement, tense, articles (a/an/the), prepositions, punctuation, word form (e.g., "informations" → "information").
  • Do not change the user's intended meaning or vocabulary choices.
  • If the original is grammatically correct, reproduce it as-is.
  • 仅修复语法错误：主谓一致、时态、冠词（a/an/the）、介词、标点、单词形式（例如："informations" → "information"）。
  • 不得更改用户的原意或词汇选择。
  • 如果原文语法正确，直接原样保留。

Natural column

自然表述列

  • Rewrite as a native English speaker would naturally say it.
  • Prefer common, idiomatic phrasing over literal translations.
  • You may restructure sentences, change vocabulary, or adjust register (formal/informal) to match the likely context.
  • If the corrected version is already fully natural, reproduce it as-is.
  • 按照母语使用者的习惯重新撰写。
  • 优先使用常见的惯用表达，而非直译。
  • 可根据可能的语境调整句子结构、替换词汇或调整语体（正式/非正式）。
  • 如果修正后的版本已经完全自然，直接原样保留。

Notes column (Korean)

说明列（韩文）

  • Explain only the most important changes in 1–3 bullet points.
  • Write in Korean. Keep each point to one concise sentence.
  • Focus on patterns the user is likely to encounter again (e.g., 관사 생략, 전치사 오용, 단수/복수 혼동).
  • If there are no errors and no naturalness improvements, write: "문법 오류 없음. 표현도 자연스럽습니다."
  • 仅用1-3个要点解释最重要的修改。
  • 用韩文撰写，每个要点保持简洁的一句话。
  • 聚焦用户可能再次遇到的语法模式（例如：관사 생략, 전치사 오용, 단수/복수 혼동）。
  • 如果没有错误且无需优化自然度，请写："문법 오류 없음. 표현도 자연스럽습니다."

Multi-sentence input

多句输入处理

If the user wrote multiple English sentences:
  • Treat them as a single block; show the full corrected and natural versions together (do not split into per-sentence rows).
  • The Notes column may reference specific sentences by quoting a short phrase.
如果用户输入了多个英文句子：
  • 将其视为一个整体；同时展示完整的修正版和自然表述版（不要拆分为逐句行）。
  • 说明列可通过引用短短语来指代特定句子。

Examples

示例

Example 1 — grammar error + unnatural phrasing

示例1 — 语法错误 + 表述不自然

User message:
"Can you explain me how does React hooks work?"
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | Can you explain me how does React hooks work? |
| **Corrected** | Can you explain to me how React hooks work? |
| **Natural** | Could you explain how React hooks work? |

💡 **Notes:**
- "explain me" → "explain to me": explain은 간접목적어 앞에 to가 필요합니다.
- 간접의문문에서는 어순이 평서문과 같아야 합니다 ("how does" → "how").

---
用户消息：
"Can you explain me how does React hooks work?"
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | Can you explain me how does React hooks work? |
| **Corrected** | Can you explain to me how React hooks work? |
| **Natural** | Could you explain how React hooks work? |

💡 **Notes:**
- "explain me" → "explain to me": explain은 간접목적어 앞에 to가 필요합니다.
- 간접의문문에서는 어순이 평서문과 같아야 합니다 ("how does" → "how").

---

Example 2 — correct but unnatural

示例2 — 语法正确但表述不自然

User message:
"I want to know the difference of var and let."
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | I want to know the difference of var and let. |
| **Corrected** | I want to know the difference between var and let. |
| **Natural** | What's the difference between var and let? |

💡 **Notes:**
- "difference of" → "difference between": 두 대상을 비교할 때는 between을 씁니다.

---
用户消息：
"I want to know the difference of var and let."
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | I want to know the difference of var and let. |
| **Corrected** | I want to know the difference between var and let. |
| **Natural** | What's the difference between var and let? |

💡 **Notes:**
- "difference of" → "difference between": 두 대상을 비교할 때는 between을 씁니다.

---

Example 3 — no errors

示例3 — 无错误

User message:
"What are the benefits of using TypeScript over JavaScript?"
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | What are the benefits of using TypeScript over JavaScript? |
| **Corrected** | What are the benefits of using TypeScript over JavaScript? |
| **Natural** | What are the benefits of using TypeScript over JavaScript? |

💡 **Notes:** 문법 오류 없음. 표현도 자연스럽습니다.

---
用户消息：
"What are the benefits of using TypeScript over JavaScript?"
markdown
---
✏️ **English Proofreading**

| | Text |
|---|---|
| **Original** | What are the benefits of using TypeScript over JavaScript? |
| **Corrected** | What are the benefits of using TypeScript over JavaScript? |
| **Natural** | What are the benefits of using TypeScript over JavaScript? |

💡 **Notes:** 문법 오류 없음. 표현도 자연스럽습니다.

---

Edge cases

边缘情况处理

  • Mixed Korean + English: Extract only the English portion for the correction block. Do not alter or translate the Korean parts.
  • Very long input: Correct all English prose but keep the Notes concise; do not list every minor fix.
  • Intentional style (e.g., informal slang): Preserve in the Natural column if the context clearly calls for it; note the stylistic choice in Notes.
  • Code-heavy messages: Skip proofreading if the only English is inside code fences or inline code spans.
  • 韩文+英文混合内容：仅提取英文部分用于校对模块，不要修改或翻译韩文内容。
  • 超长输入：校对所有英文篇章内容，但保持说明简洁；无需列出每一处细微修改。
  • 刻意风格（例如：非正式俚语）：如果语境明确需要，在自然表述列保留该风格；并在说明列注明此风格选择。
  • 代码密集型消息：如果仅有的英文内容位于代码块或行内代码中，跳过校对。