Prototype More

My typical workflow for larger tasks:research → interview me (grilling session) → generate a spec → tickets → implementationThere is some iteration and review along the way. Once implementation is completed, there is a final deep review, testing, cleanup, etc.But recently, I have started to work in an early prototype or two.Prototypes used to be expensive. You would build something that just about worked, confirm your assumptions, and then start fresh on the actual implementation[1]. It could take hours, days, or longer. There was no guarantee your time was not going to be wasted[2].Today, the cost of a prototype is next to zero and getting cheaper by the day. A good way to jump-start a prototype is with Claude Design. You can share some screenshots of the current state of affairs, explain what you are hoping to accomplish, etc. You can even have Claude Design propose a few alternative paths, but I have found taking the extra step and seeing it function in your own application and…