jaccen/awesome-gaussian-skills/cg-paper-writing

CG Paper Writing Engine (Router)

Evidence-first operating contract

Use this skill to improve research clarity, auditability and writing efficiency. Do not promise acceptance, predict acceptance probabilities from self-scores, or imply that simulated roles are actual journal reviewers. For conflicts among fragments, this contract and references/review-integrity.md take precedence over historical templates and scoring heuristics.

Start from the supplied artifacts: manuscript/version, research question, contribution type, target venue/year/track, available results and requested deliverable. Proceed with a bounded draft when inputs are incomplete; label missing evidence rather than inventing it. A focused edit does not require a full submission audit. Only certify submission readiness for checks actually completed.

For methods, experiments, novelty assessment and full-paper review, load domain-evidence-review.md. For Nature-family targeting, also load top-journal-strategy.md; resolve the exact journal and article type before applying its requirements.

Templates are optional rhetorical examples, not evidence or mandatory contribution counts. Public-paper critique and author-owned mock review differ from confidential assigned peer review: verify the venue's current AI/confidentiality rules before accepting review materials; do not process prohibited confidential submissions or generate prohibited official review content.

Architecture: Axis-driven static/dynamic router. Do NOT try to apply the writing logic from memory or from this router alone. Always load fragments from disk as described below.

Step 1 — Detect Request Axes

Analyze the user's request to determine axis values:

Axis: section

Axis: task (lifecycle fusion, 2026-10-27)

Task axis takes precedence over section axis when both are detected. For example, "评估这个 idea" → task=idea-eval (ignore section); "画架构图" → task=figure (also sets section=figure); "回复审稿人" → task=rebuttal (also sets section=rebuttal). When task=none, fall back to section-driven routing.

Axis: venue

If the user does not specify, defaults are: section=all, venue=all.

Step 2 — Load Required Fragments

Always Load (every invocation)

Read these files from references/:

• references/review-integrity.md — Shared evidence and scoped review rules
• references/core-stance.md — Role, writing process, de-AI rules, citation fact-check, guardrails
• references/symbols-terminology.md — Mathematical symbols, CG/CAD/3D terminology reference
• references/writing-patterns-from-top-papers.md — Exemplar patterns from 3DGS/Mip-Splatting/D4RT (concrete writing techniques with direct quotes); load for style calibration on any section
• references/core-paper-writing-paradigm.md — 领域通用论文架构模式（多源证据：10 篇 CVPR 2026 共性 + 3DGS/Mip-Splatting/D4RT 逐句拆解 + 四方向模板；两篇新增样本仅入证据附录）：给“论证链六环 + 五类论文 + 八环节变体矩阵”的不变量与中英双轨模板；任何环节写作、结构规划、中文核心投稿、按范文校准文风时加载

On-Demand Load (by detected section)

On-Demand Load (by detected task — lifecycle fusion)

When task axis is non-none, load the corresponding fragment FIRST, then supplement with section/venue fragments if the task also involves writing. Task fragments fuse 7 external skills into this skill for full-pipeline coverage (2026-10-27).

On-Demand Load (by detected venue)