gpui-kit
Skill515 starsChanged 47 days agoLicence not identifiedView on GitHub
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 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.
12 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- Y-ASLant/ElegantClipboardword for word, first seen Nov 9, 2026
- vibex-ai/vibexedited, first seen Nov 8, 2026
- MaraniMatias/Musterword for word, first seen Nov 1, 2026
- Zingzy/wspword for word, first seen Nov 1, 2026
- wsp-labs/wspword for word, first seen Nov 1, 2026
- 821869798/aitoolplusedited, first seen Oct 17, 2026
Other versions12 projects use a version of this.
Word for word · 8
- longbridge/gpui-kit★ 20k100% same
- longbridge/gpui-component★ 20k100% same
- vicanso/zedis★ 2.2k100% same
- Y-ASLant/ElegantClipboard★ 486100% same
- StudentWeis/ropy★ 203100% same
- wsp-labs/wsp★ 14100% same
- Zingzy/wsp★ 14100% same
- MaraniMatias/Muster★ 2100% same
Edited · 4
- AprilNEA/OpenLogi★ 25k94% same
- since2006/shell-rs★ 47694% same
- vibex-ai/vibex★ 7094% same
- 821869798/aitoolplus★ 484% same
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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- gpui-kit-design-guidesSkill
The file
We split this skill into the rules it gives an agent
9 rules. 4 are common, 0 are distinctive, and 5 are very specific to this project.
4
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.