gum-forms-default-visuals

Document Gum Forms default visual classes, styling, and initialization.

597|79|Updated Mar 11, 2015
One-click install
npx skills add https://github.com/vchelaru/Gum --skill gum-forms-default-visuals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gum-forms-default-visuals
Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/gum-forms-default-visuals
Command: npx skills add https://github.com/vchelaru/Gum --skill gum-forms-default-visuals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a clear, concise guide to the code‑only visual classes that back Gum Forms controls, especially when customizing or debugging default visuals.

Core Features & Use Cases

  • Two‑generation overview: Explains legacy V1 Default*Runtime visuals and modern V2+ *Visual classes, including the V3 variants.
  • Construction pattern details: Describes the step‑by‑step initialization (child runtimes, state categories, styling pull, control attachment) for V2+ visuals.
  • Initialization flow: Clarifies how GumService.Initialize() registers defaults and how project‑based defaults can override them.
  • Styling centralization: Documents Styling.cs constants for colors, nine‑slice textures, icons, and text configurations.
  • Naming conventions: Lists required child names (e.g., "TextInstance", "FocusIndicator") that Forms controls expect.
  • Key file map: Provides a quick reference table of the most important source files related to default visuals.

Quick Start

Load the gum‑forms‑default‑visuals reference and ask how to build a custom visual for a new Forms control.

Frequently Asked Questions about gum-forms-default-visuals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom code-only visuals for Gum Forms controls?

Custom Gum Forms visuals are built by creating *Visual classes that initialize child runtimes, define state categories, pull from Styling.cs, and attach to Forms controls using specific naming conventions like "TextInstance".

What is the difference between legacy Default*Runtime and modern *Visual classes in Gum?

Gum Forms legacy V1 visuals used Default*Runtime classes, while modern V2+ and V3 variants use *Visual classes that support centralized styling and a structured construction pattern for better control customization.

How does GumService.Initialize() handle default visual registration?

GumService.Initialize() registers default visual classes during startup, but project-based defaults can override them to apply custom styling and visual components to your Forms controls.

What child component names do Gum Forms controls expect for visual styling?

Gum Forms controls expect specific child names like "TextInstance" and "FocusIndicator" to properly bind visual elements and apply centralized styling constants from Styling.cs.

Where are colors and textures defined for Gum Forms default visuals?

Gum Forms default visuals centralize their colors, nine-slice textures, icons, and text configurations in the Styling.cs constants file for consistent application across all visual classes.

Can I override default Gum Forms templates without modifying the core source files?

Yes, you can override default Gum Forms templates by registering project-based defaults through GumService.Initialize(), allowing custom *Visual classes to replace the built-in visuals without changing core files.