Teacher workflowlive

minionify

A teacher shouldn't re-type the same score into three systems. Prompts that let your own Claude Code build the tools, a live demo of what they do, and a calculator for the hours.

The classroom problem

An attendance note gets typed into the school’s system. A score goes into the gradebook, then into the class site, then gets checked against both. Comments, results from practice sites and posting the week’s work repeat the pattern. None of it is teaching, and it all happens before the first lesson or after the last one.

Every teacher has a list like this, and no two lists match. Each school’s systems are different too.

The design decision

The repo holds Markdown files and a license, no code. A teacher’s own Claude Code reads them and builds a tool on that teacher’s own computer, under that teacher’s own logins. Student names and grades stay on that computer.

Every tool follows four rules: it shows a preview first, it waits for the teacher’s confirmation, the school’s gradebook is written first, and student data is used only for the teacher’s own task. The first tool Claude builds only reads. Writing comes later.

Before anything gets built, the teacher asks their school for permission in writing and reads the terms of each system they use. The repo says plainly that it runs in the terminal, and a warning at the top tells anyone who has never used one to stop there. Software that collects what students do in order to sell a study guide serves the vendor, so these tools are built to do the opposite.

How it works

The live demo groups the tools into seven areas, each with sample sessions that show the preview, the confirmation and the check afterwards. Sample sessions use made-up students; no real names, grades or records appear on the page. A calculator turns a teacher’s own minutes into hours a week. The “by hand” times are mine. The “with Claude” times are estimates until they have been timed.

To build your own, a teacher installs Claude Code (it needs a paid Claude account or API credits), works through the school and terms checklists, and pastes the setup prompt into an empty folder. Claude then walks through the setup one click at a time and builds a read-only tool that lists the day’s classes. Starter prompts follow for attendance, grades, and posting to the class site.

It has not been tested with other teachers. The setup prompt has not been run start to finish on a clean computer.

Get the prompts on GitHub