免费在 GitHub 公开

create-lecture

Create a new Beamer lecture `.tex` from source papers and materials, with notation consistency checks and the project's preamble wired in. Use when user says "create a lecture on X", "new lecture from these papers", "start a deck on topic Y", "scaffold a new Beamer file", "build me a lecture from these PDFs". Scaffolds the full deck — NOT for compiling existing `.tex` (use `/compile-latex`).

中文简介正在准备中。当前显示原文说明。

pedrohcgs/claude-code-my-workflow

查看安装方法

包含的文件（1）

SKILL.md5.1 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Lecture Creation Workflow

Create a beautiful, pedagogically excellent Beamer lecture deck.

This is a collaborative, iterative process. The instructor drives the vision; Claude is a thinking partner.

CONSTRAINTS (Non-Negotiable)

Read the knowledge base FIRST — notation registry, narrative arc, applications database
Every new symbol MUST be checked against the notation registry
Motivation before formalism — no exceptions
Worked example within 2 slides of every definition
Max 2 colored boxes per slide
No \pause or overlay commands (check project rules)
Transition slides at major conceptual pivots
Thread at least 1 running empirical application throughout
All citations verified against the bibliography
Work in batches of 5-10 slides — share for feedback, don't bulk-dump

WORKFLOW

Phase 0: Intake & Context (Pre-Flight Report required)

Read the inputs, then produce a Pre-Flight Report in your response before Phase 1 starts.

Inputs to read:

.claude/rules/knowledge-base-template.md — notation registry, narrative arc, applications
.claude/rules/content-invariants.md — INV-1..INV-8 govern slide content
Any source papers / existing slides the user provided
The previous lecture's .tex (last section + ending slide) if one exists

Required Pre-Flight Report block:

## Pre-Flight Report

**Sources read:**
- [source 1]: [one-line takeaway — what notation, what result, what diagram]
- [source 2]: ...

**Notation registry check:**
- New symbols this lecture will introduce: [list]
- Symbols reused from prior lectures: [list, with the lecture each was introduced in]
- Conflicts detected: [none / specific clashes]

**Narrative position:** [Where does this lecture sit in the course arc? What did the previous lecture end on? What does the next lecture need you to set up?]

**Pedagogical goal:** [one sentence]

**Running application:** [which real-world example threads through this deck]

State the pedagogical goal, get user confirmation, then proceed.

First-lecture fallback (fresh fork, empty knowledge base). If .claude/rules/knowledge-base-template.md still has unfilled placeholder tables (no notation registry entries, no applications, no prior lectures in Slides/), do NOT halt waiting for it. Instead:

Acknowledge the template is empty and we're creating the course's first lecture.
Propose a minimal starter knowledge base from the user's topic: 5-8 key symbols with conventions, 1-2 running applications, a short narrative arc (intro → main idea → implications). Present for approval.
Write the approved stub into the knowledge base template so subsequent lectures inherit it.
Continue to Phase 1.

This prevents /create-lecture from deadlocking for every new forker.

Phase 1: Paper Analysis (When Papers Provided)

Split into chunks, extract key ideas
Map paper notation → course notation
Identify slide-worthy content
Present summary for approval

Phase 2: Structure Proposal

Propose outline (5-Act or 3-Part template)
List TikZ diagrams and R figures needed
List new notation to introduce
GATE: User approves before Phase 3

Phase 3: Draft Slides (Iterative)

Work in batches of 5-10 slides
Check notation, apply creation patterns
Quality checks during drafting

Phase 4: Figures & Code

R scripts following conventions
TikZ diagrams in Beamer source (single source of truth)
Save RDS for future Quarto integration

Phase 5: Polish & Compile

Full 3-pass compilation
Run Devil's Advocate
Run Substance Review (if domain reviewer configured)
Update knowledge base with new notation

Post-Creation Checklist

[ ] Lecture compiles without errors
[ ] No overfull hbox > 10pt
[ ] All citations resolve
[ ] Every definition has motivation + worked example
[ ] Max 2 colored boxes per slide
[ ] 2-3 Socratic questions embedded
[ ] Transition slides between sections
[ ] At least 1 running application threaded throughout
[ ] New notation added to knowledge base
[ ] Session log updated
[ ] Devil's Advocate run

Cross-references

.claude/skills/translate-to-quarto/SKILL.md — port the finished Beamer deck to a Quarto RevealJS mirror.
.claude/skills/qa-quarto/SKILL.md — adversarial Beamer↔Quarto parity (loop-until-dry).
.claude/skills/deploy/SKILL.md — render + publish the lecture to GitHub Pages.
.claude/skills/scaffold-exercises/SKILL.md — problem sets + solutions to accompany the lecture.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

adjudicate-review

免费

Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel.

中文简介正在准备中。当前显示原文说明。