axiom audit liquid glass

Engineering Community

Skill notes

Note on Audit Framing

Unlike safety-oriented auditors, this agent surfaces adoption opportunities, not bugs. A codebase with no Liquid Glass adoption is not broken — it's pre-adoption. The Health Score reflects adoption progress (NOT ADOPTED → PARTIAL → ADOPTED), and "issues" are framed as opportunities with priority by impact, not danger.

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Step 6: Read Key Files

Read 1-2 representative view files (root container / navigation / a primary screen) to understand: Whether the app's chrome (toolbars, tab bars, sidebars) has any glass treatment Whether existing blurs/materials are gated behind if #available(iOS 26, *) Whether glass adoption follows Regular vs Clear variant guidance Whether nested view hierarchies stack multiple glass effects

Output

Write a brief Visual Treatment Map (5-10 lines) summarizing: Deployment target (and whether iOS 26+ glass APIs are reachable without availability checks) Existing legacy effect surface (UIBlurEffect / NSVisualEffectView / .material count) Existing glass adoption count (.glassEffect, .glassBackgroundEffect) Toolbar surface (number of toolbar definitions, primary-action discipline)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map Visual Treatment Architecture

Phase 1: Map Visual Treatment Architecture

02
Step 1: Identify Deployment Target and Availability Discipline

Step 1: Identify Deployment Target and Availability Discipline

03
Step 2: Identify Existing Visual Effects (Migration Surface)

Step 2: Identify Existing Visual Effects (Migration Surface)

04
Step 3: Identify Existing Glass Adoption

Step 3: Identify Existing Glass Adoption

05
Step 4: Identify Toolbar, Tab, and Search Surface

Step 4: Identify Toolbar, Tab, and Search Surface

06
Step 5: Identify Custom Container Surfaces

Step 5: Identify Custom Container Surfaces

07
Step 6: Read Key Files

Read 1-2 representative view files (root container / navigation / a primary screen) to understand: Whether the app's chrome (toolbars, tab bars, sidebars) has any glass treatment Whether existing blurs/materials are gated behind `if #available(iOS 26, *)` Whether glass adoption follows Regular vs Clear variant guidance Whether nested view hierarchies stack multiple glass effects

08
Phase 2: Detect Known Adoption Opportunities

Run all 7 detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

09
Phase 3: Reason About Adoption Completeness

Using the Visual Treatment Map from Phase 1 and your domain knowledge, check for what's *missing or incomplete* — not just what's wrong. Question · What it detects · Why it matters If deployment target is below iOS 26, is every `.glassEffect()` / `.glassBackgroundEffect()` call gated behind `if #available(iOS 26, *)`? · Build/runtime mismatch · Calling iOS 26-only API on iOS 25 crashes at runtime; without `#available` the Xcode warning is the only signal

10
Phase 4: Cross-Reference Adoption Compounds

Bump priority for these combinations: Finding A · + Finding B · = Compound · Priority Old `.material` background (Pattern 1) · iOS 26+ deployment target with no `if #available` gate · Direct replacement, ship-ready · HIGH Glass over media (Phase 3) · Regular variant chosen · Color distortion over photos/videos; switch to Clear immediately · HIGH Glass adoption (Pattern 1/3) · No accessibility re-check · Contrast may drop below WCAG 4.5:1; flag for accessibility-auditor follow-up · HIGH

11
Phase 5: Liquid Glass Adoption Health Score

Metric · Value Deployment target · iOS X.Y Legacy effect sites · M UIBlurEffect/NSVisualEffectView/`.material` references Glass adoption sites · N `.glassEffect`/`.glassBackgroundEffect` calls Toolbar modernization · M of N toolbars use `.borderedProminent` + tint on primary action (Z%)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.