Back to Details

academic-writing-style

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Academic Writing Style

学术写作风格

Transform provided information into well-written academic assignments that match the user's natural writing style, avoiding obvious AI patterns while maintaining professional quality.
将提供的信息转化为撰写精良的学术作业，匹配用户自然的写作风格，在保持专业质量的同时避免明显的AI生成痕迹。

Core Approach

核心方法

Generate content that reads naturally and fluently, with:
  • Clear chapter organization using descriptive headings
  • Natural topic progression without rigid "firstly...secondly...finally" structures
  • Moderate use of first-person perspective appropriate to assignment type
  • Specific examples and details rather than generic statements
  • Mixed sentence lengths without excessive complexity
  • Proper punctuation for target language (Chinese or English)
生成自然流畅的内容，具备以下特点：
  • 使用描述性标题构建清晰的章节结构
  • 自然的主题推进，避免刻板的“首先...其次...最后”结构
  • 根据作业类型适度使用第一人称视角
  • 采用具体示例和细节，而非泛泛之谈
  • 混合不同长度的句子，避免过度复杂
  • 符合目标语言（中文或英文）的正确标点规范

Before Writing

写作前准备

  1. Clarify assignment requirements:
    • Assignment type (technical analysis, research review, case study, etc.)
    • Target language (Chinese, English, or both)
    • Expected length or scope
    • Specific topics or concepts to cover
    • Any special requirements
  2. Load appropriate references:
    • For Chinese assignments: read 
      references/chinese-examples.md
    • For English assignments: read 
      references/english-examples.md
    • Always read 
      references/writing-guidelines.md
      for core principles
  3. Assess personalization level:
    • Technical analyses: More objective, minimal first-person
    • Research reviews: Moderate personal voice
    • Case studies: Higher personalization appropriate with reflections
  1. 明确作业要求：
    • 作业类型（技术分析、研究综述、案例研究等）
    • 目标语言（中文、英文或双语）
    • 预期篇幅或范围
    • 需要涵盖的特定主题或概念
    • 任何特殊要求
  2. 加载合适的参考资料：
    • 中文作业：阅读 
      references/chinese-examples.md
    • 英文作业：阅读 
      references/english-examples.md
    • 始终阅读 
      references/writing-guidelines.md
      以遵循核心原则
  3. 评估个性化程度：
    • 技术分析：更客观，尽量少用第一人称
    • 研究综述：适度加入个人观点
    • 案例研究：可适当提高个性化程度，加入反思内容

Writing Process

写作流程

Structure Development

结构搭建

Create descriptive chapter headings that preview content rather than generic labels:
  • Instead of "Introduction" → "Docker and the Container Revolution: A Practical Perspective"
  • Instead of "Analysis" → "从繁琐到简洁：Spring Boot如何改变Java开发"
  • Instead of "Conclusion" → "Migrating a Production Database: Lessons from a Zero-Downtime PostgreSQL Switch"
Organize content by natural topic flow, allowing chapters to build on each other through content connections rather than explicit transitions.
创建能够预览内容的描述性章节标题，而非通用标签：
  • 不用“引言” → 改用“Docker与容器革命：实践视角”
  • 不用“分析” → 改用“从繁琐到简洁：Spring Boot如何改变Java开发”
  • 不用“结论” → 改用“迁移生产数据库：PostgreSQL零停机切换的经验教训”
按照自然的主题流组织内容，通过内容关联实现章节间的递进，而非依赖显式过渡语句。

Paragraph Construction

段落构建

Integrate information into flowing paragraphs instead of lists. When information naturally forms a list, embed it in prose:
Avoid: The key advantages include:
  • Performance improvement
  • Cost reduction
  • Scalability enhancement
Prefer: The optimization brought three main benefits: performance improved significantly with response times dropping by 60%, costs decreased through more efficient resource usage, and the architecture gained better scalability for future growth.
将信息整合为流畅的段落，而非列表形式。当信息自然适合列表时，将其嵌入文本中：
避免： 主要优势包括：
  • 性能提升
  • 成本降低
  • 可扩展性增强
推荐： 此次优化带来了三大主要益处：性能显著提升，响应时间缩短60%；通过更高效的资源利用降低了成本；架构获得了更好的可扩展性，以支持未来增长。

Transitions and Flow

过渡与流畅性

Connect paragraphs through:
  • Topic extension: Last concept of previous paragraph continues in next
  • Natural contrast: Present contrasting ideas without heavy transition words
  • Implicit questions: Address unstated questions the content raises
  • Chapter breaks: Use chapter divisions to signal major topic shifts
Avoid mechanical transitions like "however", "furthermore", "in addition" in favor of letting content flow naturally.
通过以下方式连接段落：
  • 主题延伸： 前一段的最后一个概念在后一段继续展开
  • 自然对比： 呈现对比观点，无需使用生硬的过渡词
  • 隐含问题： 回应内容引发的未明确提出的问题
  • 章节划分： 用章节分隔来标志主要主题的转变
