LaTeX Cheat Sheet

LaTeX cheat sheet with real commands and snippets for setup, core workflows, debugging, and production-safe automation patterns. If you are working across tools, pair this with the Markdown Cheat Sheet and JSON Cheat Sheet.

Setup and Validation

Goal: Run formatters and linters for content files

# Format project files when formatter is available
npx prettier -w . || true

# Lint Markdown/YAML/JSON if linters exist
npx markdownlint-cli2 '**/*.md' || npx yaml-language-server --help || true

# Search for TODO placeholders before publish
rg "TODO|TBD" .

Core Patterns

Goal: Use a production-safe snippet

\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{amsmath}

\begin{document}
\section{Cheat Sheet Example}
Inline math: $E = mc^2$.

Display math:
\[
  \int_0^1 x^2 \, dx = \frac{1}{3}
\]
\end{document}

Automation and CI

Goal: Add validation step to CI pipeline

# Run strict shell mode in CI
set -euo pipefail

# Validate syntax and formatting in one pass
npx prettier -c .

# Fail build if broken references exist
rg "](/[^)]+)" src/content -n

Debugging and Troubleshooting

Goal: Track parse failures quickly

# Use ripgrep to isolate malformed syntax
rg "{{|}}|<[^>]*$" src -n

# Print files with potential encoding issues
file -I src/content/sheets/*.md

# Re-run formatter with explicit parser
npx prettier --parser markdown src/content/sheets/*.md || true

Common Gotchas

• Keep LaTeX content valid and machine-readable for build pipelines.
• Avoid trailing commas or comments in strict JSON files.
• Use consistent heading depth to keep TOC generation stable.
• Prefer explicit encoding (UTF-8) for portability.
• Run formatter checks before committing content edits.

Related Sheets

• Markdown Cheat Sheet — daily Markdown commands and production-ready examples.
• JSON Cheat Sheet — daily JSON commands and production-ready examples.
• Kotlin Cheat Sheet — daily Kotlin commands and production-ready examples.