Fetches axiom-liquid-glass-ref from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-liquid-glass-ref
Restart Cursor to activate axiom-liquid-glass-ref. Access via /axiom-liquid-glass-ref in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Migrating from previous materials (blur effects, custom translucency)
Ensuring accessibility compliance with Liquid Glass interfaces
Reviewing search, navigation, or organizational component updates
Related Skills
Use axiom-liquid-glass for implementing the Liquid Glass material itself and design review pressure scenarios
Use axiom-swiftui-performance for profiling Liquid Glass rendering performance
Use axiom-accessibility-diag for accessibility testing
Overview
Adopting Liquid Glass doesn't mean reinventing your app from the ground up. Start by building your app in the latest version of Xcode to see the changes. If your app uses standard components from SwiftUI, UIKit, or AppKit, your interface picks up the latest look and feel automatically on the latest platform releases.
Key Adoption Strategy
Build with latest Xcode SDKs
Run on latest platform releases
Review changes using this reference
Adopt best practices incrementally
Visual Refresh
What Changes Automatically
Standard Components Get Liquid Glass
Navigation bars, tab bars, toolbars
Sheets, popovers, action sheets
Buttons, sliders, toggles, and controls
Sidebars, split views, menus
How It Works
Liquid Glass combines optical properties of glass with fluidity
Forms distinct functional layer for controls and navigation
Adapts in response to overlap, focus state, and environment
Helps bring focus to underlying content
Leverage System Frameworks
✅ DO: Use Standard Components
Standard components from SwiftUI, UIKit, and AppKit automatically adopt Liquid Glass with minimal code changes.
// ✅ Standard components get Liquid Glass automaticallyNavigationView{List(items){ item inText(item.name)}.toolbar {ToolbarItem{Button("Add"){}}}}// Recompile with Xcode 26 → Liquid Glass applied
❌ DON'T: Override with Custom Backgrounds
// ❌ Custom backgrounds interfere with Liquid GlassNavigationView{}.background(Color.blue.opacity(0.5))// Breaks Liquid Glass effects.toolbar {ToolbarItem{}.background(LinearGradient(...))// Overlays system effects}
What to Audit
Split views
Tab bars
Toolbars
Navigation bars
Any component with custom background/appearance
Solution Remove custom effects and let the system determine background appearance.
Test with Accessibility Settings
Liquid Glass adapts to: Reduce Transparency (frostier), Increase Contrast (black/white borders), Reduce Motion (no elastic animations). Verify legibility maintained under each setting and that custom elements provide fallback experiences. For detailed accessibility testing workflows, see axiom-liquid-glass discipline skill.
Liquid Glass brings attention to underlying content. Overusing it on multiple custom controls distracts from content. Apply .glassEffect() only to important functional elements (navigation, primary actions) — not content cards, list rows, or decorative elements.
// ✅ Content layer: no glass. Navigation layer: glass on functional buttons only.ZStack{ScrollView{ForEach(articles){ArticleCard($0)}}VStack{Spacer()HStack{Button("Filter"){}.glassEffect()Spacer()Button("Sort"){}.glassEffect()}.padding()}}
App Icons
App icons now take on a design that's dynamic and expressive. Updates to the icon grid result in standardized iconography that's visually consistent across devices. App icons contain layers that dynamically respond to lighting and visual effects.
Design clean, simplified layers with solid fills and semi-transparent overlays. Let the system handle effects (reflection, refraction, shadow, blur, masking). Do NOT bake in pre-applied blur, manual shadows, hardcoded highlights, or fixed masking.
Design Using Layers
Three layers: foreground (primary elements), middle (supporting), background (foundation). Export each layer as PNG or SVG at @1x/@2x/@3x with transparency preserved.
Icon Composer
Included in Xcode 26+ (also standalone from developer.apple.com/design/resources). Drag and drop layers, add optional background, adjust attributes (opacity, position, scale), preview with system effects and all appearance variants, export directly to asset catalog.
Preview Against Updated Grids
Grids: iOS/iPadOS/macOS use rounded rectangle mask; watchOS uses circular mask. Download from developer.apple.com/design/resources. Keep elements centered to avoid clipping, test at all sizes, verify all appearance variants look intentional.
Controls
Controls have refreshed look across platforms and come to life during interaction. Knobs transform into Liquid Glass during interaction, buttons fluidly morph into menus/popovers. Hardware shape informs curvature of controls (rounder forms nestle into corners).
Updated Appearance
Bordered buttons default to capsule shape (mini/small/medium on macOS retain rounded-rectangle). Knobs transform into glass during interaction; buttons morph into menus/popovers. New controlSize(.extraLarge) option; heights slightly taller on macOS. Use controlSize(.small) for backward-compatible high-density layouts. Standard controls adopt automatically — remove hard-coded .frame() dimensions.
Review Updated Controls
Audit sliders, toggles, buttons, steppers, pickers, segmented controls, and progress indicators. Verify appearance matches interface, spacing looks natural, controls aren't cropped, and interaction feedback is responsive.
Color in Controls
Use system colors (.tint(.blue), .accentColor) — they adapt to light/dark contexts automatically. Avoid hard-coded RGB values (Color(red:green:blue:)) which may not adapt. Test in both modes and verify WCAG AA contrast ratios.
Check for Crowding or Overlapping
Liquid Glass elements need breathing room. Use default HStack spacing (not spacing: 4) for glass buttons. Overcrowding or layering glass-on-glass creates visual noise. Use GlassEffectContainer when multiple glass elements must be close together.
Optimize for Legibility with Scroll Edge Effects
Use .scrollEdgeEffectStyle(.hard, for: .top) to obscure content scrolling beneath controls. System bars (toolbars, navigation bars, tab bars) adopt this automatically; custom bars need it explicitly.
Align Control Shapes with Containers
Use containerRelativeShape() to align control curvature with containers — creates concentric visual continuity from controls to sheets to windows to display.
New Button Styles
Use built-in styles instead of custom glass effects: .borderedProminent (primary, with .tint()), .bordered (secondary), .plain + .glassEffect() (tertiary/custom). Each adapts to Liquid Glass automatically.
Navigation
Liquid Glass applies to topmost layer where you define navigation. Key navigation elements like tab bars and sidebars float in this Liquid Glass layer to help people focus on underlying content.
Clear Navigation Hierarchy
Maintain two distinct layers: Navigation (tab bar, sidebar, toolbar — Liquid Glass) floats above Content (articles, photos, data — no glass). Do NOT apply .glassEffect() to content items like list rows — glass on the content layer blurs the boundary and competes with navigation.
Tab Bar Adapting to Sidebar
Use .tabViewStyle(.sidebarAdaptable) (iOS 26) to let the tab bar adapt to sidebar on iPad/macOS while remaining a tab bar on iPhone. Transitions fluidly with adaptive window sizes.
Use NavigationSplitView with sidebar, content, and detail columns. Liquid Glass applies automatically to sidebars and inspectors. iOS adapts column visibility; iPadOS/macOS shows all columns on large screens.
Verify content peeks through appropriately beneath sidebars/inspectors. Use .safeAreaInset(edge:) when content needs to account for sidebar/inspector space.
Padding with Edge-to-Edge Glass
When glass extends edge-to-edge via .ignoresSafeArea(), use .safeAreaPadding() (not .padding()) on the content layer to respect device safe areas (notch, Dynamic Island, home indicator):
// ❌ .padding(.horizontal, 20) — doesn't account for safe areas// ✅ .safeAreaPadding(.horizontal, 20) — 20pt beyond safe areas
Applies to: full-screen sheets with materials, edge-to-edge toolbars, floating panels, custom glass navigation bars. Requires iOS 17+. See axiom-swiftui-layout-ref for full .safeAreaPadding() vs .padding() guidance.
Verify: content visible beneath sidebar/inspector, not cropped, peek-through looks intentional, properly inset from notch/Dynamic Island/home indicator.
Background Extension Effect
Mirrors and blurs content under sidebar/inspector for an immersive edge-to-edge feel, without actually scrolling content there. Best for hero images, photo galleries, and media-rich split views.
Tab bars can recede when scrolling via .tabBarMinimizeBehavior() (iOS 26). Options: .onScrollDown (recommended for reading/media apps), .onScrollUp, .automatic, .never. Tab bar expands when scrolling in opposite direction.
Menus and Toolbars
Menus have refreshed look across platforms. They adopt Liquid Glass, and menu items for common actions use icons to help people quickly scan and identify actions. iPadOS now has menu bar for faster access to common commands.
Cross-Platform Menu Consistency
Menus now have consistent layout across iOS and macOS — icons on leading edge, same API (Label or standard control initializers) produces the same visual result on both platforms.
Menu Icons for Standard Actions
Automatic Icon Adoption
// ✅ Standard selectors get icons automaticallyMenu
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
