Skip to content

joshua-zyy/academic-paper-writer / skills/academic-latex-layout

academic-latex-layout

Verified

Use when working on academic paper LaTeX layout, figure/table float placement, draft-to-template LaTeX generation, existing .tex project layout repair, figures piling up, figures far from text, large blank areas, two-column figure/table placement, page-limit layout cleanup, or compiled PDF layout review.

references/workflow-layout-repair.md

View on GitHub
# Layout Repair Workflow

Use this workflow when a complete `.tex` project already exists and the user reports float pileups, distant figures/tables, blank areas, poor two-column layout, or page-limit pressure.

## Steps

1. Discover the project: main `.tex`, included section files, bibliography, figures directory, build files, generated PDF, and logs.
2. Identify template constraints before editing: class, style files, column mode, loaded float/caption packages, page limit, and prohibited template edits.
3. Inventory every figure/table environment: source file, environment type, placement specifier, caption, label, first `\ref`, first meaningful discussion, size, and section.
4. Diagnose root causes: float backlog, too many floats in one section, oversized assets, wrong `figure*` or `table*`, missing or excessive barriers, static references, unresolved labels, and large float-only gaps.
5. Classify each possible edit as direct-safe, confirm-first, or prohibited by default using `static/core/stance.md`.
6. Apply direct-safe edits only: local movement, local placement tuning, width correction, limited barriers, subfigure organization, and label consistency.
7. Compile using `pdf-preview-loop.md`.
8. Review the PDF outcome. Repeat only for direct-safe fixes that are clearly supported by the PDF findings.
9. Stop when remaining improvements require user confirmation or when compilation/preview is blocked.
10. Produce the layout repair report from `report-format.md`.

## Page-Limit Repair Priority

When the paper is over a hard page limit, try fixes in this order:

1. Remove accidental layout blockers: stale `\clearpage`, excessive barriers, overly restrictive placement specifiers, oversized floats, or missing assets.
2. Move floats according to semantic adjacency to reduce backlog and blank areas.
3. Adjust widths only while labels, legends, and table text remain readable.
4. Use `figure*` or `table*` when full-width placement improves both readability and page flow.
5. Consider local, venue-compatible line recovery such as `\enlargethispage` for one or two lines.
6. Consider caption font or spacing controls only if the template allows them; do not shorten caption text without confirmation.
7. Present ranked confirm-first options when remaining fixes require text cuts, figure consolidation, package additions, or template changes.

## Direct-Safe Repair Examples

| Symptom | Candidate repair |
|---|---|
| Figure appears two pages after first meaningful discussion | Move the float closer to that paragraph and prefer `[t]`, `[tbp]`, or `[!t]` over `[H]` |
| Wide figure is unreadable in one column | Consider `figure*` if the template and reading flow support full-width placement |
| Floats leak into the next section | Add a limited `\FloatBarrier` at the section boundary if `placeins` is already available or safe to add |
| Large blank region before a float | Check whether the asset is too tall/wide, float specifier is too restrictive, or an earlier barrier/page break caused the gap |
| Too many unprocessed floats | Reduce float density by moving floats to semantic locations, relaxing specifiers, or proposing consolidation; do not globally force `[H]` |

## Confirm Before Applying

Ask before shortening text, changing figure order, splitting panels, merging tables, adding risky packages, changing global spacing/page geometry, or applying many local line-recovery commands.

When all remaining options are confirm-first, present two or three ranked choices with readability impact, page savings estimate, and venue risk.

If the user declines all confirm-first options, stop with status `partial` and state that the layout is as improved as possible under direct-safe edits.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall