math-beamer

Math Beamer

Build and audit mathematical Beamer decks that are meant to be presented, compiled, and traced back to source material. This skill covers mathematical slide structure, not generic slide decoration.

Use When

Use this skill when the user wants to:

• turn a mathematical paper, lecture note, proof sketch, experiment log, or theorem outline into a Beamer deck;
• revise an existing .tex Beamer project for mathematical clarity, source-grounded claims, or build reliability;
• select a reusable template for a seminar, reading group, defense, course, workshop, poster, or domain-specific math talk;
• audit theorem/proof/algorithm/formula/figure slides for notation, assumptions, overclaiming, and layout risks;
• build a Chinese, English, or bilingual mathematics deck with reproducible LaTeX commands.

Do not use this skill to invent results, prove unverified theorems, fabricate citations, or make institutional-branded templates public without checking license and logo rights.

Inputs

• Required: presentation goal, source packet, target audience, language, talk duration or slide count, and preferred output folder.
• Optional: existing Beamer source, bibliography, figures, data files, institutional style constraints, template choice, handout/poster mode, speaker notes, and compile command.

If the source packet is missing, produce a source request or an outline of needed evidence. Do not produce a full deck with unsupported claims.

Guided Interaction Contract

Default to guided mode unless the user explicitly requests autonomous execution or has already supplied an approved brief, template, outline, and sample direction.

• Work on one stage at a time. Ask only for decisions needed by the current stage.
• End every guided response with a checkpoint containing:
  • current stage;
  • what was completed;
  • the decision needed from the user;
  • available responses: approve, revise, reject, skip, or stop;
  • what will happen after approval.
• Do not interpret silence, a new attachment, or a general acknowledgement as approval for a later stage.
• A user may combine stages only by explicitly providing the decisions for each skipped checkpoint.