ai-paper-writing

name	ai-paper-writing
description	Assist with drafting, polishing, grammar checking, and BibTeX cleaning for AI top-tier conference or journal papers in LaTeX. Use when working on manuscripts targeting venues such as ICLR, NeurIPS, ICML, CVPR, ICCV, ECCV, AAAI, IJCAI, KDD, WWW, IEEE TPAMI, IEEE TMM, IEEE TIP, IEEE TNNLS, IJCV, JMLR, or TMLR.

AI Top Paper Writing

1. Project Overview

Treat the manuscript as submission-targeted work for an AI top conference or top journal. If the user specifies a target venue and year, follow that target strictly. If unspecified, follow the writing style of top-tier AI conferences such as CVPR, ICCV, NeurIPS, ICML, and ICLR.

At the beginning of each skill invocation, return the checklist below and ask the user to confirm or update each item before writing:

Treat the file layout below as a suggested default, not a requirement. If the user defines a different project structure in # Custom prompts, follow the user-defined structure instead.

• ./Aux: manuscript support materials
• ./Aux/Rebuttal: rebuttal materials
• ./Figs: figure assets
• ./Sec: section .tex files
• ./Aux/Rebuttal/{venue}-Reviews.md or ./Aux/Rebuttal/{venue}-{reviewer}.md: review file(s), either a single file for all reviewers or one file per reviewer (for example ICLR26-Reviews.md or ICLR26-R1.md).
• preamble.tex: predefined LaTeX macros
• xx.bib: bibliography source (\bibliography{xx.bib})
• AGENTS.md: Codex local prompt file with project-specific custom prompts. This skill defaults to Codex. If using another AI tool, such as GitHub Copilot or Claude Code, rename or adapt this prompt file according to that tool's own instruction-file convention.
• .vscode/settings.json: fixed VS Code LaTeX Workshop settings
• .latexmkrc: fixed local latexmk configuration
• .gitignore: fixed ignore rules aligned with the LaTeX workflow
• Aux/Guidelines.pdf: formatting guideline.

All checklist items are optional. If any item is missing, return a concise hint about its purpose and how to provide it, then continue with the available context.

---

2. Writing and Formatting Requirements

2.1 LaTeX Conventions

When writing equations and text in LaTeX (Overleaf), please follow these specific rules carefully:

• Do not use prohibited spacing commands. Avoid \;, \!, or \, at all times.

• Adaptive brackets. Always use \left and \right for scalable delimiters (parentheses, brackets, braces, absolute values, etc.). Do not use manual size commands such as \big, \Big, \bigl, \bigr, \biggl, or \Biggl, unless i explicitly require so. Use plain (, ), [, ], {, }, and | when no scaling is needed, and use \left. / \right. for invisible delimiters.

• Predefined macros. Use only the macros already defined in preamble.tex.
  Do not redefine or modify them locally within any section.

• Bibliography management.
  Use the following bibliography sources only:

  \bibliography{xx.bib}
  

  Do not create new or fabricated references.
  If a reference is missing, request the citation so that it can be added.

• Prohibition of sentence splitting dashes. Do not use any long dash symbols such as -- or --- to separate or cut sentences. When you need a pause or a shift in tone, use commas, conjunctions, or split the content into two sentences instead. You are still allowed to use - and -- in compound words, such as "manifold-valued point", "point-to-horosphere", "ResNet-18", 'Beltrami--Klein' and so on, and to use standard dash notation where it is required.

• Please use $...$ not \(...\) for inline equations;

• Display equations. Use \begin{equation} ... \end{equation} or \begin{align} ... \end{align} for display equations instead of \[ ... \]. Display equations do not require labels unless they are cited later. In the appendix, do not use align unless sub-equations must be labeled, or I explicitly require so. Use aligned within equation for multi-line equations to avoid generating unnecessary equation numbers.

• When introducing the terminology for the first time, please use \emph{}. For instance the terminology in \begin{definition}, and terminology in the main text when we do not use definition environment. If the terminology first shown in text and then formally defined in \begin{definition}, please use \emph{} only in the \begin{definition}.

• Use \textbf{xxxx.} instead of \paragraph{xxxx} to highlight the heading of each paragraph.

• When describing a set, use \{x \mid \text{condition}\} instead of \{x : \text{condition}\}.

• When writing or editing the manuscript, minimize the use of semicolons (“;”) unless strictly necessary, such as when enumerating multiple complex items within a single sentence (e.g., “(1); (2); (3); …”). If the sentence can be clearly expressed as two separate sentences without affecting logical continuity, prefer splitting it rather than connecting with a semicolon.

---

2.2 Writing Style and Editing Rules

When providing academic writing assistance or polishing text, follow these principles:

• Preserve mathematical and technical accuracy.
  Do not change the meaning, symbols, or any LaTeX command within equations.

