agentleFS
jcm-developerjcm-developer/liquid-glass-components/agents/copilot-instructions.md

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.

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
  1. Distinctive:

    When generating UI components with a glass aesthetic:

    line 8
  2. Very specific:

    Never stack glass on glass.

    line 15
  3. Very specific:

    Never use will-change: backdrop-filter (causes iOS crashes) or animate backdrop-filter

    line 24
  4. Very specific:

    Never use border-image with border-radius (incompatible per spec)

    line 25
  5. Very specific:

    Never use mix-blend-mode on text over glass

    line 26

≈ “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.

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

Liquid Glass component guidelines (v2.1.0)

When generating UI components with a glass aesthetic:

Rules

  1. Low frost: backdrop-filter: blur(8px) saturate(180%) with the -webkit- prefix; never 20px+
  2. Specular light from two inset rim shadows (var(--glass-shadow-rim)), not a ::before mask border
  3. Real refraction: add data-refract and load liquid-glass.js (Chromium only); the component must look complete without it
  4. Glass ONLY on the navigation layer (tab bars, toolbars, sidebars, docks, modals, popovers, toasts, floating buttons), never on content
  5. Never stack glass on glass; controls inside glass use flat fills (.glass-btn--plain)
  6. Include accessibility fallbacks for:
    • prefers-reduced-transparency: reduce (with backdrop-filter: none !important)
    • prefers-reduced-motion: reduce
    • prefers-contrast: more
    • forced-colors: active
  7. Pressed controls grow (var(--glass-press-scale)); selections slide; linear() springs over 600ms
  8. Min font-weight 500 on glass surfaces
  9. At most 3 glass surfaces visible on a mobile viewport
  10. Never use will-change: backdrop-filter (causes iOS crashes) or animate backdrop-filter
  11. Never use border-image with border-radius (incompatible per spec)
  12. Never use mix-blend-mode on text over glass

See the project's skills/liquid-glass/snippets/tokens.css for design tokens.

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.