What problem does it solve?
Porting a Gum Forms theme from its code-only C# implementation into a self-contained Gum project that the Add Forms dialog can import is full of silent failure modes: unnamespaced components that overwrite each other, stale staged build output, fonts that silently fall back, and recolors that pass every structural check while rendering wrong. This Skill encodes the correct sequencing and verification steps to avoid those landmines.
Core Features & Use Cases
- Theme Porting Workflow: A step-ordered process for cloning an existing theme tree, building the Styles component, recoloring, and wiring every state to Styles swatches.
- Namespacing Rules: Explains how to prefix qualified names across .gumx references, BaseType attributes, VariableReferences, and behavior DefaultImplementation so multiple themes can coexist in one project.
- Verification Guidance: Distinguishes structural checks (gumcli check, check-references, diff-standards) from real behavioral verification via GumProjectFontGenerator, gumcli screenshot, and diffing staged build output.
- Use Case: When adding a new Forms theme (e.g. porting a code-only theme like DarkPro into Templates/FormsThemes), follow this Skill to avoid duplicate-import bugs, stale FontCache entries, and silently skipped postbuild copies.
Quick Start
Use the gum-forms-theme-import skill to port a new code-only Forms theme into a tool-content theme under Templates/FormsThemes and verify it imports correctly through Add Forms.