playbooks

home / skills / a5c-ai / babysitter / latex-proof-formatter

latex-proof-formatter skill

/plugins/babysitter/skills/babysit/process/specializations/domains/science/computer-science/skills/latex-proof-formatter

This skill formats proofs and algorithms in publication-quality LaTeX, applying inference rules, algorithms, cross-references, and style compliance.

npx playbooks add skill a5c-ai/babysitter --skill latex-proof-formatter

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1010 B
---
name: latex-proof-formatter
description: Format proofs and algorithms in publication-quality LaTeX
allowed-tools:
  - Bash
  - Read
  - Write
  - Edit
  - Glob
  - Grep
metadata:
  specialization: computer-science
  domain: science
  category: research-documentation
  phase: 6
---

# LaTeX Proof Formatter

## Purpose

Provides expert guidance on formatting theoretical CS proofs and algorithms in publication-quality LaTeX.

## Capabilities

- Algorithm pseudocode formatting (algorithmicx)
- Inference rule typesetting
- Proof environment formatting
- Theorem numbering and cross-references
- BibTeX integration
- Conference style compliance

## Usage Guidelines

1. **Structure**: Organize proof structure clearly
2. **Algorithms**: Format algorithms with algorithmicx
3. **Rules**: Typeset inference rules with mathpartir
4. **References**: Manage cross-references properly
5. **Style**: Conform to conference/journal style

## Tools/Libraries

- LaTeX
- algorithmicx
- mathpartir
- amsthm
- Overleaf

Overview

This skill formats proofs and algorithms into publication-quality LaTeX tailored for theoretical computer science and related fields. I provide ready-to-use LaTeX snippets, environment recommendations, and style guidance to make proofs, inference rules, and pseudocode look professional and conference-ready. The output balances correctness, readability, and compliance with common conference templates.

How this skill works

I analyze the input proof or algorithm structure and map components to appropriate LaTeX packages and environments (amsthm, algorithmicx, mathpartir, etc.). I produce formatted LaTeX code for theorems, lemmas, proofs, inference rules, and algorithms, plus suggestions for numbering, cross-references, and BibTeX integration. I can adapt the formatting to common conference styles and point out package conflicts or compilation pitfalls.

When to use it

  • Preparing a paper or appendix that contains formal proofs and requires consistent typesetting.
  • Converting handwritten or plain-text proofs into LaTeX-ready environments.
  • Formatting algorithm pseudocode for clarity and publication standards.
  • Typesetting inference rules or operational semantics using mathpartir.
  • Ensuring theorem numbering, cross-references, and citations follow a conference template.

Best practices

  • Start with a minimal working example and add packages incrementally to avoid conflicts.
  • Use amsthm for consistent theorem/lemma environments and provide custom \,theoremstyles sparingly.
  • Format algorithms with algorithmicx and customize keywords to match paper conventions.
  • Typeset inference rules with mathpartir and keep premises/conclusions compact for readability.
  • Name labels semantically (e.g., \label{thm:completeness}) and use \autoref or \cref for cross-referencing.

Example use cases

  • Convert a draft proof into a clean LaTeX proof environment with numbered lemmas and inline references.
  • Produce publication-ready pseudocode for an algorithm section using algorithmicx with custom indentation.
  • Typeset operational semantics or typing rules as aligned inference rules using mathpartir.
  • Adapt theorem and proof layouts to a specific conference class (IEEE, ACM, or LNCS) while preserving numbering.
  • Integrate bibliography entries and cite foundational lemmas correctly with BibTeX or BibLaTeX.

FAQ

Which LaTeX packages do you recommend?

Use amsthm for theorems, algorithmicx for pseudocode, mathpartir for inference rules, amsmath for math environments, and BibLaTeX/BibTeX for citations.

Can you adapt to a conference template?

Yes — I provide adjustments and warnings about package conflicts and show how to embed formatted proofs within common conference classes.