• Enhance academic fluency and clarity.
  Rewrite in precise and professional English consistent with AI top-tier papers, such as CVPR/ICCV/NeurIPS/ICML/ICLR.

• Maintain consistency across sections.
  Ensure uniform notation, flow, and tone throughout the entire manuscript.

• When asked to write, polish, or rewrite a section, always read the surrounding context to ensure consistency in notation, terminology, and logic. Adhere to the above LaTeX conventions and writing style rules.

2.3 Refs

By default, all refs as well as the manuscript can be found in ./Aux. If the user defines a different layout in # Custom prompts, follow that layout instead.

---

3. Collaboration and Writing Procedure

3.1 Academic Writing Assistance

I may provide initial drafts, mathematical derivations, or conceptual notes. You will return a refined, publication-ready LaTeX version that meets the formal style of top-tier AI venues. You can revise my latex directly, unless I indicate otherwise.

When working on conceptual notes or bullet points, You will convert them into coherent academic text and ensure consistent mathematical presentation.

If a citation, definition, or formula is missing, You will explicitly note it so that the missing item can be added later.

---

3.2 Initialization

When I say init latex, initialize the LaTeX workspace for VS Code with LaTeX Workshop by applying the project setup below before any writing or polishing work.

• Work from the manuscript root that contains the main .tex entry file.

• Detect the default main file first. If main.tex exists, use it as the default root file. If main.tex does not exist, ask me which .tex file should be treated as the main file before initialization, because the fixed settings below assume main.tex.

• Ensure the folders Aux/, Figs/, and Sec/ exist. Create any missing folder before writing the configuration files.

• Create .vscode/ if it does not already exist.

• Treat AGENTS.md as the default local prompt file for Codex. If the manuscript will be maintained with another AI tool, such as GitHub Copilot or Claude Code, use that tool's corresponding instruction file name and copy or adapt the same prompt content there.

• Write AGENTS.md with the exact content below, without adapting or merging:

  Use $ai-paper-writing.
  
  # Custom prompts
  # add your own prompts below
  

• Write .latexmkrc with the exact content below, without adapting or merging:

  $out_dir = 'out';
  $aux_dir  = 'out';
  
  # Optional: keep only final PDF in out/ and minimal aux in repo root
  # You can extend the list of extensions latexmk cleans if needed.
  
  # Enable shell-escape so glossaries-extra's automake can run
  # makeglossaries/makeglossaries-lite from within LaTeX.
  $pdflatex = 'pdflatex -shell-escape %O %S';
  $xelatex  = 'xelatex  -shell-escape %O %S';
  $lualatex = 'lualatex -shell-escape %O %S';
  

• Write .vscode/settings.json with the exact content below, without adapting or merging:

  {
    "latex-workshop.latex.outDir": "%DIR%/out",
    "latex-workshop.latex.autoClean.run": "onBuilt",
    "latex-workshop.latex.clean.subfolder.enabled": true,
    "latex-workshop.latex.clean.fileTypes": [
      "*.aux",
      "*.bbl",
      "*.blg",
      "*.bcf",
      "*.fdb_latexmk",
      "*.fls",
      "*.log",
      "*.out",
      "*.synctex.gz",
      "*.toc",
      "*.run.xml",
      "*.nav",
      "*.snm",
      "*.vrb",
      "*.xdv"
    ],
    "latex-workshop.latex.rootFile.doNotPrompt": false,
    "latex-workshop.view.pdf.viewer": "tab",
    "latex-workshop.latex.autoBuild.run": "onSave",
    "latex-workshop.view.pdf.internal.synctex.keybinding": "double-click",
    "latex-workshop.latex.search.rootFiles.include": [
      "main.tex",
      "rebuttal.tex"
    ],
    // "latex-workshop.latex.search.rootFiles.exclude": [
    //   "**/rebuttal.tex"
    // ],
    "latex-workshop.latex.tools": [
      {
        "name": "latexmk-main",
        "command": "latexmk",
        "args": [
          "-pdf",
          "-interaction=nonstopmode",
          "-synctex=1",
          "-file-line-error",
          "-outdir=out",
          "main.tex"
        ]
      },
      {
        "name": "latexmk-rebuttal",
        "command": "latexmk",
        "args": [
          "-pdf",
          "-interaction=nonstopmode",
          "-synctex=1",
          "-file-line-error",
          "-outdir=out",
          "rebuttal.tex"
        ]
      },
    ],
    "latex-workshop.latex.recipes": [
      {
        "name": "latexmk (main.tex)",
        "tools": [
          "latexmk-main"
        ]
      },
      {
        "name": "latexmk (rebuttal.tex)",
        "tools": [
          "latexmk-rebuttal"
        ]
      },
    ],
    "latex-workshop.latex.recipe.default": "latexmk (main.tex)",
    "files.exclude": {
      "**/out/**/*.aux": true,
      "**/out/**/*.bbl": true,
      "**/out/**/*.blg": true,
      "**/out/**/*.bcf": true,
      "**/out/**/*.fdb_latexmk": true,
      "**/out/**/*.fls": true,
      "**/out/**/*.log": true,
      "**/out/**/*.out": true,
      "**/out/**/*.synctex.gz": true,
      "**/out/**/*.toc": true,
      "**/out/**/*.run.xml": true,
      "**/out/**/*.nav": true,
      "**/out/**/*.snm": true,
      "**/out/**/*.vrb": true,
      "**/out/**/*.xdv": true
    },
    "ltex.language": "en-US",
    "ltex.enabled": ["latex", "markdown"],
    "ltex.latex.useLaTeXParser": true,
    "ltex.latex.commands": {
      "\\cite": "ignore",
      "\\citet": "ignore",
      "\\citep": "ignore",
      "\\cref": "ignore",
      "\\Cref": "ignore",
      "\\ref": "ignore",
      "\\eqref": "ignore",
      "\\url": "ignore",
      "\\inner": "ignore",
      "\\norm": "ignore",
      "\\Linner": "ignore",
      "\\Lnorm": "ignore",
      "\\pball": "ignore",
      "\\lorentz": "ignore"
    },
    "ltex.latex.environments": {
      "equation": "ignore",
      "equation*": "ignore",
      "align": "ignore",
      "align*": "ignore",
      "gather": "ignore",
      "gather*": "ignore",
      "multline": "ignore",
      "multline*": "ignore"
    },
    "editor.wordWrap": "on",
    "editor.wordWrapColumn": 80,
    "editor.wrappingStrategy": "advanced",
    "diffEditor.wordWrap": "on",
    "diffEditor.renderSideBySide": false
  }
  

