Loading...
Loading...
Found 5 Skills
Build cross-platform desktop applications with Rust using Tauri framework and native GUI alternatives
Tauri framework for building cross-platform desktop applications with Rust backend and web frontend. Covers architecture, IPC commands, plugins, bundling, code signing, and security best practices. USE WHEN: user mentions "Tauri", "Rust desktop app", asks about "Tauri commands", "Tauri plugins", "Tauri IPC", "Rust + Svelte/React", "lightweight desktop app", "Tauri bundling", "Tauri security" DO NOT USE FOR: Electron applications - use `electron` skill instead
How to build desktop applications with GPUI Kit, the Rust framework published as the gpui-kit crate (GPUI plus gpui_kit::component, gpui_kit::base, gpui_kit::assets). Use when setting up a gpui-kit app, choosing or using a component (Button, Input, Select, Dialog, Sheet, Tabs, Sidebar, List, DataTable, Tree, Chart, etc.), handling component state, theming, or window overlays, and for GPUI mechanics: actions and keybindings, async tasks, contexts, custom elements, entities, events, focus, global state, layout and styling, ElementId, and tests. Holds the normative Coding Guides: read them before any architecture, state-ownership, public API, naming, or testing decision. Pairs with the gpui-kit-design-guides skill for the Design Guides.
Generates Rust code for GPUI desktop UI components following Zed editor patterns. Use when building desktop applications with gpui crate, creating themed UI components, implementing autocomplete/completions, building command palettes, or working with the gpui-component library. Covers RenderOnce components, Entity state management, theming with ActiveTheme, and Zed-style UI patterns.
Build, scaffold, refactor, debug, review, and visually validate production Rust desktop interfaces with GPUI. Use for setting up a production-ready GPUI starter app; new GPUI apps or components; Entity, Context, action, async, and lifecycle architecture; Apple-style macOS UI, Liquid Glass or translucent materials, motion, gestures, focus, keyboard, accessibility, text input, IME, clipboard, drag and drop, menus, multi-window behavior, and restoration; packaging, CI, performance, and testing work; or translating selected Paper.design frames into maintainable GPUI code with screenshot comparison. Covers published GPUI and pinned Zed revisions, macOS/Linux/Windows boundaries, narrow AppKit interop, and stability audits.