This is a structured approach to mapping interaction flows before you commit to visuals. It centers on breadboarding, a text notation from Shape Up that forces you to name places, affordances, and destinations explicitly. The discipline is in the edges: you're expected to design failure paths, empty states, and error conditions as required steps, not afterthoughts. It includes a set of techniques for different contexts (task analysis for redesigns, service blueprinting when backstage operations are involved) and clear rules like "every affordance has a named destination" and "no broken objects." If you're tired of flows that fall apart when someone hits the back button or loses connection, this gives you a checklist and notation to catch those gaps early.
npx skills add https://github.com/jamiemill/layers-skills --skill layers-interaction-flow