liquid-glass-components / agents
Copilot instructions4 starsChanged 27 days agoMITView on GitHub
Liquid Glass design system for refractive, accessible glass UI components
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,397 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository5 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- liquid-glassSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When generating UI components with a glass aesthetic:
- Very specific: line 15
Never stack glass on glass.
- Very specific: line 24
Never use will-change: backdrop-filter (causes iOS crashes) or animate backdrop-filter
- Very specific: line 25
Never use border-image with border-radius (incompatible per spec)
- Very specific: line 26
Never use mix-blend-mode on text over glass
≈ “Common” is an estimate: at least 1 in 5 of the 3,854 Copilot instructions 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.
Files
Liquid Glass component guidelines (v2.1.0)
When generating UI components with a glass aesthetic:
Rules
- Low frost:
backdrop-filter: blur(8px) saturate(180%)with the-webkit-prefix; never 20px+ - Specular light from two inset rim shadows (
var(--glass-shadow-rim)), not a::beforemask border - Real refraction: add
data-refractand loadliquid-glass.js(Chromium only); the component must look complete without it - Glass ONLY on the navigation layer (tab bars, toolbars, sidebars, docks, modals, popovers, toasts, floating buttons), never on content
- Never stack glass on glass; controls inside glass use flat fills (
.glass-btn--plain) - Include accessibility fallbacks for:
prefers-reduced-transparency: reduce(withbackdrop-filter: none !important)prefers-reduced-motion: reduceprefers-contrast: moreforced-colors: active
- Pressed controls grow (
var(--glass-press-scale)); selections slide;linear()springs over 600ms - Min font-weight 500 on glass surfaces
- At most 3 glass surfaces visible on a mobile viewport
- Never use
will-change: backdrop-filter(causes iOS crashes) or animatebackdrop-filter - Never use
border-imagewithborder-radius(incompatible per spec) - Never use
mix-blend-modeon text over glass
See the project's skills/liquid-glass/snippets/tokens.css for design tokens.
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.