避免使用“然而”“此外”“另外”等机械过渡词，让内容自然流畅地衔接。

Incorporating Examples and Details

融入示例与细节

Make writing concrete through:
  • Specific metrics: "response time dropped from 8 seconds to 2 seconds"
  • Real cases: "Netflix split their monolith into hundreds of microservices over several years"
  • Technical details: "the query involved 7 table joins and generated N+1 query problems"
  • Personal observations: "in my experience, this approach works well for..." (use sparingly)
通过以下方式让写作更具体：
  • 具体指标：“响应时间从8秒降至2秒”
  • 真实案例：“Netflix在数年内将其单体应用拆分为数百个微服务”
  • 技术细节：“该查询涉及7张表连接，产生了N+1查询问题”
  • 个人观察：“根据我的经验，这种方法在...场景下效果良好”（谨慎使用）

Language Calibration

语言校准

For Chinese writing:
  • Use proper Chinese punctuation: ，。：""
  • Keep technical terms in English where appropriate: "Spring Boot", "Docker"
  • Maintain natural Chinese sentence rhythm and flow
  • Avoid direct English-to-Chinese translation patterns
For English writing (IELTS 6.0 level):
  • Prefer common over complex vocabulary: "use" instead of "utilize"
  • Keep sentences under 30 words typically
  • Use clear, direct constructions
  • Define acronyms on first use: "Object-Relational Mapping (ORM)"
  • Mix sentence lengths for readability
中文写作：
  • 使用正确的中文标点：，。：""
  • 适当保留英文技术术语：“Spring Boot”“Docker”
  • 保持自然的中文语句节奏与流畅度
  • 避免直接的英中直译模式
英文写作（IELTS 6.0水平）：
  • 优先使用常用词汇而非复杂词汇：用“use”代替“utilize”
  • 通常将句子长度控制在30词以内
  • 使用清晰、直接的句式
  • 首次使用缩写时进行定义：“Object-Relational Mapping (ORM)”
  • 混合句子长度以提升可读性

First-Person Usage

第一人称使用

Use first-person perspective strategically:
  • Describing practical experience: "笔者在项目中遇到过..." / "from my experience..."
  • Expressing informed opinions: "我认为..." / "I found that..."
  • Case study reflections: "如果重新设计，我会..." / "looking back, I would..."
Maintain objectivity for:
  • Technical explanations of principles
  • Literature review content
  • Pure technical analysis
策略性地使用第一人称视角：
  • 描述实践经验：“笔者在项目中遇到过...” / “from my experience...”
  • 表达有依据的观点：“我认为...” / “I found that...”
  • 案例研究反思：“如果重新设计，我会...” / “looking back, I would...”
在以下场景保持客观性：
  • 原理的技术解释
  • 文献综述内容
  • 纯技术分析

Quality Verification

质量验证

Before finalizing, verify:
  • No "firstly...secondly...finally" structures present
  • Minimal use of bullet points (only when absolutely necessary)
  • Paragraphs connect naturally through content
  • Specific examples and details included throughout
  • Chapter headings are descriptive and informative
  • First-person usage is appropriate and not excessive
  • Punctuation matches target language conventions
  • Sentence variety present (mix of long and short)
  • Language avoids obvious AI markers
  • Technical terminology used accurately and consistently
定稿前，验证以下内容：
  • 不存在“首先...其次...最后”结构
  • 尽量少用项目符号（仅在绝对必要时使用）
  • 段落通过内容自然衔接
  • 通篇融入具体示例与细节
  • 章节标题具有描述性且信息丰富
  • 第一人称使用恰当不过度
  • 标点符合目标语言规范
  • 句子类型多样（长短句混合）
  • 语言避免明显的AI生成痕迹
  • 技术术语使用准确且一致

Special Considerations

特殊注意事项

For bilingual assignments (both Chinese and English versions needed):
  • Write each version independently, not as direct translation
  • Adapt examples and phrasing to each language's natural patterns
  • Maintain consistent technical accuracy across both versions
  • Adjust formality level appropriately for each language context
For technical analysis:
  • Reduce personal voice, increase objectivity
  • Focus on technical accuracy and detailed explanation
  • Use concrete examples from real systems or projects
  • Balance accessibility with technical precision
For research reviews:
  • Synthesize sources into narrative rather than listing them
  • Show connections and evolution of ideas
  • Acknowledge debates and different perspectives
  • Maintain critical but balanced tone
For case studies:
  • Provide rich contextual details
  • Include specific challenges encountered
  • Reflect on lessons learned (appropriate place for first-person)
  • Balance description with analysis
