academic-paper-composer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Academic Paper Composer

学术论文定稿工具

Overview

概述

This is the writing and finalization skill for Codex-based undergraduate software engineering theses. It consumes the strategist's evidence-backed plan and turns it into a clean, submission-ready manuscript grounded in the real project.

Companion flow:

```
academic-paper-strategist
```
- determine structure, evidence map, keep/rewrite/delete scope
```
academic-paper-composer
```
- rewrite sections and assemble the final thesis text
```
drawio
```
- rebuild engineering-style figures when needed
```
playwright
```
- capture real runtime screenshots when the thesis needs running-system evidence
```
doc
```
- apply Word formatting and visually verify the final DOCX

This skill is responsible for the thesis content and final assembly logic. It must not claim completion until the copied or user-designated working DOCX has been formatted and checked.

这是基于Codex的本科软件工程论文写作与定稿工具。它会接收策略工具生成的基于证据的方案，将其转化为依托真实项目的、整洁且可提交的论文手稿。

配套流程:

```
academic-paper-strategist
```
- 确定结构、证据图谱、保留/重写/删除范围
```
academic-paper-composer
```
- 重写章节并组装最终论文文本
```
drawio
```
- 必要时重建工程风格图表
```
playwright
```
- 当论文需要系统运行证据时，捕获真实运行截图
```
doc
```
- 应用Word格式并可视化验证最终DOCX文件

本工具负责论文内容与最终组装逻辑，只有在复制或用户指定的工作DOCX文件完成格式设置与检查后，才能宣告任务完成。

Required Inputs

必需输入

the strategist's outline or rewrite brief
the existing thesis draft
the school format sample
the real project evidence files
detection reports when available (similarity / plagiarism / AIGC PDFs, screenshots, or extracted text)
the exact destination path for the copied final DOCX or the exact working draft path the user wants to continue editing
the exact destination path for the rework report, if provided

策略工具生成的大纲或重写简要说明
现有论文初稿
学校格式样本
真实项目证据文件
可用的检测报告（相似度/查重/AIGC的PDF、截图或提取文本）
复制后的最终DOCX文件的准确目标路径，或用户希望继续编辑的准确工作初稿路径
若有要求，改稿报告的准确目标路径

Non-Negotiable Rules

不可协商规则

Operate on a copied draft only unless the user explicitly says the current hand-edited draft is now the working file.
Never overwrite the user's untouched original source draft.

Load and obey:

references/zjkj-undergrad-thesis-format.md

```
references/project-grounding-rules.md
```
```
references/finalization-task-rules.md
```

Load
```
references/detection-report-rewrite-playbook.md
```
whenever the user asks to lower similarity or AIGC risk and provides reports.
Load
```
references/docx-draft-salvage-and-runtime-screenshot-playbook.md
```
whenever the task involves continuing from a hand-edited draft, partial section replacement, restoring original tables/figures, or adding real running-system screenshots.
Load
```
references/thesis-revision-operation-checklist.md
```
whenever the task involves editing a live working draft, because the edit order matters.
Rewrite unsupported text instead of polishing false content.
When lowering similarity or AIGC risk, rewrite the wording while preserving project truth; never game the score by inventing facts or deleting essential substance.
Keep all visible manuscript text black.
Remove hyperlink styling, process notes, instructional text, and template hints.
Use only project-supported figures and screenshots.
Prefer restoring a supported original figure/table over redrawing it.
Keep the testing chapter conservative and evidence-based.

仅对复制的初稿进行操作，除非用户明确表示当前手动编辑的初稿为工作文件。
绝不能覆盖用户未改动的原始初稿。

加载并遵循：

references/zjkj-undergrad-thesis-format.md

```
references/project-grounding-rules.md
```
```
references/finalization-task-rules.md
```

