gum-forms-behaviors

What problem does it solve?

Gum's visual save model and the Forms behavioral layer are disconnected, which forces developers to set interaction and data defaults in code after project load. This Skill explains how behaviors declared in .behx/BehaviorSave files and ElementSave behavior references are mapped at load time to DefaultFromFileXxxRuntime types that instantiate Forms controls, and why many Forms properties cannot be set from the Gum editor.

Core Features & Use Cases

• Behavior model overview: Explains BehaviorSave, ElementBehaviorReference, and StandardFormsBehaviorNames and how behavior names are used to select runtime wrappers.
• Wrapping lifecycle: Describes FormsUtilities.RegisterFromFileFormRuntimeDefaults, the DefaultFromFileXxxRuntime AfterFullCreation pairing, and ReactToVisualChanged event flow.
• Property promotion gap: Identifies which common Forms properties (e.g., Button.Text, CheckBox.IsChecked, TextBox.Text, Slider range, ItemsControl items) have no VariableSave equivalent and recommends where to set defaults in code.
• Use case: Debugging why a component's designed visual appears but its interactive defaults (selection, text, checked state, min/max values) are missing until runtime.

Quick Start

Ask the AI to summarize how a specific component's Behaviors list maps to DefaultFromFileXxxRuntime classes and which Forms properties cannot be authored in the Gum editor.