Case study 6 · Process
A rule-based pipeline for about 200 course documents
As a math teacher I built two full courses alone. A rules file, a required check-and-compile step and a log of corrections kept about 200 documents consistent.
2full courses built alone (Algebra 1 and 2)
~200documents, teacher and student versions counted separately
Claude Code · LaTeX · Windows
Problem
At Trilogy School I built the Algebra 1 and Algebra 2 courses on my own, from the opening pre-assessment to the unit tests, plus electives. That is a lot of documents that must look the same and be right.
Design
- A rules file defined document structure, formatting, file names, and a required check-and-compile step before any file was saved.
- Each correction went into a shared memory file, to keep the same mistake out of later documents.
- I checked problems and answer keys before anything reached students, and kept separate teacher and student versions of key lessons.
- The AI ran on a separate virtual disk with restricted file access, so it could not make uncontrolled changes to the rest of the computer.
Rules file
structure, formatting, file names
structure, formatting, file names
→
Draft
lesson, project or test
lesson, project or test
→
Check and compile
required before saving
required before saving
→
Teacher review
problems and answer keys
problems and answer keys
→
Correction log
read before the next document
read before the next document
Results
About 200 lessons, projects and tests across Algebra 1, Algebra 2 and the electives, most with a short summary for teachers.
Built with Claude Code: I set the goal, wrote the rules and the checks, and decided what counts as done; Claude Code wrote the code and the tests; a second model reviewed them.