explain-backOpt-in only, never automatic: quiz the user with 3-5 questions on a gt-visualize explainer's seams, one at a time, comparing each answer with the story and the vault; --diff limits it to scenes a diff touches. Use when the user says: explain-back, quiz me on the explainer, test my understanding of t
gt-visualizeShow a codebase in 3D: EXPLAIN, a scroll-driven walkthrough of how its parts work together, or CODE CITY, files as buildings sized by lines and coloured by language or churn. One offline HTML file, publishable after a scrub gate and the user's yes. Use when the user says: explain how this codebase w
tourWalk a newcomer through a gt-visualize explainer scene by scene, with a prediction pause before each reveal and step into or over at any scene; progress resumes in a later session. Use when the user says: tour the explainer, walk me through the explainer, step through the explainer scenes, resume th
traceRun one gt-visualize explainer scene forward hop by hop, with a prediction pause before each reveal, grounded in a real test when one exists (else a labelled STATIC walkthrough). Use when the user says: trace this scene, trace this part, follow the hops, trace the request path through the explainer,
whatisAnswer what one part of a gt-visualize explainer does, at its own altitude, from its note, its scenes and the vault, then offer step into, out or over. Use when the user says: what is this part, what does this part do, whatis, what is this box in the explainer, where does this part sit in the explai