MCPInstall

gpui-kit-design-guides

The normative Design Guides for GPUI Kit desktop applications. Read in full before designing or changing any screen, layout, spacing, visual hierarchy, color, density, component choice, interaction state, overlay, motion, data-heavy view, or interface copy in a GPUI Kit (gpui-kit / gpui-component) application, and before reviewing UI work for design quality. Also use when asked what the design rules are, or whether a UI decision follows them.

Installs
992
Last 24h
+16
Trending rank
#6850
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/longbridge/gpui-kit --skill gpui-kit-design-guides
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads gpui-kit-design-guides automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

GPUI Kit Design Guides

The guide is references/design-guides.md. It is a requirement, not inspiration. Read the guide file itself before doing UI work. Do not answer from this page, from an existing screen in the codebase, or from training data.

If the file is missing, fetch https://gpui-kit.com/docs/design-guides.md. The guide is a verbatim copy of that page, so its link to ./coding-guides.md means the Coding Guides in the gpui-kit skill (or https://gpui-kit.com/docs/coding-guides.md).

How to read it

Read the whole guide for a new screen or a redesign. For a narrow change, read "Design thesis" and "Start from the task" first, then the section for the change. Sections, in order (grep -n '^## ' references/design-guides.md):

SectionRead when
Design thesisAlways
Learning from ShadcnChoosing what to borrow from web component libraries
Start from the taskAlways; task hierarchy, interaction promise, what to leave out
Visual languageColor, typography, spacing, radius, borders, elevation, density, icons
Layout patternsWindow structure, sidebars, toolbars, panels, forms, resizable regions
Components and compositionPicking a component, composing parts, when to build a new one
Interaction statesHover, focus, pressed, selected, disabled, loading, validation, danger
Feedback and overlaysDialog, sheet, popover, menu, notification, tooltip, dismissal, focus
MotionAny animation or transition
Designing data-heavy interfacesTables, lists, trees, dashboards, dense inspectors
Interface languageAny user-facing text: labels, buttons, titles, errors, empty states
Internationalization and platform fitMulti-locale copy, Chinese terminology, macOS/Windows conventions
Guidance for AI-generated interfacesAlways when an agent produces UI
Accessibility checklistBefore finishing
Design review checklistBefore finishing; run every item against the work

Non-negotiables

A floor, not a substitute for the guide.

  • Desktop before web convention. Keyboard access, window chrome, menus, dense data views, resizable regions, persistent navigation.
  • Button vs Link. Button for every in-app command, ghost or outline when it should read quietly. Link only for external URLs and email addresses.
  • Tokens before values. No raw hex or rgb(...); use cx.theme() semantic tokens and rem-based helpers. Any spacing number quoted in the guide is the current default scale, not a literal to repeat.
  • State must be visible. Hover, focus, selection, disabled, loading, validation, and destructive states each need distinct, consistent treatment.
  • Overlays. Escape dismisses the topmost surface and returns focus to its trigger.
  • Copy. Name the object and the verb: Delete "Roadmap"? with a Delete button, not Are you sure? with OK.

Finish by running the Design review checklist against the work.

FAQ

What does the gpui-kit-design-guides skill do?

The normative Design Guides for GPUI Kit desktop applications. Read in full before designing or changing any screen, layout, spacing, visual hierarchy, color, density, component choice, interaction state, overlay, motion, data-heavy view, or interface copy in a GPUI Kit (gpui-kit / gpui-component) application, and before reviewing UI work for design quality. Also use when asked what the design rules are, or whether a UI decision follows them.

How do I install gpui-kit-design-guides?

Run npx skills add https://github.com/longbridge/gpui-kit --skill gpui-kit-design-guides in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/gpui-kit-design-guides/ (personal) or .claude/skills/gpui-kit-design-guides/ (project).

Which AI agents can use gpui-kit-design-guides?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is gpui-kit-design-guides safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains gpui-kit-design-guides?

It is published by longbridge in longbridge/gpui-kit. It has 992 recorded installs.

More from longbridge/gpui-kit

View all →

gpui-kit

longbridge/gpui-kit

How to build desktop applications with GPUI Kit, the Rust framework published as the gpui-kit crate (GPUI plus gpuikit::component, gpuikit::base, gpuikit::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 including UI integration testing. 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.

gpui

longbridge/gpui-kit

Open the skill to read its SKILL.md instructions.

334 installs

gpui-layout-and-style

longbridge/gpui-kit

Open the skill to read its SKILL.md instructions.

Frontend & Design319 installs

gpui-async

longbridge/gpui-kit

Open the skill to read its SKILL.md instructions.

298 installs

gpui-component

longbridge/gpui-kit

Open the skill to read its SKILL.md instructions.

Frontend & Design295 installs

gpui-context

longbridge/gpui-kit

Open the skill to read its SKILL.md instructions.

286 installs

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs