When you're designing anything of even moderate interface interactivity or complexity, state machines are a great way to help you manage that. I make these all the time, and they're remarkably useful little tools.↗

a quick opus 4.5 vibecoding tip ask claude to make state machine diagrams of existing components this causes it to map out all paths (which, it will default to being lazy otherwise) but also helps you verify if it's doing things correctly at a systems level↗