双语作业（需要中英文两个版本）：
  • 独立撰写每个版本，而非直接翻译
  • 根据每种语言的自然模式调整示例与措辞
  • 确保两个版本的技术准确性一致
  • 根据每种语言的语境适当调整正式程度
技术分析：
  • 减少个人观点，增加客观性
  • 注重技术准确性与详细解释
  • 使用来自真实系统或项目的具体示例
  • 在易读性与技术精准度间取得平衡
研究综述：
  • 将来源整合为叙述性内容，而非简单罗列
  • 展示观点间的关联与演变
  • 认可不同观点与争议
  • 保持批判性但平衡的语气
案例研究：
  • 提供丰富的背景细节
  • 包含遇到的具体挑战
  • 反思获得的经验教训（适合使用第一人称的场景）
  • 在描述与分析间取得平衡

File Output Convention

文件输出规范

Output Directory Convention

输出目录规范

Recommended Approach (Following Claude Code Official Standards):
Save all academic writing outputs to 
outputs/<project-name>/writing/
:
outputs/
└── <project-name>/              # Project name (e.g., cloud-computing-analysis)
    └── writing/
        ├── technical-analysis.md    # Technical analysis report
        ├── research-review.md       # Research review document
        ├── case-study.md            # Case study report
        └── project-documentation.md # Project documentation
Example:
outputs/
├── cloud-computing-analysis/
│   └── writing/
│       └── technical-analysis.md
├── ai-ethics-research/
│   └── writing/
│       └── research-review.md
└── database-optimization-case/
    └── writing/
        └── case-study.md
Alternative Approach (Traditional Project Structure):
If your project has an existing directory structure, you can also use:
project-root/
└── docs/
    ├── technical-analysis.md
    ├── research-review.md
    └── case-study.md
推荐方案（遵循Claude Code官方标准）：
将所有学术写作输出保存至 
outputs/<project-name>/writing/
：
outputs/
└── <project-name>/              # 项目名称（例如：cloud-computing-analysis）
    └── writing/
        ├── technical-analysis.md    # 技术分析报告
        ├── research-review.md       # 研究综述文档
        ├── case-study.md            # 案例研究报告
        └── project-documentation.md # 项目文档
示例：
outputs/
├── cloud-computing-analysis/
│   └── writing/
│       └── technical-analysis.md
├── ai-ethics-research/
│   └── writing/
│       └── research-review.md
└── database-optimization-case/
    └── writing/
        └── case-study.md
替代方案（传统项目结构）：
如果项目已有现有目录结构，也可使用：
project-root/
└── docs/
    ├── technical-analysis.md
    ├── research-review.md
    └── case-study.md

Output File List

输出文件列表

Generate documents based on assignment type:
Technical Analysis:
  • technical-analysis.md
    - Technical analysis report
Research Review:
  • research-review.md
    - Research review document
Case Study:
  • case-study.md
    - Case study report
Project Documentation:
  • project-documentation.md
    - Project documentation
根据作业类型生成文档：
技术分析：
  • technical-analysis.md
    - 技术分析报告
研究综述：
  • research-review.md
    - 研究综述文档
案例研究：
  • case-study.md
    - 案例研究报告
项目文档：
  • project-documentation.md
    - 项目文档

File Naming Convention

文件命名规范

  • Use kebab-case: 
    cloud-computing-technical-analysis.md
  • Include version/date when needed: 
    research-review-v1.0.md
  • Use descriptive names: 
    database-optimization-case-study.md
  • Specify language if bilingual: 
    technical-analysis-en.md
    , 
    technical-analysis-zh.md
  • 使用短横线分隔命名（kebab-case）：
    cloud-computing-technical-analysis.md
  • 需要时包含版本/日期：
    research-review-v1.0.md
  • 使用描述性名称：
    database-optimization-case-study.md
  • 双语文档需指定语言：
    technical-analysis-en.md
    , 
    technical-analysis-zh.md

Delivery Summary

交付总结

After generating the document, provide a brief summary:
  • Document type and target language
  • Word count and chapter structure
  • Key topics covered
  • Writing style characteristics applied
  • File save location confirmation
生成文档后，提供简短总结：
  • 文档类型与目标语言
  • 字数与章节结构
  • 涵盖的核心主题
  • 应用的写作风格特点
  • 文件保存位置确认

References

参考资料

Detailed examples and guidelines available in:
  • references/chinese-examples.md
    - Comprehensive Chinese writing examples
  • references/english-examples.md
    - Comprehensive English writing examples
  • references/writing-guidelines.md
    - Core writing principles and techniques
详细示例与指南可在以下文件中获取：
  • references/chinese-examples.md
    - 全面的中文写作示例
  • references/english-examples.md
    - 全面的英文写作示例
  • references/writing-guidelines.md
    - 核心写作原则与技巧