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 app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization.
$ npx -y skills add charleswiltgen/axiom --skill axiom-performance --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/axiom-performanceContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization.
name: axiom-performance description: Use when app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization. license: MIT
**You MUST use this skill for ANY performance issue including memory leaks, slow execution, battery drain, or profiling.**
<!-- 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-analyze-swift-performance`, `axiom-audit-energy`, `axiom-audit-memory`. > > The ones that shell out — builds, tests, simulators, crash symbolication — need shell access to run. <!-- AXIOM_AUDITOR_INLINE_END -->
Use this router when:
**Memory leaks (Swift)** → See skills/memory-debugging.md
**Memory leak scan** → `axiom-audit-memory` (5-phase semantic audit: maps resource ownership, detects 6 leak patterns, reasons about missing cleanup, correlates compound risks, scores lifecycle health)
**Memory leaks (Objective-C blocks)** → See skills/objc-block-retain-cycles.md
**Performance profiling (GUI)** → See skills/performance-profiling.md
**Automated profiling (CLI)** → See skills/xctrace-ref.md
**Run automated profile** → Use `performance-profiler` agent or `axiom-profile-performance`
**Compare two traces / detect regressions** → See skills/trace-comparison.md or `/axiom:compare-traces` (Claude Code only)
**App hangs or freezes** → See skills/hang-diagnostics.md
**Corpus/aggregate hang triage (Sentry, ASC)** → `axiom-shipping (skills/production-triage.md)` + `triage-analyzer` agent
**Slow app launch** → See skills/app-launch.md
**Battery drain, high energy** → See skills/energy.md
**Symptom-based diagnosis** → See skills/energy-diag.md
**API reference with code** → See skills/energy-ref.md
**Energy scan** → `axiom-audit-energy` (8 anti-patterns: timer abuse, polling, continuous location, animation leaks, background mode misuse, network inefficiency, GPU waste, disk I/O)
**Timer crash patterns (DispatchSourceTimer)** → See `axiom-integration` (skills/timer-patterns.md)
**Timer API reference** → See `axiom-integration` (skills/timer-patterns-ref.md)
**Swift performance optimization** → See skills/swift-performance.md
**Swift performance scan** → `axiom-analyze-swift-performance` (unnecessary copies, ARC overhead, unspecialized generics, collection inefficiencies, actor isolation costs, memory layout)
**Modern Swift idioms** → See axiom-swift (skills/swift-mod
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.