eventkitlisted
Install: claude install-skill thienqo/ios-skills
# EventKit
Use EventKit for calendar and reminder authorization, CRUD, recurrence, alarms,
and system editors.
## Contents
- [Workflow](#workflow)
- [Route by Task](#route-by-task)
- [Core Decisions](#core-decisions)
- [Common Mistakes](#common-mistakes)
- [Review Checklist](#review-checklist)
- [References](#references)
## Workflow
1. Determine whether the app needs event write-only access, full event access, or reminder access and declare the matching usage descriptions.
2. Retain one `EKEventStore`, request the narrowest authorization, and branch on current status.
3. Create or fetch objects from that store, choose writable calendars, and make timezone/recurrence semantics explicit.
4. Save or batch changes with the intended commit policy and surface recoverable errors.
5. Observe store changes and verify denied/restricted access, recurrence edits, timezone changes, and external modifications.
## Route by Task
- Read [core implementation details](references/core-implementation.md) for authorization, events, reminders, recurrence, alarms, EventKitUI, and change observation.
- Read [extended EventKit patterns](references/eventkit-patterns.md) for SwiftUI wrappers, predicates, batch operations, and advanced recurrence workflows.
## Core Decisions
- Use current full-access/write-only authorization APIs rather than legacy generic access calls.
- Never mix `EKObject` instances from different event stores.
- Check calendar mutability before save and preserve explicit tim