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
- steipete/agent-scriptstheir own version, first seen Nov 14, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- tornikegomareli/Skillstheir own version, first seen Nov 8, 2026
- coco-research/cocotheir own version, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilltheir own version, first seen Nov 1, 2026
- spokvulcan/claude-code-build-ios-appstheir own version, first seen Oct 17, 2026
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.
eugenepyvovarovSkillswift-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
patrickserranoSkillapp-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
kingsidharthSkillswiftui-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
xfstudioSkillswiftui-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
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- openai/plugins★ 7.8ksame name
- steipete/agent-scripts★ 7.5ksame name
- Dimillian/Skills★ 4ksame name
- coco-research/coco★ 797same name
- FloWritesCode/fwc-swiftui-skills★ 418same name
- omarshahine/HomeClaw★ 194same name
- robinebers/skills★ 48same name
- eugenepyvovarov/mcpbundler-agent-skills-marketplace★ 12same name
- 199-biotechnologies/swiftui-claude-skills★ 7same name
- deonmenezes/mobile-app-skill★ 4same name
12 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 repository95 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- agent-memory-profilesSkill
- agent-messaging-gatewaySkill
- agent-session-checkpointsSkill
- agent-skill-migrationSkill
- ai-interaction-designSkill
- animation-craftSkill
- animation-vocabularySkill
- apple-designSkill
- apple-desktop-automationSkill
- approval-sandbox-policiesSkill
- atomic-designSkill
- better-colorsSkill
- better-typographySkill
- better-uiSkill
- browser-research-agentSkill
- codex-opsSkill
- competitive-intelSkill
- component-catalogSkill
- content-designSkill
- creative-rendering-auditSkill
- cron-agent-workflowsSkill
- dashboard-from-researchSkill
- data-synthesisSkill
- design-extractSkill
- design-measurement-and-experimentationSkill
- design-sandbox-proofSkill
- design-system-referenceSkill
- design-systemsSkill
- design-to-code-handoffSkill
- dialkitSkill
- docker-environmentsSkill
- emil-design-engSkill
- figma-auditSkill
- figma-code-connectSkill
- figma-create-fileSkill
- figma-design-systemsSkill
- figma-ds-rulesSkill
- figma-generate-designSkill
- figma-generate-librarySkill
- figma-implement-designSkill
- figma-library-builderSkill
- figma-plugin-apiSkill
- figma-prototypeSkill
- figma-syncSkill
- figma-useSkill
- figma-web-captureSkill
- find-animation-opportunitiesSkill
- flutter-genSkill
- gateway-ops-observabilitySkill
- hermes-agent-bridgeSkill
- hyperframes-videoSkill
- improve-animationsSkill
- information-architectureSkill
- interaction-designSkill
- interface-craft-gateSkill
- interview-researchSkill
- ios-app-intentsSkill
- ios-performance-debuggingSkill
- The first 60 shown.
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
- Distinctive: line 8
Use Liquid Glass as system chrome and interaction hierarchy, not as a decorative coating for every surface.
- Distinctive: line 14
Prefer system navigation, tab, toolbar, search, and button behavior before custom glass.
- Distinctive: line 19
Verify increased contrast, reduced transparency, reduced motion, Dynamic Type, dark appearance, and scrolling performance.
- Distinctive: line 23
Keep content legible without depending on the background image or color.
- Distinctive: line 24
Avoid stacking translucent layers.
- Distinctive: line 26
Use morphing identifiers only for a real hierarchy transition.
- Distinctive: line 28
Do not label June 2026 APIs as iOS 27 unless the checked Apple SDK documentation explicitly does so.
- Distinctive: line 30
Read references/review.md for the audit matrix and fallback pattern.
“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.
Files
SwiftUI Liquid Glass
Use Liquid Glass as system chrome and interaction hierarchy, not as a decorative coating for every surface.
Workflow
- Confirm the build SDK and minimum deployment target. Liquid Glass APIs require an iOS 26+ availability path.
- Identify the small set of controls or floating surfaces that need separation from content.
- Prefer system navigation, tab, toolbar, search, and button behavior before custom glass.
- Apply layout, shape, and content modifiers before the glass effect.
- Group nearby custom glass elements in
GlassEffectContainerso they render and morph coherently. - Mark glass interactive only when the element actually accepts input.
- Provide an earlier-OS fallback using native materials or standard controls, not a visual imitation that changes behavior.
- 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.
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.

