record
record
Take a code change, recover the prompt that produced it, and write a lesson the creator reads straight into the camera.
The lesson teaches the decisions, not the code. A viewer can get a file by file walkthrough from their own agent in ten seconds. Recorded minutes spent on one waste the only thing a human has and the agent does not.
Three things transfer to a different codebase. Why the change is shaped this way, what the alternative would have cost, and which rule got written down so the decision survives.
Here is the test. A creator opens the file after two weeks away from the code. They record, and they work through it without a pause to think.
Steps
Copy this checklist into your response and tick items off as you go. The verify step is the one that gets skipped, and skipping it puts unchecked claims in front of an audience.