Gpui Kit Design Guides

OrganizationPopular

longbridge

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.

Overview

Publisher	longbridge
Repository	`gpui-kit`
Skill name	`gpui-kit-design-guides`
Stars	14.5K
Forks	891
Bundled files	1
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by longbridge on GitHub. Read the source before you install it.

Installation

Install the Gpui Kit Design Guides AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/longbridge/gpui-kit.git /tmp/gpui-kit
mkdir -p .claude/skills
cp -r /tmp/gpui-kit/skills/gpui-kit-design-guides .claude/skills/gpui-kit-design-guides

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gpui Kit Design Guides in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gpui Kit Design Guides on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gpui Kit Design Guides is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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):

Section	Read when
Design thesis	Always
Learning from Shadcn	Choosing what to borrow from web component libraries
Start from the task	Always; task hierarchy, interaction promise, what to leave out
Visual language	Color, typography, spacing, radius, borders, elevation, density, icons
Layout patterns	Window structure, sidebars, toolbars, panels, forms, resizable regions
Components and composition	Picking a component, composing parts, when to build a new one
Interaction states	Hover, focus, pressed, selected, disabled, loading, validation, danger
Feedback and overlays	Dialog, sheet, popover, menu, notification, tooltip, dismissal, focus
Motion	Any animation or transition
Designing data-heavy interfaces	Tables, lists, trees, dashboards, dense inspectors
Interface language	Any user-facing text: labels, buttons, titles, errors, empty states
Internationalization and platform fit	Multi-locale copy, Chinese terminology, macOS/Windows conventions
Guidance for AI-generated interfaces	Always when an agent produces UI
Accessibility checklist	Before finishing
Design review checklist	Before 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/design-guides.md46 KB

Frequently asked questions

What does the Gpui Kit Design Guides AI skill do?

Why use Gpui Kit Design Guides on TypingMind?

Because you install it once and use it with any model. Gpui Kit Design Guides is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gpui Kit Design Guides in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/longbridge/gpui-kit/tree/main/skills/gpui-kit-design-guides. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Gpui Kit Design Guides?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gpui Kit Design Guides?

As many as you like. As long as a model supports skills, you can use Gpui Kit Design Guides with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gpui Kit Design Guides AI skill free?

It is published on GitHub by longbridge. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagram

garrytan

CommunityPopular

Turn an English description (or mermaid source) into a diagram triplet: the source, an editable .excalidraw file you can open on excalidraw.com, and rendered SVG + PNG. (gstack)

Office Hours

YC Office Hours — two modes. (gstack)

Plan Design Review

Designer's eye plan review — interactive, like CEO and Eng review. (gstack)

Banner Design

Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner.…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

GPUI Kit Design Guides

How to read it

Non-negotiables

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now