← ClaudeAtlas

liquid-glass-motionlisted

Animation, morphing, and shader best practices for Liquid Glass and SwiftUI motion on iOS 26+/macOS 26+ through iOS 27. Use when animating glass or building UI motion: glassEffectID, @Namespace morphing, GlassEffectContainer spacing, glassEffectUnion, glassEffectTransition (.matchedGeometry/.materialize), withAnimation, springs, UnitCurve, PhaseAnimator, KeyframeAnimator, @Animatable, matchedTransitionSource, navigationTransition zoom, scrollTransition, visualEffect, Metal shaders (colorEffect, distortionEffect, layerEffect, [[stitchable]]), accessibilityReduceMotion gating, Instruments/xctrace profiling of hangs and animation hitches. Also fires on symptoms: glass morph not animating, view pops in instead of morphing, glass fades instead of materializing, morph flickers with Reduce Motion, menu glass morphs as a rectangle, animation runs on insert but not removal, PhaseAnimator loops forever or fires once, shader shows clipped edges (maxSampleOffset), animation hitches or main-thread hangs while scrolling gl
YordiLorenzo/liquid-glass-skills · ★ 7 · Web & Frontend · score 68
Install: claude install-skill YordiLorenzo/liquid-glass-skills
# Liquid Glass — motion, animation, and shaders Companion to the **liquid-glass** skill (`~/.claude/skills/liquid-glass/`). Same tag system: `[verified]` / `[apple]` / `[multi]` / `[single]` / `[version-pinned]` — see that skill's SKILL.md. Composed 2026-08 and verified against Apple documentation and SDK interfaces. ## Operating rules 1. Before generating code, ALWAYS read the availability firewall in the companion **liquid-glass** skill (installed alongside this one): `references/availability-and-sdk27.md`. Motion code trips the same SDK-27 breakages (`.if` ban, `@ContentBuilder`, renames). 2. Load references on demand via the router — one topic, one file. 3. The motion model: Liquid Glass and its motion were designed together. Glass does not fade — it materializes by modulating lensing; when glass grows, its material gets thicker (deeper shadow, stronger lensing). Size change is a material change, which is why morphs must be the system animation, never hand-faked. 4. Verify motion claims against `references/` before repeating them — circulating write-ups get several of these facts wrong; the corrected facts live in these files. 5. Profiling evidence beats reasoning: record an Instruments trace with `xctrace` before optimizing, and never trust the iOS Simulator for the SwiftUI instrument — see `references/performance-and-instrumentation.md`. ## Hard rules (the short list) 1. Never animate glass with `.opacity` / fades — use `glassEffectTransi