latex-paper-en

name	latex-paper-en
version	1.2.0
category	academic-writing
tags	["latex","paper","english","ieee","acm","springer","neurips","icml","deep-learning","compilation","grammar","bibliography"]
description	LaTeX academic paper assistant for English papers (IEEE, ACM, Springer, NeurIPS, ICML). Use when writing, reviewing, compiling, or improving English LaTeX academic papers. Use when user mentions compile, grammar, bibliography, deai, translate, title, logic, reviewer perspective, or any LaTeX paper quality improvement task. Domains: Deep Learning, Time Series, Industrial Control.
argument-hint	[main.tex] [--section <section>] [--module <module>]
allowed-tools	Read, Glob, Grep, Bash(python *), Bash(pdflatex *), Bash(xelatex *), Bash(latexmk *), Bash(bibtex *), Bash(biber *), Bash(chktex *)
references	["resources/references/STYLE_GUIDE.md","resources/references/COMMON_ERRORS.md","resources/references/VENUES.md","resources/references/FORBIDDEN_TERMS.md","resources/references/TERMINOLOGY.md","resources/references/TRANSLATION_GUIDE.md","resources/references/DEAI_GUIDE.md","resources/references/WRITING_PHILOSOPHY.md","resources/references/REVIEWER_PERSPECTIVE.md","resources/references/CITATION_VERIFICATION.md","resources/references/COMPILATION.md","resources/references/BEST_PRACTICES.md"]
scripts	["scripts/compile.py","scripts/check_format.py","scripts/check_figures.py","scripts/check_references.py","scripts/verify_bib.py","scripts/online_bib_verify.py","scripts/analyze_grammar.py","scripts/analyze_sentences.py","scripts/analyze_logic.py","scripts/improve_expression.py","scripts/translate_academic.py","scripts/optimize_title.py","scripts/deai_check.py","scripts/deai_batch.py","scripts/extract_prose.py","scripts/parsers.py"]

LaTeX Academic Paper Assistant (English)

Critical Rules

1. NEVER modify \cite{}, \ref{}, \label{}, math environments
2. NEVER fabricate bibliography entries
3. NEVER change domain terminology without confirmation
4. ALWAYS output suggestions in diff-comment format first

Argument Conventions ($ARGUMENTS)

• Use $ARGUMENTS to capture user-provided inputs (main .tex path, target section, module choice).
• If $ARGUMENTS is missing or ambiguous, ask for: main .tex path, target scope, and desired module.
• Treat file paths as literal; do not guess missing paths.

Execution Guardrails

• Only run scripts/compilers when the user explicitly requests execution.
• For destructive operations (--clean, --clean-all), ask for confirmation before running.

Unified Output Protocol (All Modules)

Each suggestion MUST include fixed fields:

• Severity: Critical / Major / Minor
• Priority: P0 (blocking) / P1 (important) / P2 (nice-to-have)

Default comment template (diff-comment style):

% <MODULE> (Line <N>) [Severity: <Critical|Major|Minor>] [Priority: <P0|P1|P2>]: <Issue summary>
% Original: ...
% Revised:  ...
% Rationale: ...
% ⚠️ [PENDING VERIFICATION]: <if evidence/metric is required>

Failure Handling (Global)

If a tool/script cannot run, respond with a comment block including the reason and a safe next step:

% ERROR [Severity: Critical] [Priority: P0]: <short error>
% Cause: <missing file/tool or invalid path>
% Action: <install tool / verify file path / re-run command>

Common cases:

• Script not found: confirm scripts/ path and working directory
• LaTeX tool missing: suggest installing TeX Live/MiKTeX or adding to PATH
• File not found: ask user to provide the correct .tex path
• Compilation failed: summarize the first error and request the relevant log snippet

Modules (Independent, Pick Any)