# Macos Liquid Glass

Implement and review macOS SwiftUI Liquid Glass UI.

- Repository: https://github.com/robinebers/openusage (4503 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add robinebers/openusage --skill macos-liquid-glass -g -a claude-code -y`
Codex: `npx skills add robinebers/openusage --skill macos-liquid-glass -g -a codex -y`
Cursor: `npx skills add robinebers/openusage --skill macos-liquid-glass -g -a cursor -y`
Gemini CLI: `npx skills add robinebers/openusage --skill macos-liquid-glass -g -a gemini-cli -y`

## Description

Implement and review macOS SwiftUI Liquid Glass UI. Use when adopting system glass, removing conflicting custom chrome, or building glass surfaces.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

1. Read the relevant scene or root view and identify the structural pattern:
   `NavigationSplitView`, `TabView`, sheet presentation, detail/inspector
   layout, toolbar, or custom floating controls.
2. 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.
3. Update standard SwiftUI structure and controls first.
4. Add custom `glassEffect` surfaces only for app-specific UI that standard
   controls do not cover.
5. Validate that glass grouping, transitions, icon treatment, and foreground
   activation are visually coherent and still usable with pointer and keyboard.
6. If the UI change also affects launch behavior for a SwiftPM GUI app, use
   `macos-build-run-debug` so the app runs as a foreground `.app` bundle rather
   than as a raw executable.

## App Structure

The rest: https://github.com/robinebers/openusage/blob/HEAD/.agents/skills/macos-liquid-glass/SKILL.md