What problem does it solve? Writing ViewModels by hand means repetitive INotifyPropertyChanged plumbing, RelayCommand boilerplate, and collection-change wiring. This Skill guides the use of VeloxDev's compile-time source generators so a partial class with attributes produces all of that automatically — and it documents the silent failure modes (missing partial, no diagnostics emitted) that otherwise leave developers guessing why nothing was generated. ## Core Features & Use Cases - Observable properties with [VeloxProperty]: Generate notifying properties from fields or partial properties, with (oldValue, newValue) change callbacks, naming rules, and automatic collection-change hooks for INotifyCollectionChanged types. - Commands with [VeloxCommand]: Generate lazily-cached IVeloxCommand members from Task/void methods, with cancellation tokens, semaphore-based concurrency, CanExecute validation, and a full lifecycle event set. - MVVM framework interop: The generator detects CommunityToolkit.Mvvm, Prism, ReactiveUI, and Caliburn.Micro and routes the setter through the host framework's notification mechanism. - [MonoBehaviour] frame loop: Give any POCO a Unity-style Awake/Update/FixedUpdate lifecycle on a background channel via MonoBehaviourManager. - Use Case: You are building a WPF or Avalonia workflow editor and need a node ViewModel with observable slots, an async save command with cancellation, and collection hooks — write a partial class with three attributes instead of hundreds of lines of plumbing. ## Quick Start Ask the AI to write a partial C# ViewModel class using VeloxDev's [VeloxProperty] for an observable property and [VeloxCommand] for an async command with cancellation.
