agentleFS
podopodo/design-agent-skills/skills/liquid-glass-skill/SKILL.md

liquid-glass-skill

Skill32 starsChanged 6 months agoMITView on GitHub

Deep knowledge of Apple's Liquid Glass design system (iOS 26+/macOS 26+): .glassEffect() modifier, .buttonStyle(.glass), GlassEffectContainer, platform-specific implementations, migration from existing apps, and common pitfalls with tested solutions.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    License: no LICENSE file in the upstream repo <!-- das:install:end -->

    line 62

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

liquid-glass-skill

Catalogue stub — full skill: haider-nawaz/liquid-glass-skill

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? Upstream names this skill liquid-glass, so it installs next to this pointer (the pointer is not replaced).
    • Global: f=~/.agents/skills/liquid-glass/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/liquid-glass/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as liquid-glass, invoke it and proceed
    • pointer → go to step 2
  2. Detect scope, then install:

    [ -e ~/.agents/skills/liquid-glass-skill ] && echo "global" || echo "project"

    Global:

    npx skills add haider-nawaz/liquid-glass-skill --skill liquid-glass -g -y

    Project:

    npx skills add haider-nawaz/liquid-glass-skill --skill liquid-glass -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add haider-nawaz/liquid-glass-skill
/plugin install liquid-glass@liquid-glass-skills

Heads-up

  • License: no LICENSE file in the upstream repo
<!-- das:install:end -->

Invoke after install

  • Skill name: liquid-glass
  • Plugin route only: the /liquid-glass:liquid-glass command
  • Trigger phrases: "Liquid Glass", "iOS 26 design", "glassEffect", "GlassEffectContainer"

What it does

Provides comprehensive knowledge of Apple's Liquid Glass material system introduced in iOS 26 and macOS 26. Covers the SwiftUI .glassEffect() view modifier, .buttonStyle(.glass) for interactive elements, GlassEffectContainer for grouping glass surfaces, morphing transitions, glass toolbars and tab bars, platform-specific behavioral differences between iOS, macOS, tvOS, and visionOS, a step-by-step migration workflow for apps upgrading from pre-26 designs, and a catalogue of known pitfalls (performance, layering, contrast) with tested solutions. The skill ships API, migration, platform and pitfall reference files plus code patterns from Apple's Landmarks sample.

When NOT to use

  • Apps targeting iOS versions before iOS 26 — Liquid Glass APIs are unavailable
  • Android or cross-platform design — use mobile-app-design instead
  • General SwiftUI patterns beyond Liquid Glass — use swiftui-claude-skills or swiftui-patterns

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.