agentleFS
memi-designmemi-design/design-skills/skills/swiftui-liquid-glass/SKILL.md

swiftui-liquid-glass

Skill7 starsChanged 4 months agoMITView on GitHub

Adopt or audit iOS 26+ SwiftUI Liquid Glass with native APIs, correct availability fallbacks, restrained hierarchy, accessibility, and measured rendering performance.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use swift-concurrency-expert, app-store-changelog and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • eugenepyvovarovSkill

    swift-concurrency-expert

    Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

    Also in 6 projects that use this

  • patrickserranoSkill

    app-store-changelog

    Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.

    Also in 4 projects that use this

  • kingsidharthSkill

    swiftui-pro

    Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

    Also in 4 projects that use this

  • xfstudioSkill

    swiftui-expert-skill

    Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 8

    Distinctive

    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:

    Use Liquid Glass as system chrome and interaction hierarchy, not as a decorative coating for every surface.

    line 8
  2. Distinctive:

    Prefer system navigation, tab, toolbar, search, and button behavior before custom glass.

    line 14
  3. Distinctive:

    Verify increased contrast, reduced transparency, reduced motion, Dynamic Type, dark appearance, and scrolling performance.

    line 19
  4. Distinctive:

    Keep content legible without depending on the background image or color.

    line 23
  5. Distinctive:

    Avoid stacking translucent layers.

    line 24
  6. Distinctive:

    Use morphing identifiers only for a real hierarchy transition.

    line 26
  7. Distinctive:

    Do not label June 2026 APIs as iOS 27 unless the checked Apple SDK documentation explicitly does so.

    line 28
  8. Distinctive:

    Read references/review.md for the audit matrix and fallback pattern.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 22 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.

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

SwiftUI Liquid Glass

Use Liquid Glass as system chrome and interaction hierarchy, not as a decorative coating for every surface.

Workflow

  1. Confirm the build SDK and minimum deployment target. Liquid Glass APIs require an iOS 26+ availability path.
  2. Identify the small set of controls or floating surfaces that need separation from content.
  3. Prefer system navigation, tab, toolbar, search, and button behavior before custom glass.
  4. Apply layout, shape, and content modifiers before the glass effect.
  5. Group nearby custom glass elements in GlassEffectContainer so they render and morph coherently.
  6. Mark glass interactive only when the element actually accepts input.
  7. Provide an earlier-OS fallback using native materials or standard controls, not a visual imitation that changes behavior.
  8. Verify increased contrast, reduced transparency, reduced motion, Dynamic Type, dark appearance, and scrolling performance.

Guardrails

  • Keep content legible without depending on the background image or color.
  • Avoid stacking translucent layers.
  • Preserve system hit regions, focus, and semantic roles.
  • Use morphing identifiers only for a real hierarchy transition.
  • Profile repeated custom glass in scroll-heavy layouts.
  • Do not label June 2026 APIs as iOS 27 unless the checked Apple SDK documentation explicitly does so.

Read references/review.md for the audit matrix and fallback pattern.

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.