prototypekit
prototypekit
Write code that answers one question; keep the answer, delete the code.
An image of a screen, or image options of one, is uikit mockup when installed; otherwise draw the image with whatever image tool is present. A question that documentation can settle is a research job, not a prototype. A demo request gets the bounce in No question, no prototype.
No question, no prototype
Before writing a line, state the question and the decision it unblocks, one sentence each. If you can't write both, there is nothing to prototype yet.
An ask that resolves to "build me a demo", "make a proof of concept for the client", or "just try something" is production work under a softer name. Bounce it once, naming the reason and the route: it wants a plan and a real build, not a throwaway.
If the user reaffirms, the ask converts, not the skill. Say plainly that this is production work, then do it as production work: no marker, no exclude entry, no disposal, and it stays on disk. prototypekit stops driving at that point. Never build a demo as a marked, disposed prototype: that hands someone a thing to show a client and then deletes it.
The six rules
Both modes obey these.