← ClaudeAtlas

core-motionlisted

Builds sensor workflows with Core Motion for accelerometer, gyroscope, device motion, pedometer, activity recognition, altitude, headphone motion, workout motion, and submersion/depth data. Use for motion interaction, steps, activity classification, AirPods tracking, or watchOS depth features.
thienqo/ios-skills · ★ 11 · AI & Automation · score 69
Install: claude install-skill thienqo/ios-skills
# CoreMotion Access accelerometer, gyroscope, attitude/device motion, pedometer, altitude, and specialized sensors using Core Motion. Targets Swift 6.4 / iOS 26+. ## Contents - [Setup & Authorization](#setup--authorization) - [Motion Manager & Raw Sensors](#motion-manager--raw-sensors) - [Device Motion (Attitude & Gravity)](#device-motion-attitude--gravity) - [Pedometer & Activity Recognition](#pedometer--activity-recognition) - [Altimeter & Specialized Sensors](#altimeter--specialized-sensors) - [Battery & Lifecycle](#battery--lifecycle) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## Setup & Authorization Add `NSMotionUsageDescription` to Info.plist explaining why the app accesses motion sensors. Check authorization status for managers exposing privacy controls (`CMPedometer`, `CMMotionActivityManager`, `CMAltimeter`): ```swift import CoreMotion guard CMMotionActivityManager.authorizationStatus() != .denied else { // Prompt user to enable motion permissions in Settings return } ``` Raw accelerometer/gyro streams under `CMMotionManager` do not prompt for permission directly but require the usage description and throw errors on unauthorized access. ## Motion Manager & Raw Sensors Maintain exactly **one** shared `CMMotionManager` instance per application to avoid sensor contention: ```swift final class MotionProvider { static let shared = MotionProvider() let manager = CMMotionManager()