Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swiftui-liquid-glass100
Does it follow best practices?
Validation for skill structure
Multi-element glass container usage
GlassEffectContainer used
0%
100%
Container spacing set
0%
100%
glassEffect after layout modifiers
27%
81%
interactive() on tappable controls only
0%
81%
Static label NOT interactive
71%
100%
Consistent shapes
62%
87%
iOS 26 availability guard
100%
100%
Non-glass fallback provided
100%
100%
Native glass API used
100%
100%
Shape parameter specified
0%
0%
Without context: $0.2423 · 57s · 11 turns · 11 in / 3,943 out tokens
With context: $0.2731 · 55s · 14 turns · 15 in / 2,808 out tokens
Morphing glass transitions
@Namespace declared
0%
100%
glassEffectID used
0%
100%
Unique IDs per state
0%
0%
GlassEffectContainer wraps views
0%
100%
withAnimation on state toggle
100%
100%
glassEffect after layout modifiers
0%
100%
iOS 26 availability guard
100%
100%
Non-glass fallback provided
100%
100%
Native glass API used
0%
100%
Container spacing parameter set
0%
100%
Without context: $0.1780 · 40s · 9 turns · 10 in / 2,383 out tokens
With context: $0.3628 · 1m 9s · 15 turns · 17 in / 4,215 out tokens
Glass button styles and availability
glassProminent for primary button
0%
100%
glass style for secondary button
0%
100%
glassEffect on card surface
100%
100%
glassEffect after layout modifiers
100%
100%
Native API over custom blur
100%
100%
iOS 26 availability guard
100%
100%
Non-glass fallback provided
100%
100%
Card shape specified
100%
100%
Consistent button shapes
0%
100%
Glass tinting applied
0%
0%
Without context: $0.1619 · 38s · 8 turns · 9 in / 2,182 out tokens
With context: $0.2264 · 41s · 11 turns · 12 in / 2,298 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.