axiom-accessibility
Use when fixing or auditing ANY accessibility issue — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review.
Use when making design decisions, implementing HIG patterns, Liquid Glass, SF Symbols, typography, or structuring app entry points and authentication flows.
$ npx -y skills add charleswiltgen/axiom --skill axiom-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/axiom-designContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when making design decisions, implementing HIG patterns, Liquid Glass, SF Symbols, typography, or structuring app entry points and authentication flows.
name: axiom-design description: Use when making design decisions, implementing HIG patterns, Liquid Glass, SF Symbols, typography, or structuring app entry points and authentication flows. license: MIT
**You MUST use this skill for ANY visual design, HIG compliance, Liquid Glass, SF Symbols, typography, or app composition work.**
<!-- AXIOM_AUDITOR_INLINE_BEGIN — rewritten for Codex by scripts/build-codex.ts; do not hand-edit --> > **Auditors are skills here.** Where this router says "Launch `some-auditor` agent", invoke the > matching Codex skill instead — same procedure, no Claude Code agent required. > > Available: `axiom-audit-liquid-glass`. > > The ones that shell out — builds, tests, simulators, crash symbolication — need shell access to run. <!-- AXIOM_AUDITOR_INLINE_END -->
| Symptom / Task | Reference | |----------------|-----------| | Design decisions, HIG compliance, colors, backgrounds | See `skills/hig.md` | | Spacing, padding, margins, insets — what value to use | See `skills/hig.md` | | Section index / A–Z index strip / alphabet scrubber — should this list have one | See `skills/hig.md` | | Semantic colors, custom color patterns, material styles | See `skills/hig-ref.md` | | Liquid Glass effects, adoption, migration from blur effects | See `skills/liquid-glass.md` | | App-wide Liquid Glass adoption, backward compatibility | See `skills/liquid-glass-ref.md` | | SF Symbols rendering modes, effects, animations | See `skills/sf-symbols.md` | | SF Symbols API signatures, UIKit equivalents, availability | See `skills/sf-symbols-ref.md` | | Verify a symbol name exists / check one symbol's availability or supported modes (`sfsymbols` CLI) | See `skills/sf-symbols-ref.md` (Part 11) | | San Francisco fonts, text styles, Dynamic Type, tracking | See `skills/typography-ref.md` | | App entry points, auth flows, root view switching, scene lifecycle, document-based apps | See `skills/app-composition.md` | | Apple Pay button / Wallet pass design / Tap to Pay button | See `axiom-payments` suite, plus `skills/hig.md` for cross-cutting HIG context |
digraph design {
start [label="Design task" shape=ellipse];
what [label="What do you need?" shape=diamond];
start -> what;
what -> "skills/hig.md" [label="design decision,\nHIG compliance,\ncolor/background choice"];
what -> "skills/hig.md" [label="spacing/padding/margin value"];
what -> "skills/hig-ref.md" [label="semantic color API,\ncustom color code,\nmaterial style details"];
what -> "skills/liquid-glass.md" [label="Liquid Glass effects,\nmigrate from blur,\nRegular vs Clear"];
what -> "skills/liquid-glass-ref.md" [label="app-wide Liquid Glass plan,\nplatform differences,\nbackward compat"];
what -> "skills/sf-symbols.md" [label="rendering mode choice,\nsymbol effects/animations,\ncustom symbols"];
what -> "skills/sf-symbols-ref.md" [label="SF Symbols API syntax,\nUIKit equivalents,\navailability matrix"];
what -> "skills/typography-ref.md" [label="font selection,\nDynamic Type,\ntext styles, tracking"];
what -> "skills/app-composition.md" [label="@main entry point,\nauth flow, root view,\nscene lifecycle"];
}1. Design decision / HIG compliance / choosing colors or backgrounds? → `skills/hig.md` 1a. Need semantic color API, custom color code, or material style details? → `skills/hig-ref.md` 2. Liquid Glass effects / migrating from blur / Regular vs Clear variant? → `skills/liquid-glass.md` 2a. Planning app-wide Liquid Glass adoption / platform differences / backward compatibility? → `skills/liquid-glass-ref.md` 3. SF Symbols rendering mode / symbol effects / custom symbols? → `skills/sf-symbols.md` 3a. Need SF Symbols API syntax / UIKit equivalents / availability check? → `skills/sf-symbols-ref.md` 4. Font selection / Dynamic Type / text styles / tracking / leading? → `skills/typography-ref.md` 5. App entry point / auth flow / root view switching / scene lifecycle? → `skills/app-composition.md` 6. SwiftUI view implementation? → `/skill axiom-swiftui` 7. TextKit / rich text editing / Writing Tools? → `/skill axiom-uikit` 8. Accessibility compliance (VoiceOver, contrast, touch targets)? → `/skill axiom-accessibility` 9. Audit UI for Liquid Glass adoption? → liquid-glass-auditor (Agent — surfaces migration opportunities AND adoption-completeness gaps: variant discipline, nesting hygiene, availability gating, primary-action tinting, accessibility re-check; scores ADOPTED / PARTIAL / NOT ADOPTED) 10. CarPlay app design, categories, driver-distraction rules? → `/skill axiom-media` (carplay-hig.md)
**design vs swiftui**: When building UI: 1. **Use design FIRST** — Decide what to build (colors, materials, typography, layout intent) before how to build it. 2. **Then use swiftui** — Implement the design decision in SwiftUI code.
**design vs accessibility**: When choosing colors or typography:
**design (liquid-glass) vs swiftui**: When implementing Liquid Glass:
**design (app-composition) vs swiftui**: When structuring app architecture:
**design vs media (CarPlay)**: When designing for CarPlay:
Battle-tested skills, agents, and tools for modern Apple OS development — Swift 6, SwiftUI, Liquid Glass, Apple Intelligence, and more. Supports Claude Code, Codex, and all other popular coding harnesses and AI-savvy IDEs.
Repo: charleswiltgen/axiom
Use when fixing or auditing ANY accessibility issue — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review.
Use when implementing, testing, or evaluating ANY Apple Intelligence, on-device AI, or speech-to-text feature. Covers Foundation Models, @Generable,…
Use when the user has a crash log (.ips, MetricKit JSON, legacy .crash text, .xccrashpoint bundle, or pasted text) that needs analysis.
Use when the user mentions Swift performance audit, code optimization, or performance review.
Use when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues.
Use when the user mentions flaky tests, tests that pass locally but fail in CI, race conditions in tests, or needs to diagnose WHY a specific test fails.