# Researchstack Paper Layout

> LaTeX and presentation-layout skill for research papers. Use when Codex should improve paper structure, section ordering, notation consistency, figure placement, table formatting, captions, appendix organization, or submission compliance while preserving technical precision and readability.

- Skill: `lqf0624/researchstack-paper-layout-2` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add lqf0624/researchstack-paper-layout-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lqf0624/researchstack-paper-layout-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: lqf0624 (https://skillmd.com/u/lqf0624)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lqf0624/researchstack-paper-layout-2

---


<!-- AUTO-GENERATED for codex from researchstack v0.3.0. Edit source SKILL.md files, then regenerate from the source checkout. -->

# Paper Layout

Read [../researchstack/references/figures.md](../researchstack/references/figures.md).

Use the bundled checklists:

- [assets/latex-structure-checklist.md](assets/latex-structure-checklist.md)
- [assets/caption-table-checklist.md](assets/caption-table-checklist.md)
- [assets/appendix-camera-ready-checklist.md](assets/appendix-camera-ready-checklist.md)

Treat layout as part of argument clarity.

Focus on:

- section flow and narrative load,
- notation consistency,
- figure/table placement near first reference,
- caption self-sufficiency,
- appendix boundary discipline,
- camera-ready formatting risks.

When revising layout:

1. Surface reader friction points.
2. Suggest a better ordering.
3. Identify bloated paragraphs that should become bullets, tables, or figures.
4. Normalize notation, acronyms, and terminology.
5. Check whether key evidence is buried too late.

For tables:

- use clear column semantics,
- highlight the intended comparison,
- avoid dense walls of decimals without narrative support.

When reviewing a draft, mark each checklist item as `pass`, `fix`, or `n/a`.

Compile or render the deliverable before handoff. Inspect the actual pages for broken fonts, overflow, clipped content, misplaced floats, unreadable captions, and inconsistent notation. A valid source file alone does not pass layout review.