当用户要求降低相似度或AIGC风险并提供报告时，加载
```
references/detection-report-rewrite-playbook.md
```
。
当任务涉及基于手动编辑的初稿继续修改、部分章节替换、恢复原始表格/图表或添加真实系统运行截图时，加载
```
references/docx-draft-salvage-and-runtime-screenshot-playbook.md
```
。
当任务涉及编辑实时工作初稿时，加载
```
references/thesis-revision-operation-checklist.md
```
，因为编辑顺序至关重要。
重写不被支持的文本，而非润色虚假内容。
降低相似度或AIGC风险时，在保留项目真实性的前提下重写措辞；绝不能通过编造事实或删除核心内容来刻意操控分数。
所有可见手稿文本保持黑色。
移除超链接样式、处理备注、指导文本和模板提示。
仅使用项目支持的图表和截图。
优先恢复受支持的原始图表/表格，而非重新绘制。
测试章节需保持严谨且基于证据。

Workflow

工作流程

Step 1: Safety Copy

步骤1：安全复制

If the user provides a source draft and a destination path:

copy the source draft first
verify the destination copy exists
preserve the source draft untouched

If the user says the already hand-edited draft is the working file:

treat that file as the working manuscript
create a timestamped backup before any structural edit
keep all later edits on that working file only

Do not start direct editing on the wrong file under any circumstance.

若用户提供源初稿和目标路径：

先复制源初稿
验证目标副本存在
保持源初稿未被改动

若用户表示已手动编辑的初稿为工作文件：

将该文件视为工作手稿
在进行任何结构性编辑前创建带时间戳的备份
后续所有编辑仅针对该工作文件

任何情况下都不得直接编辑错误的文件。

Step 2: Format Baseline Extraction

步骤2：格式基准提取

Read

references/zjkj-undergrad-thesis-format.md

and the provided school sample.

Extract and enforce:

cover structure
originality statement
copyright authorization
Chinese abstract page
English abstract page
automatic table of contents
heading hierarchy
body typography
figure/table caption style
references
acknowledgement
appendices

读取

references/zjkj-undergrad-thesis-format.md

和提供的学校样本。

提取并执行以下格式要求：

封面结构
原创性声明
版权授权书
中文摘要页
英文摘要页
自动生成的目录
标题层级
正文排版
图表标题样式
参考文献
致谢
附录

Step 3: Draft Audit

步骤3：初稿审核

Scan the current draft and mark:

content to keep
content to rewrite
content to delete
figures to replace
figures/tables to preserve from the original draft
formatting pollution to remove

Specifically remove:

colored titles
hyperlink-style headings
template prompts
revision notes
unsupported data claims
decorative figures

扫描当前初稿并标记：

需保留的内容
需重写的内容
需删除的内容
需替换的图表
需从原始初稿保留的图表/表格
需移除的格式污染

需特别移除：

彩色标题
超链接样式标题
模板提示
修改备注
无依据的数据声明
装饰性图表

Step 3A: Detection-Report Triage

步骤3A：检测报告分类处理

If the user provided similarity or AIGC reports, read

references/detection-report-rewrite-playbook.md

At this stage:

extract the latest score and hotspot pages
map each hotspot back to the copied draft
decide whether each hotspot needs heavy structural rewriting or light cleanup

若用户提供相似度或AIGC报告，读取

references/detection-report-rewrite-playbook.md

。

此阶段需：

提取最新分数和热点页面
将每个热点对应到复制的初稿
判断每个热点是需要大幅结构性重写还是轻度清理

Step 3B: Existing-Draft Continuation / Salvage Mode

步骤3B：现有初稿续改/修复模式

Use this mode when the user has already hand-edited part of the draft or asks to keep specific old content.

In this mode:

identify the true working DOCX first
identify the protected backup/original DOCX second
detect replacement boundaries by body heading style, not by table-of-contents text
never use TOC paragraphs as anchors for section replacement
when the user asks to replace only content before or after a section such as
```
2.3
```
, edit only that body span
preserve untouched manual edits outside the requested span
if the user asks to keep an original E-R figure, per-table database description, or other supported legacy asset, restore it from backup instead of regenerating it

当用户已手动编辑部分初稿或要求保留特定旧内容时，使用此模式。

此模式下：

