القائمة
Use when editing live SCI LaTeX sources, Overleaf exports, arXiv source packages, figures, tables, citations, author blocks, labels, refs, packages, or appendix files
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when creating, revising, validating, or packaging SCI/arXiv manuscript figures, graphical abstracts, system diagrams, mechanism diagrams, evidence snapshots, image-generation prompts, figure captions, or Overleaf figure assets under claim-evidence constraints.
Use when starting or resuming any SCI paper task in this workspace, including manuscript revision, citation repair, result writing, review preflight, LaTeX editing, arXiv packaging, or multi-agent handoff
Use when finding references, building literature review tables, identifying up-to-date or highly cited papers, comparing research methods, verifying citation quality, mapping references to claims, or converting AI literature notes into SCI-ready bibliography inputs
Use when a manuscript claims novelty, improvement, efficiency, speedup, superiority, reduced cost, better performance, or contribution relative to prior work, baselines, surveys, systems, or benchmarks
Use when converting experiment tables, logs, figures, measurements, HIL outputs, simulations, or appendix data into results, discussion, limitations, or contribution text
Use when a SCI paper task begins from a vague request, reviewer comment, advisor feedback, suspected flaw, manuscript confusion, or multi-step repair need
| name | sci-latex-editing |
| description | Use when editing live SCI LaTeX sources, Overleaf exports, arXiv source packages, figures, tables, citations, author blocks, labels, refs, packages, or appendix files |
Make surgical LaTeX changes without destabilizing the manuscript.
Core principle: small scoped patches beat broad rewrites.
Use this strategy even when no project-specific TeX guide exists.
Prefer editing:
sections/*.texmain.tex only when necessaryAfter structural edits, check:
\input{} paths\input.