agentleFS
Y-ASLantY-ASLant/ElegantClipboard/.agents/skills/gpui-kit-design-guides/SKILL.md

gpui-kit-design-guides

Skill493 starsChanged 9 days agoMITView on GitHub

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.

12 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions12 projects use a version of this.

    Word for word · 12

    1. AprilNEA/OpenLogi★ 26k100% same
    2. longbridge/gpui-kit★ 21k100% same
    3. longbridge/gpui-component★ 21k100% same
    4. vicanso/zedis★ 2.2k100% same
    5. since2006/shell-rs★ 844100% same
    6. feigeCode/onetcli★ 515100% same
    7. vibex-ai/vibex★ 245100% same
    8. StudentWeis/ropy★ 209100% same
    9. wsp-labs/wsp★ 15100% same
    10. Zingzy/wsp★ 15100% same

    2 more not listed

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the file is missing, fetch https://gpui-kit.com/docs/design-guides.md.

    line 13
  2. Very specific:

    Read the whole guide for a new screen or a redesign.

    line 19
  3. Very specific:

    Tokens before values: No raw hex or rgb(...); use cx.theme() semantic tokens and rem-based helpers.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.