liquid-glass
Skill1 starsChanged 2 months agoMITView on GitHub
IntelliHelper Liquid Glass design system — chrome vs content layers, frosted surfaces, themes (mono, aurora, sunset, frost, ocean), glass primitives, and visual polish. Use when styling glass UI, choosing button variants, building toolbars vs CTAs, setting themes, or fixing washed-out/over-saturated glass. Triggers: "liquid glass", "glassmorphism", "frosted glass", "chrome layer", "glass-bar", "theme mono aurora", "glass button variant".
11 other projects use a version of this.
Adopted by
Most recently taken up by
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- charlie947/reel-editing-skillstheir own version, first seen Nov 1, 2026
- yichen08092025/liquid-glasstheir own version, first seen Oct 25, 2026
- axot/agent-skillstheir own version, first seen Oct 21, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- heyparsadev/liquid-glass-skilltheir own version, first seen Oct 11, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- openai/plugins★ 7.8ksame name
- skopevoj/spoti.pw★ 732same name
- eylonshm/claude-meter★ 15same name
- patrickserrano/skills★ 13same name
- heyparsadev/liquid-glass-skill★ 11same name
- charlie947/reel-editing-skills★ 9same name
- YordiLorenzo/liquid-glass-skills★ 3same name
- MMACABRE/SKILLS★ 1same name
- axot/agent-skills★ 0same name
- shekhsahebali/ux-ux-skills★ 0same name
1 more not listed
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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-componentSkill
- compose-uiSkill
- intellihelper-uiSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
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
- Very specific: line 25
Call MCP list_themes for theme IDs and descriptions.
- Very specific: line 26
Call get_component for the real variant / size / shape APIs — do not invent them.
- Distinctive: line 27
Ensure project CSS loads tokens/themes (init + docs: https://ui.intellihelper.in/getting-started).
- Very specific: line 43
Prefer these over custom backdrop-blur one-offs:
- Distinctive: line 81
Always re-check exports and prop names via MCP before shipping.
- Distinctive: line 90
Contrast: verify light/dark on frosted surfaces (audit checklist).
- Distinctive: line 91
Motion: prefer existing component transitions over custom bounce everywhere.
“Common” is measured: kept by at least 6 in 10 of the 10 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.
Files
Liquid Glass design system
IntelliHelper UI is a two-layer glass language:
| Layer | Role | Feel | Typical components / variants |
| Chrome | Toolbars, icon controls, navigation chrome, secondary actions | Neutral, frosted, Apple mini-player | outline, secondary, ghost, glass; glass-bar, glass-icon-button |
| Content | Primary CTAs, marketing panels, destructive emphasis | Theme-saturated, expressive | primary, destructive; glass-content-card |
Rule of thumb: chrome stays quiet so content and data stay legible. One saturated CTA per region is usually enough.
Before styling
- Call MCP
list_themesfor theme IDs and descriptions. - Call
get_componentfor the realvariant/size/shapeAPIs — do not invent them. - Ensure project CSS loads tokens/themes (init + docs: https://ui.intellihelper.in/getting-started).
Themes
| ID | Label | Character |
mono | Mono Basic | Pure black/white foundational minimal |
aurora | Cool Aurora | Deep navy + cyan-violet accents |
sunset | Warm Sunset | Amber-coral + rose-gold glass |
frost | Neutral Frost | Icy slate, crystalline |
ocean | Deep Ocean | Teal depths + aqua accents |
Themes drive CSS variables used by glass utilities. Prefer theme tokens over ad-hoc hex for surfaces, borders, and glow.
Glass system components
Prefer these over custom backdrop-blur one-offs:
| Component | Use |
glass-bar | Neutral capsule for grouped media / chrome controls |
glass-icon-button | Circular icon-only chrome actions |
glass-content-card | Expressive saturated content panels under chrome |
background-picture-picker | Mesh/gradient/upload backgrounds for glass stages |
component-preview | Live preview + source (docs/playground style) |
card | Frosted panels for chrome and content layouts |
Install (web): npx @intellihelper/cli@latest add glass-bar glass-icon-button card -y
Install (native): npx @intellihelper/cli@latest add @native/glass-bar @native/glass-icon-button @native/card -y
Button language (verify with get_component)
Typical button variants in the design system:
| Variant | Layer | Use |
default / glass | Chrome-ish frosted | Default frosted control |
outline / secondary / ghost | Chrome | Neutral toolbars, secondary actions |
primary | Content | Main CTA |
destructive | Content | Destructive CTA |
link | Material | Text link, no glass chrome |
Shapes commonly include rounded, pill, rectangular. Sizes: default, sm, lg, icon.
// Chrome toolbar
<Button variant="outline" size="icon"><Settings /></Button>
<Button variant="ghost">Cancel</Button>
// Content CTA
<Button variant="primary">Continue</Button>
<Button variant="destructive">Delete</Button>Always re-check exports and prop names via MCP before shipping.
Visual quality bar
Ship interfaces that feel intentional:
- Hierarchy: one primary action; chrome supports, content leads.
- Density: pick comfortable (
gap-6/p-6) or compact (gap-4/p-4) per page — do not mix randomly. - Radius: stay consistent with component shapes; avoid stacking many different radii.
- Contrast: verify light/dark on frosted surfaces (audit checklist).
- Motion: prefer existing component transitions over custom bounce everywhere.
- Icons: Lucide at consistent sizes (
size-4/h-4 w-4).
Anti-patterns
- Glass on every surface (noise, illegible text)
- Saturated primary chrome on icon toolbars
- Nested glass cards three levels deep
- Random gradients + glow competing with theme
- Ignoring
focusRing/ keyboard focus styles - Using playground internal imports (
@intelli/ui,@intelli/ui-native,@intelli/utils) in consumer apps
Progressive disclosure
- Layer details & pairing → references/layers.md
- Theme setup notes → references/themes.md
- Page recipes → skill
compose-ui - Install path → skill
add-component
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.