先确定真正的工作DOCX文件
再确定受保护的备份/原始DOCX文件
通过正文标题样式检测替换边界，而非目录文本
绝不能将目录段落作为章节替换的锚点
当用户要求仅替换如
```
2.3
```
之前或之后的内容时，仅编辑对应正文范围
保留请求范围外未改动的手动编辑内容
若用户要求保留原始E-R图、每张表的数据库描述或其他受支持的旧资产，从备份中恢复而非重新生成

Step 4: Rewrite The Thesis Body

步骤4：重写论文正文

Rewrite chapter by chapter using only project-supported evidence.

Typical chapter responsibilities:

Introduction: background, significance, scope, chapter arrangement
Requirements analysis: roles, workflows, functional and non-functional requirements
Overall design: architecture, modules, data design, security/control strategy
Detailed implementation: real mechanisms from code and config
Testing: real functional verification and conservative summary
Conclusion: summarize actual completed work and future improvements

For every section:

prefer precise engineering wording
avoid exaggerated novelty language
avoid unsupported metrics
remove any instruction text before final assembly

When the task includes lowering similarity or AIGC risk, apply these rewrite rules:

follow the rewrite principles and transformations in
```
references/detection-report-rewrite-playbook.md
```
keep technical facts, chapter structure, figure/table numbering, and citations stable unless they are unsupported
preserve meaning first; score reduction is secondary to factual accuracy

仅使用项目支持的证据逐章重写。

典型章节职责：

引言：背景、意义、研究范围、章节安排
需求分析：角色、工作流、功能与非功能需求
总体设计：架构、模块、数据设计、安全/控制策略
详细实现：来自代码和配置的真实机制
测试：真实功能验证与严谨总结
结论：总结实际完成的工作与未来改进方向

对于每个章节：

优先使用精准的工程术语
避免夸大的创新性表述
避免无依据的指标
最终组装前移除所有指导文本

当任务包含降低相似度或AIGC风险时，应用以下重写规则：

遵循

references/detection-report-rewrite-playbook.md

中的重写原则与转换方法

保持技术事实、章节结构、图表编号和引用稳定，除非它们不被支持
优先保留含义；分数降低是事实准确性的次要目标

Step 4A: Anti-AIGC / Anti-Similarity Rewrite Loop

步骤4A：反AIGC/反相似度重写循环

When the user gives a target such as "降到 10% 以下":

attack the highest-yield hotspots first
rebuild the copied manuscript
if the user brings back a newer report, repeat the triage -> rewrite -> rebuild loop
in later rounds, focus only on the remaining hotspot pages instead of rewriting the whole paper again

Do not promise a score in advance. The composer's responsibility is to maximize safe, evidence-preserving reductions.

当用户给出目标（如"降到10%以下"）：

优先处理收益最高的热点
重建复制的手稿
若用户提供更新的报告，重复分类处理->重写->重建循环
后续轮次中，仅关注剩余热点页面，而非重写整篇论文

不得提前承诺分数。本工具的职责是在保证安全、保留证据的前提下最大化降低分数。

Step 5: Figures, Legacy Assets, And Database Tables

步骤5：图表、旧资产与数据库表

If the thesis already contains a supported original figure or table block that the user wants to keep:

preserve or restore it from the backup/original draft
keep the caption style consistent with the school sample
renumber later figures/tables only when necessary

Common salvage cases include:

original E-R figure blocks
per-table database field-description blocks
screenshots already extracted from a valid older manuscript
original engineering diagrams that still match the project

Only redraw through

drawio

when the figure is missing, unsupported, or visually unsuitable.

若论文包含用户希望保留的受支持原始图表或表格块：

从备份/原始初稿中保留或恢复
保持标题样式与学校样本一致
仅在必要时重新编号后续图表/表格

常见修复场景包括：

原始E-R图块
每张表的数据库字段描述块
已从有效旧手稿中提取的截图
仍与项目匹配的原始工程图

仅当图表缺失、不被支持或视觉不合适时，通过

drawio

重新绘制。

Step 5A: Real Runtime Screenshot Capture

步骤5A：真实运行截图捕获

