Which command, when
The toolkit is a handful of small pipelines that hand off to each other. This is the map: pick by what you're about to do, follow the arrows, then see which pipeline dispatches what. Every command links to its full field guide.
Pick by what you're doing
Find the row that matches the work in front of you. The command on the right is the one to reach for; the note underneath is what people grab by mistake.
/module-build — overkill for one page./cleanup-light — it will escalate anyway./change-heavy, not /cleanup-light.
The common sequences
Each pipeline hands off to the next. Follow the arrows; tap any command to open its guide.
The daily loop
Bookend every session so the system, not your memory, holds the standard.
A new module, end to end
The build locks a spec; the sprint walks each page through the trio, with a lock between each stage; then the pre-ship sweep.
Clearing the backlog
Group first, then feed each batch into the right change pipeline.
Changing existing code
Size the change first. Small ones can escalate; big ones start heavy.
Pre-ship a module
Audits are diagnostic; the findings route to the fixer.
Pairing notes
Where the commands overlap, and how they divide the work between them.
the-adjudicator is a referee, not a step you run
/change-heavy, /cleanup-light, /page-code, /page-implement, and /module-audit all dispatch it to mark critiques KEEP / DITCH / MODIFY. Run it directly only to triage feedback you already have.
/module-sprint orchestrates the page trio
During a sprint you rarely invoke /page-design, /page-code, or /page-implement yourself — the sprint does, with a lock between each. Use them standalone for one-off page work.
/cleanup-light self-escalates
If a "small" cleanup turns out to touch more than its scope, it hands off to /change-heavy rather than plowing ahead.
/cluster-fus feeds the change pipelines
It doesn't fix anything itself. It groups the backlog so you can batch like with like, then hand each batch to a change pipeline.
Audits are diagnostic; /page-implement is the fixer
/module-audit and /mobile-audit never auto-fix. They produce findings you route to /page-implement.
/pre-commit-check and /end-session both touch commits
/pre-commit-check is the truth-and-scope gate before a commit; /end-session writes the handoff and makes the session's commit. Run the check first.
What dispatches what
The pipelines on the left fan out to the agents, skills, and sub-commands on the right. Teal is another command in the toolkit; the rest are agents and skills.
These commands are installable
Get the toolkit
Every command on this page ships as a Claude Code plugin. Add the marketplace, install the pipelines, and run the same standard on your own repo.
/plugin marketplace add fire-farmer/red-line-toolkit