What problem does it solve? Building an interactive node-graph workflow editor in .NET requires correctly using VeloxDev's source-generated component model, undoable command stack, canvas coordinate math, and compiled execution engine — where small mistakes (a missing partial, a skipped InitializeWorkflow(), a mutated geometry getter) compile cleanly and then silently misbehave. ## Core Features & Use Cases - Model authoring: Create Tree, Node, Slot, and Link ViewModels with [WorkflowBuilder] attributes, declare slots with [VeloxProperty], and implement node behaviour in NodeHelper<T>.ReceiveAsync. - Graph execution: Compile a graph with CompilerViewModel and run it forward from a controller or backward as a reverse probe against a target node, with routers, joins, and sequential fan-out. - View scaffolding and customization: Generate the seven canvas view roles with dotnet new template packs for WPF, Avalonia, WinUI, MAUI, WinForms, Razor, or Jalium, and extend the library at its intended seams (custom link types, connection validation, variable port sets, new GUI adapters). - Use Case: Add VeloxDev.Core and VeloxDev.WPF to a WPF app, scaffold the views with dotnet new wpf-v-tree, write a node whose helper returns a computed payload, then compile and run the chain and verify dragging, connecting, and zooming at 40%. ## Quick Start Ask the AI to scaffold a VeloxDev workflow editor in your .NET project by adding the right NuGet packages, generating the canvas views with the dotnet new template pack, and writing a node ViewModel and helper that compute and return a value.