• Write .gitignore with the exact content below, without adapting or merging:

  # LaTeX intermediates and outputs
  out/*
  !out/
  !out/*.pdf
  *.aux
  *.bbl
  *.blg
  *.bcf
  *.fdb_latexmk
  *.fls
  *.log
  *.out
  *.synctex.gz
  *.toc
  *.run.xml
  *.nav
  *.snm
  *.vrb
  
  # macOS
  .DS_Store
  
  # VSCode workspace settings
  .vscode/
  
  # Shell scripts (omit from git)
  *.sh
  
  # Local-only config (omit from git)
  .latexmkrc
  .gitignore
  AGENTS.md
  AGENTS-Rebuttal.md
  /Aux/
  # \n# Reference PDFs not needed on Overleaf
  # Aux/*.pdf
  

• Do not preserve or merge unrelated existing entries in these four files. The goal of init latex is to make them match the fixed template exactly.

After initialization, briefly report which files were written and which folders were created.

3.3 Grammar check

When asked to perform a grammar check, only identify and correct grammatical errors without rephrasing or polishing the sentences. Do not alter style, structure, or word choice. Additionally, verify that all LaTeX commands comply with the project’s LaTeX Conventions.

Also check if there is any place violates the guidelines in Aux/Guidelines.pdf. If there are no explicit instructions, you may directly make the necessary corrections in the LaTeX source.

3.4 Prompt: Bib Check Instruction

When I say bib check, please automatically clean and standardize my .bib file according to the following rules:

• Apply the formatting rules only to entries from the following top-tier conferences and journals:
  ICML, ICLR, NeurIPS, ICCV, CVPR, ECCV, AAAI, IJCAI, KDD, WWW, IEEE TPAMI, IEEE TMM, IEEE TIP, IEEE TNNLS, IJCV, JMLR, TMLR.

• For each matching entry, keep only the following fields: title, author, booktitle (or journal), and year.

• Remove all other fields (e.g., abstract, pages, doi, url, volume, number, publisher, address, organization, isbn, series, note, month).

• Normalize venue names to their official abbreviated forms, such as:

  • NeurIPS, ICML, ICLR, CVPR, ICCV, ECCV, AAAI, IJCAI, KDD, WWW,
  • IEEE TPAMI, IEEE TIP, IEEE TMM, IEEE TNNLS, IJCV, JMLR, TMLR.
    Replace full names with abbreviations and auto-fill missing venue info if inferable.

• The cleaned entries must follow this exact structure (no extra fields, no extra blank lines):

```bibtex @inproceedings{bdeir2025robust, title = {Robust Hyperbolic Learning with Curvature-Aware Optimization}, author = {Ahmad Bdeir and Johannes Burchert and Lars Schmidt-Thieme and Niels Landwehr}, booktitle = {NeurIPS}, year = {2025} } ```

• Output only the cleaned .bib content, without comments or explanations.
• Do not reorder keys unless the key is clearly invalid; otherwise preserve original citation keys.
• During bib check, also detect potential duplicate references: two entries should be treated as potential duplicates if they have (almost) identical title and author information, even if their citation keys are different. In such cases, do not delete or merge them automatically. Instead, explicitly list and report these suspected duplicates back to me so that I can decide how to modify them.