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 implementing location services, maps, geofencing, or debugging location/MapKit issues. Covers Core Location, CLMonitor, MapKit, annotations, directions.
$ npx -y skills add charleswiltgen/axiom --skill axiom-location --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/axiom-locationContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when implementing location services, maps, geofencing, or debugging location/MapKit issues. Covers Core Location, CLMonitor, MapKit, annotations, directions.
name: axiom-location description: Use when implementing location services, maps, geofencing, or debugging location/MapKit issues. Covers Core Location, CLMonitor, MapKit, annotations, directions. license: MIT
**You MUST use this skill for ANY location services, mapping, geofencing, or Core Location / MapKit work.**
| Symptom / Task | Reference | |----------------|-----------| | Authorization strategy (When In Use vs Always) | See `skills/core-location.md` | | Monitoring approach (continuous, significant-change, CLMonitor) | See `skills/core-location.md` | | Accuracy selection, background location | See `skills/core-location.md` | | CLLocationUpdate, CLMonitor, CLServiceSession APIs | See `skills/core-location-ref.md` | | Authorization API patterns, geofencing API | See `skills/core-location-ref.md` | | Compass heading, heading reference body (`headingBody`) | See `skills/core-location-ref.md` (Part 12) | | Location updates never arrive | See `skills/core-location-diag.md` | | Background location stops working | See `skills/core-location-diag.md` | | Authorization always denied, geofence failures | See `skills/core-location-diag.md` | | SwiftUI Map, annotations, markers, clustering | See `skills/mapkit.md` | | MKMapView vs SwiftUI Map decision | See `skills/mapkit.md` | | Search, directions, routing | See `skills/mapkit.md` | | MapKit API: Marker, Annotation, MKLocalSearch, MKDirections | See `skills/mapkit-ref.md` | | Look Around, MKMapSnapshotter, MKMapItem | See `skills/mapkit-ref.md` | | Annotations not appearing, region jumping | See `skills/mapkit-diag.md` | | Clustering not working, search failures | See `skills/mapkit-diag.md` | | Overlay rendering, user location not showing | See `skills/mapkit-diag.md` |
digraph location {
start [label="Location / Maps task" shape=ellipse];
domain [label="Core Location or MapKit?" shape=diamond];
cl_type [label="Need what?" shape=diamond];
mk_type [label="Need what?" shape=diamond];
start -> domain;
domain -> cl_type [label="Core Location"];
domain -> mk_type [label="MapKit / Maps"];
cl_type -> "skills/core-location.md" [label="authorization, monitoring\nstrategy, accuracy,\nbackground location"];
cl_type -> "skills/core-location-ref.md" [label="API syntax\n(CLLocationUpdate,\nCLMonitor, CLServiceSession)"];
cl_type -> "skills/core-location-diag.md" [label="something broken\n(no updates, denied,\ngeofence not firing)"];
mk_type -> "skills/mapkit.md" [label="patterns, decisions\n(SwiftUI Map vs MKMapView,\nannotations, search)"];
mk_type -> "skills/mapkit-ref.md" [label="API syntax\n(Marker, Annotation,\nMKLocalSearch, MKDirections)"];
mk_type -> "skills/mapkit-diag.md" [label="something broken\n(annotations missing,\nregion jumping, clustering)"];
}1. Authorization strategy, monitoring approach, accuracy? → `skills/core-location.md` 1a. Need specific API syntax (CLLocationUpdate, CLMonitor, CLServiceSession)? → `skills/core-location-ref.md` 1b. Location not working? → `skills/core-location-diag.md` 2. Adding a map, annotations, search, directions? → `skills/mapkit.md` 2a. Need specific MapKit API syntax (Marker, MKLocalSearch, MKDirections)? → `skills/mapkit-ref.md` 2b. Map display broken? → `skills/mapkit-diag.md` 3. Location draining battery? → See axiom-performance (skills/energy.md) 4. Background task scheduling for location? → See axiom-integration 5. Privacy manifest for location? → See axiom-integration
**location vs axiom-performance**: When location is draining battery: 1. **Try location FIRST** — Excessive accuracy or continuous updates are the #1 cause. `skills/core-location.md` covers accuracy selection and monitoring strategy. 2. **Only use axiom-performance** if location settings are already correct — Profile after ruling out obvious over-tracking.
**location vs axiom-integration**: When implementing background location:
**location vs axiom-data**: When storing or syncing location data:
**location vs axiom-build**: When location permissions fail in simulator:
**Core Location** (`skills/core-location.md`):
**Core Location API** (`skills/core-location-ref.md`):
**Core Location Diagnostics** (`skills/core-location-diag.md`):
**MapKit** (`skills/mapkit.md`):
**MapKit API** (`skills/mapkit-ref.md`):
**Ma
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.