一键导入
beamer-slides-teaching
Generate LaTeX Beamer slide decks using my defined style and conventions. Use this skill whenever the user asks to create slides, a presentation, a lecture deck, or Beamer content — for teaching.
菜单
Generate LaTeX Beamer slide decks using my defined style and conventions. Use this skill whenever the user asks to create slides, a presentation, a lecture deck, or Beamer content — for teaching.
Use when creating a new `.Rmd` script in `Code/`, editing the `registry:` YAML block of an existing script in `Code/`, moving a `Code/*.Rmd` into `_Archive/`, or when the user says "update registry", "show registry", or "which script makes X". Before writing any new `Code/*.Rmd` script, read `Code/REGISTRY.md` first and surface existing matches before starting fresh. After any YAML change, run `Code/_Claude Scripts/build_registry.R` to refresh `Code/REGISTRY.md`.
End-of-milestone audit of a research project's `Code/` folder against the paper and outputs. Surfaces drift between scripts, YAML headers, the script registry, outputs, raw data, and the paper. Categorises findings as MUST-FIX or SUGGESTED and proposes fixes one at a time for the user to confirm. Use this skill when the user says "code sweep", "sweep the code", "run a code sweep", "audit my code folder", "check code freshness", "is everything up to date", "any stale outputs", "audit code consistency", or similar — typically before a paper submission, milestone, or share. Extends `script-registry`; reuses its `registry:` YAML block and `Code/_Claude Scripts/build_registry.R` builder rather than redefining either.
Per-project glossary of key definitions, abbreviations, and command-phrases, stored in `GLOSSARY.md` at the project root. Use this skill when the user defines or asks about a project-specific term — variable names, dataset or database names, acronyms — or sets up a command-phrase (a phrase that maps to an action, e.g. "push" = commit and push the paper to GitHub). Triggers include "add to glossary", "glossary: X means Y", "define X for this project", "what does X mean here", "what does X stand for", "from now on X means Y", "show the glossary", "what's in our glossary", and "remove X from glossary". Also use proactively: offer to capture a term when the user defines one in passing, or when you hit an undefined abbreviation or variable name in their code or data. Loaded at session start by `/spin-up` so command-phrases stay active.
Start-of-session orientation routine that briefs Claude on the current state of a project before work begins. Use this skill when the user says "spin up", "spin it up", "let's go", "start up", "spin up the project", "punch it chewy", or any variant signalling they want a session kickoff briefing. Performs: git status check (unpushed commits, remote divergence), CLAUDE.md and README read, most-recent session log read (focusing on "Where we left off"), PINBOARD.md open items, GLOSSARY.md load, and a short synthesis of project state. Ends by asking what to work on today.
Audit a finance paper against Alex Edmans' "Learnings From 1,000 Rejections" (2025, Financial Management) three-part framework: Contribution, Execution, Exposition. Reads the paper's current LaTeX, applies the framework with per-research-question execution checks, and generates a structured report with severity-labeled findings. Use when the user says "edmans audit", "audit my paper", "run the Edmans check", "referee readiness", "submission audit", "check paper against Edmans", or "pre-submission check".
Use this skill whenever working with the Canvas LMS REST API — including creating or updating modules, pages, and files for a course, building sync scripts, managing course structure programmatically, or uploading files and linking them in pages. Trigger this skill any time the user mentions Canvas, LMS, course sync, module pages, or file uploads to Canvas. Also use when writing or debugging any Python script that calls the Canvas API.
| name | beamer-slides-teaching |
| description | Generate LaTeX Beamer slide decks using my defined style and conventions. Use this skill whenever the user asks to create slides, a presentation, a lecture deck, or Beamer content — for teaching. |
fontspec — it is incompatible with pdfLaTeX\usepackage[T1]{fontenc} and \usepackage{lmodern} for fontsUse the standard preamble from assets/uts-beamer-preamble.tex as a starting
point. The basic structure is:
\documentclass[aspectratio=169]{beamer}
\usetheme{Madrid}
\usecolortheme{whale}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage{booktabs}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{amsmath}
\title{Title Here}
\author{Author Name}
\institute{University of Technology Sydney \\ Faculty of Business}
\date{\today}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\begin{frame}{Outline}
\tableofcontents
\end{frame}
% Content sections and frames here
\end{document}
\begin{itemize} sparingly — prefer short declarative statements
or a single key claim followed by supporting evidenceAlways use booktabs for tables in slides:
\begin{frame}{Summary Statistics}
\begin{table}
\centering
\small
\begin{tabular}{lccc}
\toprule
Variable & Mean & Std. Dev. & N \\
\midrule
ROA & 0.045 & 0.089 & 12{,}340 \\
Leverage & 0.312 & 0.201 & 12{,}340 \\
Firm Size & 7.21 & 1.84 & 12{,}340 \\
\bottomrule
\end{tabular}
\end{table}
\end{frame}
Use \small or \footnotesize for tables to fit slides. Use {,} for
thousand separators in numbers.
Tag every discussion question with its Bloom's taxonomy level in a LaTeX comment so the instructor can gauge cognitive demand at a glance:
\begin{frame}{Discussion}
% [Bloom: Evaluate]
\textbf{Question:} A mining company's CEO argues that voluntary ESG
reporting is sufficient and mandatory disclosure would harm competitiveness.
\vspace{0.5em}
Evaluate this claim in light of the ASX Corporate Governance Council's
``if not, why not'' approach. What are the strengths and weaknesses of
each model?
\end{frame}
Bloom's levels: Remember → Understand → Apply → Analyse → Evaluate → Create. Aim for a mix across a lecture, with more weight on the upper levels.
Structure case study material as: Context → Tension → Question
\begin{frame}{Enron: The Gatekeepers}
% Context
Arthur Andersen served as both auditor and consultant to Enron,
earning \$52M in fees in 2000 alone.
\vspace{0.5em}
% Tension
The dual relationship created a financial incentive to preserve the
client relationship at the expense of audit independence.
\vspace{0.5em}
% Question — [Bloom: Analyse]
\textbf{What structural features of the audit market enabled this
conflict, and how have post-SOX reforms addressed them?}
\end{frame}
When slides cover corporate governance topics, reference these frameworks where relevant:
Always contextualise Australian governance comparatively — note how the principles-based "if not, why not" approach differs from rules-based regimes (e.g., SOX in the US).
When generating MCQs for teaching, follow these conventions:
\begin{frame}{Quick Check}
Under the ASX CGC Principles, a listed company that does not comply
with a recommendation must:
\begin{enumerate}[(a)]
\item Pay a fine to ASIC
\item Explain why it has not complied in its annual report
\item Seek shareholder approval for the non-compliance
\item Delist from the ASX within 12 months
\end{enumerate}
\vspace{0.5em}
\textit{Answer: (b)}
\end{frame}
\only<2> overlay
to reveal it on clickBefore generating any slide deck, read references/slide-rhetoric.md for
principles on narrative structure, information hierarchy, and slide design.
Apply these principles to every deck.