If the thesis needs system-running screenshots:

prefer capturing the real application over fabricating static mockups
use
```
playwright
```
or an equivalent browser workflow
save screenshot assets under
```
output/playwright/
```
or a similarly explicit output directory
insert screenshots near the subsection they support, with one short lead-in sentence and a thesis-style caption

When the main database is unavailable or risky to touch:

create a temporary screenshot-only config
prefer an isolated H2 + Flyway setup over modifying the primary
```
application.yml
```
seed or create only minimal demo data needed for the screenshots
shut down the temporary runtime after capture

Good screenshot targets include:

login page for authentication chapter
resident appointment page for appointment flow chapter
resident dashboard / health-code page for health-code chapter
resident health-report page for reporting chapter
admin appointment / review pages for backend operation chapters
admin dashboard for operation summary / running-status sections

若论文需要系统运行截图：

优先捕获真实应用，而非制作静态模拟图
使用
```
playwright
```
或等效浏览器流程
将截图资产保存到
```
output/playwright/
```
或类似明确的输出目录
将截图插入到其支持的小节附近，附带一句简短引导语和符合论文风格的标题

当主数据库不可用或操作存在风险时：

创建仅用于截图的临时配置
优先使用独立的H2 + Flyway设置，而非修改主
```
application.yml
```
仅生成截图所需的最小演示数据
捕获完成后关闭临时运行环境

合适的截图目标包括：

认证章节的登录页面
预约流程章节的居民预约页面
健康码章节的居民仪表盘/健康码页面
报告章节的居民健康报告页面
后端操作章节的管理员预约/审核页面
运行状态总结章节的管理员仪表盘

Step 6: Final DOCX Formatting Through Doc

步骤6：通过Doc完成最终DOCX格式设置

Use

doc

to finalize the working

.docx

apply school-required heading styles
ensure all text is black
ensure Chinese headings are not bold unless the school sample explicitly requires it
ensure paragraph spacing and line spacing match the school sample
ensure TOC is automatic
ensure figures and captions are placed correctly
ensure references use hanging indent and correct typography
ensure field-description tables use the correct smaller font when the sample requires it
render and visually inspect pages when possible

使用

doc

完成工作

.docx

文件的最终格式设置：

应用学校要求的标题样式
确保所有文本为黑色
确保中文标题不加粗，除非学校样本明确要求
确保段落间距和行间距与学校样本匹配
确保目录为自动生成
确保图表及其标题放置正确
确保参考文献使用悬挂缩进和正确排版
确保字段描述表格在样本要求时使用正确的小字体
尽可能渲染并可视化检查页面

Step 7: Write A Separate Rework Report

步骤7：撰写单独的改稿报告

The rework report belongs outside the final thesis and may include:

deleted or weakened claims
unsupported data not retained
manual review items
figure rebuild notes
formatting fixes
for similarity / AIGC tasks: which pages were hotspots, what rewrite strategy was used, and what still needs recheck in the next report
for salvage tasks: which sections were restored from backup, which screenshots were newly captured, and which manual edits were intentionally preserved

Do not let any of that text leak into the final DOCX body.

改稿报告独立于最终论文，可包含：

删除或弱化的声明
未保留的无依据数据
人工审核项
图表重建说明
格式修复内容
针对相似度/AIGC任务：哪些页面是热点、使用了何种重写策略、下次报告中仍需复查的内容
针对修复任务：哪些章节从备份中恢复、哪些是新捕获的截图、哪些手动编辑内容被刻意保留

不得让任何此类文本泄露到最终DOCX正文中。

Step 8: Final Self-Check

步骤8：最终自检

Do not deliver until all of the following are true:

original draft untouched or explicitly superseded by a user-designated working draft
working DOCX backed up before structural edits
TOC paragraphs were not mistaken for body anchors
all headings/body text black
no blue titles remain
all figures and screenshots match thesis style
legacy figures/tables requested by the user were preserved or restored
no process/instruction text remains
school format sample followed
TOC automatic
manuscript is ready to submit

需满足以下所有条件才可交付：

