Matt Pocock defines a prototype as throwaway code that answers a question. His /prototype skill makes a rough working artifact when a conversation alone cannot settle how something should look or behave. He uses it alongside specifications, despite the video’s more categorical title.
Choose the fidelity of the answer
A simple modal with confirm and cancel buttons may be easy to discuss. A modal that displays data under different conditions can be harder to picture. Pocock reaches for a prototype when he needs to see or feel an interaction, accepting more time and token use in exchange for a more concrete discussion.
In Wayfinder, his multi-session planning workflow, a prototype can be its own decision ticket. Its output becomes an asset for the later specification and implementation.
Three search designs, then a fourth
Pocock wants to search diagrams and their snapshots in his diagramming application. His first generated prototype offers three designs: grouped rows, a filter on the left, and an inline list. He likes the search box in A and the layout in C, but finds parts of each unsatisfactory.
He feeds those preferences back and gets a fourth version. He tests a search and clicks a result. The prototype is connected to the existing route, which he says makes the test more representative. He reports that this session used roughly 100,000 tokens before the next round of feedback.
He plans to retain the prototype on a throwaway branch, then hand it to an agent to implement properly, remove old prototype code and check the spec. Useful pieces can be reused, but a successful click is not proof that the feature is production-ready.
Beyond interface design
Pocock also suggests a small interactive terminal program for exercising difficult state-machine cases. A prototype can test logic as well as appearance. He credits Shape Up as an influence and keeps separate guidance for UI and logic prototypes in his skills repository.