axiom-ios-ui

Original：🇺🇸 English
Translated

Use when building, fixing, or improving ANY iOS UI including SwiftUI, UIKit, layout, navigation, animations, design guidelines. Covers view updates, layout bugs, navigation issues, performance, architecture, Apple design compliance.

3installs
Sourcecharleswiltgen/axiom
Added on

NPX Install

npx skill4agent add charleswiltgen/axiom axiom-ios-ui

Tags

Translated version includes tags in frontmatter
ios-ui-developmentswiftuiuikitios-layoutios-navigation

SKILL.md Content

View Translation Comparison →

iOS UI Router

You MUST use this skill for ANY iOS UI work including SwiftUI, UIKit, layout, navigation, animations, and design.

When to Use

Use this router when working with:
  • SwiftUI views, state, bindings
  • UIKit views and constraints
  • Layout issues (Auto Layout, SwiftUI layout)
  • Navigation (NavigationStack, deep linking)
  • Animations and transitions
  • Liquid Glass design (iOS 26+)
  • Apple Human Interface Guidelines
  • UI architecture and patterns
  • Accessibility UI issues

Conflict Resolution

ios-ui vs ios-performance: When UI is slow (e.g., "SwiftUI List slow"):
  1. Try ios-ui FIRST — Domain-specific fixes (LazyVStack, view identity, @State optimization) often solve UI performance in 5 minutes
  2. Only use ios-performance if domain fixes don't help — Profiling takes longer and may confirm what domain knowledge already knows
Rationale: Jumping to Instruments wastes time when the fix is a known SwiftUI pattern. Profile AFTER trying domain fixes, not before.

Routing Logic

SwiftUI Issues

View not updating → 
/skill axiom-swiftui-debugging
Navigation issues → 
/skill axiom-swiftui-nav
Performance/lag → 
/skill axiom-swiftui-performance
Layout problems → 
/skill axiom-swiftui-layout
Stacks/grids/outlines → 
/skill axiom-swiftui-containers-ref
Animation issues → 
/skill axiom-swiftui-animation-ref
Gesture conflicts → 
/skill axiom-swiftui-gestures
Architecture/testability → 
/skill axiom-swiftui-architecture
App-level composition → 
/skill axiom-app-composition
Search implementation → 
/skill axiom-swiftui-search-ref
iOS 26 features → 
/skill axiom-swiftui-26-ref

UIKit Issues

Auto Layout conflicts → 
/skill axiom-auto-layout-debugging
Animation timing issues → 
/skill axiom-uikit-animation-debugging

Design & Guidelines

Liquid Glass adoption → 
/skill axiom-liquid-glass
Design decisions → 
/skill axiom-hig
Typography → 
/skill axiom-typography-ref
TextKit/rich text → 
/skill axiom-textkit-ref

Accessibility

VoiceOver, Dynamic Type → 
/skill axiom-accessibility-diag

Testing

UI test flakiness → 
/skill axiom-ui-testing

Decision Tree

  1. SwiftUI view not updating? → swiftui-debugging
  2. SwiftUI navigation? → swiftui-nav
  3. SwiftUI performance/lag? → swiftui-performance
  4. SwiftUI adaptive layout? → swiftui-layout
  5. Stacks/grids/outlines (VStack, LazyVGrid, OutlineGroup)? → swiftui-containers-ref
  6. Feature-level architecture? → swiftui-architecture
  7. App-level composition (root view, auth flows, scenes)? → app-composition
  8. Animations/gestures? → swiftui-animation-ref or swiftui-gestures
  9. SwiftUI search? → swiftui-search-ref
  10. iOS 26 features? → swiftui-26-ref
  11. Auto Layout? → auto-layout-debugging
  12. UIKit animations? → uikit-animation-debugging
  13. Liquid Glass? → liquid-glass
  14. HIG compliance? → hig
  15. Typography? → typography-ref
  16. TextKit/rich text? → textkit-ref
  17. Accessibility? → accessibility-diag

Anti-Rationalization

ThoughtReality
"Simple SwiftUI layout, no need for the layout skill"SwiftUI layout has 12 gotchas. swiftui-layout covers all of them.
"I know how NavigationStack works"Navigation has state restoration, deep linking, and identity traps. swiftui-nav prevents 2-hour debugging.
"It's just a view not updating, I'll debug it"View update failures have 4 root causes. swiftui-debugging diagnoses in 5 min.
"I'll just add .animation() and fix later"Animation issues compound. swiftui-animation-ref has the correct patterns.
"This UI is simple, no architecture needed"Even small features benefit from separation. swiftui-architecture prevents refactoring debt.
"I know how .searchable works"Search has 6 gotchas (navigation container, isSearching level, suggestion completion). swiftui-search-ref covers all of them.

Example Invocations

User: "My SwiftUI view isn't updating when I change the model" → Invoke: 
/skill axiom-swiftui-debugging
User: "How do I implement Liquid Glass in my toolbar?" → Invoke: 
/skill axiom-liquid-glass
User: "NavigationStack is popping unexpectedly" → Invoke: 
/skill axiom-swiftui-nav
User: "Should I use MVVM for this SwiftUI app?" → Invoke: 
/skill axiom-swiftui-architecture
User: "How do I switch between login and main screens?" → Invoke: 
/skill axiom-app-composition
User: "Where should auth state live in my app?" → Invoke: 
/skill axiom-app-composition
User: "How do I create a grid layout with LazyVGrid?" → Invoke: 
/skill axiom-swiftui-containers-ref
User: "What's the difference between VStack and LazyVStack?" → Invoke: 
/skill axiom-swiftui-containers-ref
User: "How do I display hierarchical data with OutlineGroup?" → Invoke: 
/skill axiom-swiftui-containers-ref
User: "How do I add search to my SwiftUI list?" → Invoke: 
/skill axiom-swiftui-search-ref
User: "My search suggestions aren't working" → Invoke: 
/skill axiom-swiftui-search-ref