原始初稿未被改动，或被用户指定的工作初稿明确替代
工作DOCX文件在结构性编辑前已备份
未将目录段落误作为正文锚点
所有标题/正文文本为黑色
无蓝色标题残留
所有图表和截图符合论文风格
用户要求保留的旧图表/表格已被保留或恢复
无流程/指导文本残留
遵循学校格式样本
目录为自动生成
手稿可提交

Writing Rules For Conservative Accuracy

严谨准确性写作规则

Replace unsupported "performance evaluation" with "functional verification" or "scenario-based testing" when appropriate.
If no formal stress test exists, do not write performance benchmark tables.
If no real deployment exists, avoid claims about cluster deployment, production operation, or concurrency scale.
If a module is configured but not fully demonstrated, describe it carefully as implemented support rather than proven large-scale capability.
For high-risk AIGC paragraphs, prefer "rewrite the whole sentence logic" over "swap a few words".
When a paragraph still reads like a polished template, reduce polish before you reduce truth: vary sentence length, remove stock transitions, and anchor the wording in the actual repository.

必要时，将无依据的"性能评估"替换为"功能验证"或"基于场景的测试"。
若无正式压力测试，不得撰写性能基准表。
若无真实部署，避免提及集群部署、生产运行或并发规模相关声明。
若模块已配置但未充分演示，需谨慎描述为已实现的支持功能，而非经证实的大规模能力。
针对高风险AIGC段落，优先"重写整句逻辑"而非"替换个别词汇"。
当段落仍像润色后的模板时，在不降低真实性的前提下减少润色：调整句子长度、移除通用过渡语、将措辞与实际代码库关联。

References To Load As Needed

按需加载的参考文件

references/zjkj-undergrad-thesis-format.md

```
references/project-grounding-rules.md
```
```
references/finalization-task-rules.md
```

references/detection-report-rewrite-playbook.md

references/docx-draft-salvage-and-runtime-screenshot-playbook.md

references/thesis-revision-operation-checklist.md

references/chinese-call-prompt-templates.md

```
references/section_guides.md
```
```
references/writing_standards.md
```

references/zjkj-undergrad-thesis-format.md

```
references/project-grounding-rules.md
```
```
references/finalization-task-rules.md
```

references/detection-report-rewrite-playbook.md

references/docx-draft-salvage-and-runtime-screenshot-playbook.md

references/thesis-revision-operation-checklist.md

references/chinese-call-prompt-templates.md

```
references/section_guides.md
```
```
references/writing_standards.md
```

Example Prompts

示例提示

继续在我手改的初稿上改，只替换正文 1 引言 到 2.3 前面的内容，目录不要当锚点。

保留原来的数据库 E-R 图和每张表的字段说明表，再把定稿对应内容补回 working draft。

根据这份最新 AIGC 报告继续降到 10% 以下，只改剩余热点页，不要整篇重写。

按学校模板把当前 working docx 整理成最终版：标题不要加粗，全文黑色，表格字段说明用五号。

给论文补系统运行截图，截图要来自真实项目页面，并且单独输出一份改稿说明。

继续在我手改的初稿上改，只替换正文1引言到2.3前面的内容，目录不要当锚点。

保留原来的数据库E-R图和每张表的字段说明表，再把定稿对应内容补回working draft。

根据这份最新AIGC报告继续降到10%以下，只改剩余热点页，不要整篇重写。

按学校模板把当前working docx整理成最终版：标题不要加粗，全文黑色，表格字段说明用五号。

给论文补系统运行截图，截图要来自真实项目页面，并且单独输出一份改稿说明。

Output Expectations

输出预期

Produce:

a cleaned thesis manuscript
a final DOCX workflow executed on the copied draft or user-designated working draft
a separate rework report

Never treat comments to the author, fix notes, or review annotations as manuscript content.

生成：

清洁后的论文手稿
在复制初稿或用户指定的工作初稿上执行的最终DOCX处理流程
单独的改稿报告

绝不能将给作者的评论、修复提示或审核注释视为手稿内容。