Patterns

Once you have the foundations, these are the moves that turn an architecture into a clean, reusable flow. Work through them in order, or jump to the one you need.

• Design patterns — find the seams, then reuse each piece at the lightest level that solves it: link in/out, link call, subflow, or packaged node.
• Handling data — classify data by what it's for, treat telemetry and control on their own paths, pace fast inputs, and hold state and config in context.
• Good form — the habits that keep a flow readable and out of spaghetti: call shared things, decouple UI from logic, catch errors where you can see them.