ワンクリックで
build-deck
Create and compile Beamer presentations following the Rhetoric of Decks philosophy. Use when making seminar or conference slides.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Create and compile Beamer presentations following the Rhetoric of Decks philosophy. Use when making seminar or conference slides.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create a new empirical research project: generates projects/<name>/ with latex, code, scripts, results, literature, and guidance subfolders plus README.md and project-level CLAUDE.md.
Publication-ready figure conventions for empirical finance and economics. Covers matplotlib styling, color palettes, export settings, and common figure types (time series, decile bars, coefficient plots, event studies). Auto-apply when creating any figure, plot, or visualization.
Agent-driven cold-start onboarding. Use the repo shell entrypoint to find or install Python 3.11+, then run the shared bootstrap audit/plan/apply flow and configure WRDS only if the user has it.
Compile LaTeX to PDF using pdflatex + bibtex cycle
Creates new Claude Code skills, auto-apply skills, or auto-trigger rules, or audits existing ones for quality and effectiveness.
Clean and fix .tex files -- strip comments, fix compilation errors, verify section markers
| name | build-deck |
| description | Create and compile Beamer presentations following the Rhetoric of Decks philosophy. Use when making seminar or conference slides. |
Create, edit, and compile academic presentations for seminars, conferences, and working sessions.
/build-deck -- start a new deck (asks audience/tone questions first)/build-deck decks/seminar.tex -- compile an existing deck/build-deck --working -- create a working deck for coauthors (denser, more detail)Before creating or significantly editing a deck, ask:
Question 1: Who is the audience?
- External -- Seminar, conference, discussant role (sparse, performative, one idea per slide)
- Working -- Coauthors, internal meeting (detailed, documentary, preserves uncertainty)
Question 2: What's the visual tone?
- Professional/Academic -- Use the house palette (navy/crimson/forest)
- Colorful/Expressive -- Design something unique for this specific deck
These determine density and visual style. If the user specifies --working, skip Question 1 (answer is Working).
Before building, internalize the rules from .claude/rules/presentation-rules.md. The key principles:
Create the .tex file in the project's decks/ directory (create if needed):
decks/
+-- seminar.tex # Main Beamer file
+-- seminar.pdf # Compiled output
\documentclass[aspectratio=169,11pt]{beamer}
\usetheme{default}
\usecolortheme{default}
% --- Strip navigation chrome ---
\setbeamertemplate{navigation symbols}{}
\setbeamertemplate{footline}{%
\hfill\insertframenumber/\inserttotalframenumber\hspace*{4pt}\vspace{2pt}%
}
% --- House palette ---
\definecolor{navy}{HTML}{1A365D}
\definecolor{darkgray}{HTML}{2D3748}
\definecolor{crimson}{HTML}{9B2335}
\definecolor{forest}{HTML}{276749}
\definecolor{steel}{HTML}{4A5568}
\definecolor{lightgray}{HTML}{F7FAFC}
\definecolor{warmgray}{HTML}{E2E8F0}
% --- Beamer colors ---
\setbeamercolor{frametitle}{fg=navy,bg=white}
\setbeamercolor{title}{fg=navy}
\setbeamercolor{subtitle}{fg=steel}
\setbeamercolor{author}{fg=darkgray}
\setbeamercolor{date}{fg=steel}
\setbeamercolor{normal text}{fg=darkgray}
\setbeamercolor{itemize item}{fg=steel}
\setbeamercolor{itemize subitem}{fg=steel!60}
\setbeamercolor{alerted text}{fg=crimson}
\setbeamercolor{block title}{fg=white,bg=navy}
\setbeamercolor{block body}{fg=darkgray,bg=lightgray}
% --- Fonts ---
\setbeamerfont{frametitle}{series=\bfseries,size=\large}
\setbeamerfont{title}{series=\bfseries,size=\Large}
% --- Custom commands ---
\newcommand{\emphnum}[1]{\textcolor{crimson}{\textbf{#1}}}
\newcommand{\goodnum}[1]{\textcolor{forest}{\textbf{#1}}}
\newcommand{\transitionslide}[1]{%
{\setbeamercolor{background canvas}{bg=navy}
\begin{frame}[plain]
\centering\vfill
{\color{white}\LARGE\bfseries #1}
\vfill
\end{frame}}
}
\newcommand{\takeaway}[1]{%
\begin{center}
\colorbox{warmgray}{\parbox{0.88\textwidth}{\centering\vspace{4pt}%
\color{navy}\bfseries #1\vspace{4pt}}}
\end{center}
}
% --- Packages ---
\usepackage{booktabs}
\usepackage{tikz}
\usepackage{graphicx}
\usepackage{amsmath,amssymb}
| Color | Purpose | Command |
|---|---|---|
crimson | Emphasis, alerts, pre-cost/gross values | \emphnum{0.82\%} |
forest | Positive outcomes, post-cost/net values | \goodnum{0.33\%} |
navy | Headers, section transitions, primary branding | -- |
steel | Secondary text, captions | -- |
darkgray | Body text | -- |
warmgray | Takeaway box background | \takeaway{...} |
Results slide with assertion title:
\begin{frame}{Transaction costs halve momentum alpha}
\centering
\begin{tabular}{lccc}
\toprule
& Gross & Net & Cost (\%) \\
\midrule
UMD & \emphnum{0.65\%} & \goodnum{0.31\%} & 52\% \\
\bottomrule
\end{tabular}
\vspace{1em}
\small The assertion is in the title. The table is evidence.
\end{frame}
Transition slide:
\transitionslide{Main Results}
ZERO TOLERANCE FOR WARNINGS.
Use the pdflatex path from canonical local state reported by tools/bootstrap.py audit (or a repo-root CLAUDE.local.md compatibility shim if present):
cd {decks_dir} && pdflatex -interaction=nonstopmode {file}.tex
pdflatex -interaction=nonstopmode! (fatal)Do not consider the deck finished until compile is completely clean.
After clean compile, review the deck against these criteria:
DECK BUILD REPORT
=================
File: {decks_dir}/{name}.tex
Status: SUCCESS / FAILED
Slides: N
Warnings: 0 (must be zero)
Errors: 0
Output: {decks_dir}/{name}.pdf
Project-specific narrative arcs belong in each project's
CLAUDE.md. Below are generic templates.