What problem does it solve? Building Rust desktop UIs with the gpui-component library requires knowing dozens of component APIs, state ownership patterns, theming rules, and desktop interaction conventions; this Skill supplies the component catalog, setup patterns, and normative design and coding guides so generated code follows the library's real APIs instead of invented ones. ## Core Features & Use Cases - Component Catalog & API Lookup: Maps UI needs to the right component (Button, Input, Select, Dialog, DataTable, Tree, Charts, etc.) with import paths, stateful vs stateless usage, and links to per-component documentation. - Normative Design Guides: Enforces desktop-first rules for hierarchy, spacing tokens, density, alignment, interaction states, overlays, and interface copy. - Normative Coding Guides: Governs crate architecture, RenderOnce vs Entity state ownership, ElementId stability, theming via cx.theme() tokens, focus handling, and public API naming conventions. - Use Case: When asked to add a settings panel to a GPUI app, the Skill directs the agent to use Form fields with Input/Select state entities, semantic theme tokens, rem-based spacing, and correct dialog focus restoration rather than improvised web-style markup. ## Quick Start Use the gpui-component skill to build a settings dialog with a text input, a select dropdown, and primary and cancel buttons in my GPUI application.