light-typesetting
Build and preflight submission-ready LaTeX/PDF artifacts for Light stage 11. Use when receiving a paper-writing manuscript, figure delivery, citation delivery.json/references.bib/citekey-audit.json, or a venue/template profile; when selecting pdfLaTeX/XeLaTeX/LuaLaTeX and BibTeX/Biber; when diagnosing LaTeX errors or unresolved references; when checking page limits, double-blind identity, PDF metadata, template, page box, embedded fonts, TODOs, figures, tables, labels and citations; or when producing a reproducible compile manifest, PDF, compliance report, failure bundle and venue-matching han
npx skills add Light0305/Light-skills --skill light-typesetting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Typesetting · stage 11 Turn approved author artifacts into a reproducible PDF submission bundle. The job is not merely to make LaTeX compile: preserve provenance, select a coherent engine/backend, preflight dependencies, compile to convergence, locate the first root cause, run profile-driven desk-reject checks, and hand exact PDF/page facts to venue-matching. Read `typesetting-resource-map.md` before running a real build. Read `references/build_contract.md` before writing or consuming machine artifacts. Use `references/latex_errors.md` only after the first source-located error is known. Use a venue template under `templates/` only when it matches the current author kit; the bundled copy is a starting point, not current venue truth. ## Non-negotiable boundaries - Consume citation `delivery.json`, `references.bib` and `citekey-audit.json`. Require `delivery.status=DELIVERED`, declared `deliverable_hashes`, empty citation failures and empty claim-review leftovers. Declared citation deliverables must be relative paths inside the citation delivery directory, and the build snapshot must preserve the audit, failure and claim-review sidecars under provenance. Check staged keys and compil
- Non-negotiable boundaries
- Local LaTeX environment contract
- Workflow
- 1. Freeze the input contract
- 2. Preflight before compilation
- 3. Select engine and bibliography backend
- 4. Compile and classify convergence
- 5. Diagnose from the first root cause
- 6. Run the profile-driven desk-reject gate
- 7. Emit canonical artifacts
- 8. Derive readiness without collapsing evidence
- 9. Run stage 11 and hand off
- ACT / ASK / NEVER
- Delivery self-check
What does the light-typesetting skill do?
Build and preflight submission-ready LaTeX/PDF artifacts for Light stage 11. Use when receiving a paper-writing manuscript, figure delivery, citation delivery.json/references.bib/citekey-audit.json, or a venue/template profile; when selecting pdfLaTeX/XeLaTeX/LuaLaTeX and BibTeX/Biber; when diagnosing LaTeX errors or unresolved references; when checking page limits, double-blind identity, PDF metadata, template, page box, embedded fonts, TODOs, figures, tables, labels and citations; or when producing a reproducible compile manifest, PDF, compliance report, failure bundle and venue-matching han
How do I install it?
Run `npx skills add Light0305/Light-skills --skill light-typesetting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Light0305/Light-skills, a repository with 505 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.