liquid-glass
Skill2k starsChanged 15 days agoApache-2.0View on GitHub
Implement and review macOS SwiftUI Liquid Glass UI. Use when adopting system glass, removing conflicting custom chrome, or building glass surfaces.
14 other projects use a version of this, 1 of them edited.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- axot/agent-skillstheir own version, first seen Nov 16, 2026
- jcm-developer/liquid-glass-componentstheir own version, first seen Nov 16, 2026
- admos98/liquid-glass-suitetheir own version, first seen Nov 15, 2026
- MMACABRE/SKILLSedited, first seen Nov 8, 2026
- charlie947/reel-editing-skillstheir own version, first seen Nov 1, 2026
- yichen08092025/liquid-glasstheir own version, first seen Oct 25, 2026
Who's talking about lingyired/status-trio
- robinebers/openusage“feat(menu-bar): add dual-arc Gauge and Color Gauge icon styles for 5h/7d limits”GitHub · Nov 6, 2026
- wudanyang6/wudanyang6.github.io“软件分享:status-trio”GitHub · Sep 16, 2026
- ruanyf/weekly“【开源自荐】Status Trio: 将 iPhone Duo 的三合一状态图标带到 macOS”GitHub · Sep 13, 2026
The biggest 3 of 3 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions14 projects use a version of this.
Word for word · 1
- openai/plugins★ 7.8k100% same
Edited · 1
- MMACABRE/SKILLS★ 194% same
Wrote their own version · 12
- skopevoj/spoti.pw★ 732same name
- eylonshm/claude-meter★ 15same name
- patrickserrano/skills★ 13same name
- heyparsadev/liquid-glass-skill★ 11same name
- charlie947/reel-editing-skills★ 9same name
- jcm-developer/liquid-glass-components★ 4same name
- YordiLorenzo/liquid-glass-skills★ 3same name
- IntelliHelper/agent-skills★ 1same name
- admos98/liquid-glass-suite★ 0same name
- axot/agent-skills★ 0same name
2 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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- background-ui-testingSkill
- brainstormingSkill
- diagnosing-superpowersSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- gitee-release-syncSkill
- github-actions-efficiencySkill
- macos-auto-updateSkill
- macos-buildSkill
- macos-notch-uiSkill
- macos-patternsSkill
- macos-releaseSkill
- macos-settings-uiSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- swift-testing-proSkill
- swiftui-proSkill
- swiftui-ui-patternsSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- ui-ux-pro-maxSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
37 rules. 0 are common, 14 are distinctive, and 23 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
23
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to bring a macOS SwiftUI app into the modern macOS design system with the least custom chrome possible.
- Distinctive: line 15
Prefer system-provided glass and adaptive materials over bespoke blur, opaque backgrounds, or custom toolbar/sidebar skins.
- Very specific: line 21
Read the relevant scene or root view and identify the structural pattern: NavigationSplitView, TabView, sheet presentation, …
- Distinctive: line 24
Remove custom backgrounds or darkening layers behind system sheets, sidebars, and toolbars unless the product explicitly needs them.
- Distinctive: line 27
Update standard SwiftUI structure and controls first.
- Very specific: line 28
Add custom glassEffect surfaces only for app-specific UI that standard controls do not cover.
- Very specific: line 32
If the UI change also affects launch behavior for a SwiftPM GUI app, use build-run-debug so the app runs as a foreground .app bundle rather …
- Very specific: line 38
Prefer NavigationSplitView for hierarchy-driven macOS layouts.
- Distinctive: line 43
Keep inspectors visually associated with the current selection and avoid giving them a heavier custom background than the content they …
- Very specific: line 45
If the app uses tabs, keep TabView for persistent top-level sections and preserve each tab's local navigation state.
- Distinctive: line 47
Do not force iPhone-only tab bar minimize/accessory behavior onto a Mac app.
- Very specific: line 49
If a sheet already uses presentationBackground purely to imitate frosted material, consider removing it and letting the system's new …
- Very specific: line 59
Use ToolbarSpacer to communicate grouping:
- Very specific: line 62
Use sharedBackgroundVisibility when an item should stand alone without the shared glass background, for example a profile/avatar item.
- Very specific: line 64
Add badge to toolbar item content for notification or status indicators.
- Distinctive: line 68
If content underneath a toolbar has extra darkening, blur, or custom background layers, remove them before judging the new automatic …
- Very specific: line 79
When search is secondary and a compact affordance is better, use searchToolbarBehavior instead of hand-rolling a toolbar button and a …
- Distinctive: line 91
Prefer standard SwiftUI controls before creating custom glass components.
- Very specific: line 95
Use buttonBorderShape when a button shape needs to be explicit.
- Very specific: line 96
Use controlSize to preserve density in inspectors and popovers, and reserve extra-large sizing for truly prominent actions.
- Distinctive: line 98
Use the system glass and glass-prominent button styles for primary actions instead of recreating a translucent button background by hand.
- Very specific: line 104
Use Label or standard control initializers for menu items so icons are consistently placed on the leading edge across platforms.
- Very specific: line 112
Use glassEffect for custom glass surfaces.
- Very specific: line 116
Add tint only when color carries meaning, such as a status or call to action.
- Very specific: line 118
Use glassEffect(... .interactive()) for custom controls or containers with interactive elements so they scale, bounce, and shimmer like …
- Very specific: line 123
Use glassEffectID with a local @Namespace when matching glass elements should morph between collapsed and expanded states.
- Distinctive: line 146
Do not rebuild system sidebars, toolbars, sheets, or controls from scratch if standard SwiftUI APIs already provide the modern macOS …
- Very specific: line 148
Do not apply custom opaque backgrounds behind a NavigationSplitView sidebar, system toolbar, or sheet just because an older version needed …
- Very specific: line 151
Do not scatter related glass elements across multiple GlassEffectContainers.
- Distinctive: line 153
Do not tint every icon or glass surface for visual variety alone.
- Distinctive: line 154
Do not assume an iPhone tab/search behavior is the right answer on macOS.
- Distinctive: line 155
Prefer desktop-native toolbar, split-view, and inspector placement.
- Distinctive: line 156
Do not leave a GUI SwiftPM app launching as a bare executable when reviewing Liquid Glass behavior.
- Very specific: line 162
Use swiftui-patterns when the main question is scene architecture, sidebar/detail layout, commands, or settings rather than Liquid …
- Very specific: line 165
Use view-refactor when the main issue is file structure, state ownership, and extracting large views before design changes.
- Very specific: line 167
Use appkit-interop when the design requires window, panel, responder-chain, or AppKit-only control behavior.
- Very specific: line 169
Use build-run-debug when you need to launch, verify, or inspect logs for the app after the visual update.
“Common” is measured: kept by at least 6 in 10 of the 12 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
Liquid Glass
Overview
Use this skill to bring a macOS SwiftUI app into the modern macOS design system with the least custom chrome possible. Start with standard app structure, toolbars, search placement, sheets, and controls, then add custom Liquid Glass only where the app needs a distinctive surface.
Prefer system-provided glass and adaptive materials over bespoke blur, opaque backgrounds, or custom toolbar/sidebar skins. Audit existing UI for extra fills, scrims, and clipping before adding more effects.
Workflow
- Read the relevant scene or root view and identify the structural pattern:
NavigationSplitView,TabView, sheet presentation, detail/inspector layout, toolbar, or custom floating controls. - Remove custom backgrounds or darkening layers behind system sheets, sidebars, and toolbars unless the product explicitly needs them. These can obscure Liquid Glass and interfere with the automatic scroll-edge effect.
- Update standard SwiftUI structure and controls first.
- Add custom
glassEffectsurfaces only for app-specific UI that standard controls do not cover. - Validate that glass grouping, transitions, icon treatment, and foreground activation are visually coherent and still usable with pointer and keyboard.
- If the UI change also affects launch behavior for a SwiftPM GUI app, use
build-run-debugso the app runs as a foreground.appbundle rather than as a raw executable.
App Structure
- Prefer
NavigationSplitViewfor hierarchy-driven macOS layouts. Let the sidebar use the system Liquid Glass material instead of painting over it. - For hero artwork or large media adjacent to a floating sidebar, use
backgroundExtensionEffectso the visual can extend beyond the safe area without clipping the subject. - Keep inspectors visually associated with the current selection and avoid giving them a heavier custom background than the content they inspect.
- If the app uses tabs, keep
TabViewfor persistent top-level sections and preserve each tab's local navigation state. - Do not force iPhone-only tab bar minimize/accessory behavior onto a Mac app. On macOS, prefer a conventional top toolbar and native tab/search placement.
- If a sheet already uses
presentationBackgroundpurely to imitate frosted material, consider removing it and letting the system's new material render. - For sheet transitions that should visually originate from a toolbar button, make the presenting item the source of a navigation zoom transition and mark the sheet content as the destination.
Toolbars
- Assume toolbar items are rendered on a floating Liquid Glass surface and are grouped automatically.
- Use
ToolbarSpacerto communicate grouping:- fixed spacing to split related actions into a distinct group,
- flexible spacing to push a leading action away from a trailing group.
- Use
sharedBackgroundVisibilitywhen an item should stand alone without the shared glass background, for example a profile/avatar item. - Add
badgeto toolbar item content for notification or status indicators. - Expect monochrome icon rendering in more toolbar contexts. Use
tintonly to convey semantic meaning such as a primary action or alert state, not as pure decoration. - If content underneath a toolbar has extra darkening, blur, or custom background layers, remove them before judging the new automatic scroll-edge effect.
- For dense windows with many floating elements, tune the content's scroll-edge
treatment with
scrollEdgeEffectStyleinstead of building a custom bar background.
Search
- For a search field that applies across a whole split-view hierarchy, attach
searchableto theNavigationSplitView, not to just one column. - When search is secondary and a compact affordance is better, use
searchToolbarBehaviorinstead of hand-rolling a toolbar button and a separate field. - For a dedicated search page in a multi-tab app, assign the search role to one
tab and place
searchableon theTabView. - Make most of the app's content discoverable from search when the field lives in the top-trailing toolbar location.
- On iPad and Mac, expect the dedicated search tab to show a centered field above browsing suggestions rather than a bottom search bar.
Controls
- Prefer standard SwiftUI controls before creating custom glass components.
- Expect bordered buttons to default to a capsule shape at larger sizes. On macOS, mini/small/medium controls preserve a rounded-rectangle shape for denser layouts.
- Use
buttonBorderShapewhen a button shape needs to be explicit. - Use
controlSizeto preserve density in inspectors and popovers, and reserve extra-large sizing for truly prominent actions. - Use the system glass and glass-prominent button styles for primary actions instead of recreating a translucent button background by hand.
- For sliders with discrete values, pass
stepto get automatic tick marks or provide specific ticks in aticksclosure. - For sliders that should expand left and right around a baseline, set
neutralValue. - Use
Labelor standard control initializers for menu items so icons are consistently placed on the leading edge across platforms. - For custom shapes that must align concentrically with a sheet, card, or
window corner, use a concentric rectangle shape with the
containerConcentriccorner configuration instead of guessing a radius.
Custom Liquid Glass
- Use
glassEffectfor custom glass surfaces. The default shape is capsule-like and text foregrounds are automatically made vibrant and legible against changing content underneath. - Pass an explicit shape to
glassEffectwhen a capsule is not the right fit. - Add
tintonly when color carries meaning, such as a status or call to action. - Use
glassEffect(... .interactive())for custom controls or containers with interactive elements so they scale, bounce, and shimmer like system glass. - Wrap nearby custom glass elements in one
GlassEffectContainer. This is a visual correctness rule, not just organization: separate containers cannot sample each other's glass and can produce inconsistent refraction. - Use
glassEffectIDwith a local@Namespacewhen matching glass elements should morph between collapsed and expanded states.
Review Checklist
- Standard structures and controls were updated first before adding custom glass.
- Opaque backgrounds, dark scrims, and custom toolbar/sheet fills that fight the system material were removed unless intentionally required.
searchableis attached at the correct container level for the intended search scope.- Toolbar grouping uses
ToolbarSpacer,sharedBackgroundVisibility, andbadgeinstead of one-off hand-built chrome. - Icon tint is semantic, not decorative.
- Custom glass elements that sit near each other share a
GlassEffectContainer. - Morphing glass transitions use
glassEffectIDwith a namespace and stable identity. - Any SwiftPM GUI app used to test the result is launched as a
.appbundle, not as a raw executable.
Guardrails
- Do not rebuild system sidebars, toolbars, sheets, or controls from scratch if standard SwiftUI APIs already provide the modern macOS behavior.
- Do not apply custom opaque backgrounds behind a
NavigationSplitViewsidebar, system toolbar, or sheet just because an older version needed one. - Do not scatter related glass elements across multiple
GlassEffectContainers. - Do not tint every icon or glass surface for visual variety alone.
- Do not assume an iPhone tab/search behavior is the right answer on macOS. Prefer desktop-native toolbar, split-view, and inspector placement.
- Do not leave a GUI SwiftPM app launching as a bare executable when reviewing Liquid Glass behavior; missing foreground activation can make a design bug look like a rendering bug.
When To Use Other Skills
- Use
swiftui-patternswhen the main question is scene architecture, sidebar/detail layout, commands, or settings rather than Liquid Glass-specific treatment. - Use
view-refactorwhen the main issue is file structure, state ownership, and extracting large views before design changes. - Use
appkit-interopwhen the design requires window, panel, responder-chain, or AppKit-only control behavior. - Use
build-run-debugwhen you need to launch, verify, or inspect logs for the app after the visual update.
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.

