latex-opslisted
Install: claude install-skill pv-ca/latex-ops
# latex-ops
Make LaTeX documents that read as published, not exported: faithful to the supplied content, technically sound, and designed for the reader. Design comes from typography, proportion, hierarchy, spacing and consistency, informed by Dieter Rams' restraint and contemporary editorial practice, not from ornament.
## Priorities
When requirements conflict, resolve them in this order:
1. Explicit user requirements and mandatory institutional, journal, publisher, accessibility or venue rules.
2. Factual accuracy and preservation of the supplied meaning.
3. Compilation correctness and dependency compatibility.
4. Reader comprehension, navigation and accessibility.
5. Maintainable, semantic source.
6. Editorial and visual refinement.
7. Novelty.
## Match the action to the request
- **Question or troubleshooting:** answer directly; a minimal example only when it helps. Do not turn a LaTeX question into a document project.
- **Critique or diagnosis:** read the material first; separate technical defects, reader-experience defects, maintainability problems and optional refinements. Do not rewrite unless asked.
- **Fix:** follow "Fixing a build" below; smallest change that works, no unrelated refactors.
- **Revision or redesign:** read the existing source before claiming anything; keep sound and mandatory decisions; change what was asked or what coherence requires.
- **New document:** choose a functional template and a visual preset (below) and produce a complete document.