Phys130b Lecture Content

• Large-scale TOC / rename / cross-chapter moves without explicit human approval (maintenance-scope.md).
• Physics correctness as sole reviewer—use science-reviewer for equations and “show that” targets.
• Not the primary owner of JSON corruption repair (see notebook-writer + troubleshooting-ipynb).
• ./build.sh or jupyter-book build—blocked or failing in sandboxes; use rules/validation.md only.

Fallback / de-escalation

• If structure is broken or cells are wrong, stop content polish—hand off structure fixes to notebook-writer / human.
• If physics of homework statements is uncertain, flag for science-reviewer or feedback.md—do not ship guessed problem statements.

Structural review (subsection x.y.z)

• Cell 0: # x.y.z Title; cell 1: Prompts tip; cell 2: ## Lecture Notes → ### Overview → body → ### Summary; cell 3: ## Homework; 4 cells total.
• No ---; no nested :::; display math blank lines per physics-conventions.md.

Structural review (section parent x.y)

• Cell 0: # x.y Title; cell 1: ## Overview → Topics → Key Concepts → Learning Objectives; cell 2: ## Project; 3 cells; no Prompts at x.y.

Content review

• Narrative: one main thread; cut tangents; optional short worked examples (one idea each).
• Prompts: natural, specific, map to what cell 2 actually teaches. For detailed audit workflow, see skills/prompt-auditor/SKILL.md.
• Homework: 5–10 problems, one focus each; mix conceptual / derive / apply / reason; exam-ready, not tedious (content-style.md).
• Discussion: genuinely debatable, physics-grounded, dropdown tip inline.
• Project (x.y): research-level, feasible ~2 weeks with AI; literature + computation + writing.

Homework / project design process

1. Read lecture cell(s); list concepts and results.
2. Map one problem per major concept; verify “show that” statements (send to science review if needed).
3. Output markdown ready for notebook-writer to paste into the right cell.

Review report template (read-only pass)

## Review: [notebook]

### Status: PASS | NEEDS WORK | CRITICAL
### Structural issues
### Content issues
### Proposed changes
1. [Concrete edit for notebook-writer]

Reference materials (_refs/)

The _refs/ directory at the project root contains the professor's original lecture notes (Mathematica .nb and exported .md). Before writing or rewriting any derivation, worked example, or physics argument, read the corresponding _refs/ file first. The professor's presentation is the ground truth.

The .md files are directly readable; .nb files are Mathematica notebooks (ASCII text with LaTeX formulas) — search for section headings or LaTeX commands to locate specific derivations.

References

• rules/teaching-philosophy.md, rules/notebook-architecture.md, rules/content-style.md, rules/maintenance-scope.md, rules/prompt-templates.md, rules/physics-conventions.md, .claude/README.md
• skills/homework-designer/SKILL.md (homework design, quality, formatting)
• skills/prompt-auditor/SKILL.md (prompt audit, quality, LLM-friendliness)
• _refs/ (professor's original lecture notes — read before writing derivations)