Fetches alarmkit from dpearson2699/swift-ios-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/alarmkit
Restart Cursor to activate alarmkit. Access via /alarmkit in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Schedule prominent alarms and countdown timers that surface on the Lock Screen,
Dynamic Island, and Apple Watch. AlarmKit requires iOS 26+ / iPadOS 26+. Alarms override
Focus and Silent mode automatically.
AlarmKit builds on Live Activities -- every alarm creates a system-managed Live
Activity with templated UI. You configure the presentation via AlarmAttributes
and AlarmPresentation rather than building custom widget views.
See references/alarmkit-patterns.md for complete code patterns including
authorization, scheduling, countdown timers, snooze handling, and widget setup.
Create AlarmAttributes with the presentation, optional metadata, and tint color.
Build an AlarmManager.AlarmConfiguration (.alarm or .timer).
Schedule with AlarmManager.shared.schedule(id:configuration:).
Observe state changes via alarmManager.alarmUpdates.
If using countdown, add a widget extension target for non-alerting Live Activity UI.
2. Review existing alarm code
Run through the Review Checklist at the end of this document.
Authorization
AlarmKit requires explicit user authorization. Without it, alarms silently
fail to schedule. Request early (e.g., at onboarding) or let AlarmKit prompt
automatically on first schedule.
let manager =AlarmManager.shared
// Request authorization explicitlylet state =tryawait manager.requestAuthorization()guard state ==.authorized else{return}// Check current state synchronouslylet current = manager.authorizationState // .authorized, .denied, .notDetermined// Observe authorization changesforawait state in manager.authorizationUpdates {switch state {case.authorized:print("Alarms enabled")case.denied:print("Alarms disabled")case.notDetermined:break@unknowndefault:break}}
Alarm vs Timer Decision
Feature
Alarm (.alarm)
Timer (.timer)
Fires at
Specific time (schedule)
After duration elapses
Countdown UI
Optional
Always shown
Recurring
Yes (weekly days)
No
Use case
Wake-up, scheduled reminders
Cooking, workout intervals
Use .alarm(schedule:...) when firing at a clock time. Use .timer(duration:...)
when firing after a duration from now.
Scheduling Alarms
Alarm.Schedule
Alarms use Alarm.Schedule to define when they fire.
// Fixed: fire at an exact Date (one-time only)let fixed:Alarm.Schedule=.fixed(myDate)// Relative one-time: fire at 7:30 AM in device time zone, no repeatlet oneTime:Alarm.Schedule=.relative(.init( time:.init(hour:7, minute:30), repeats:.never
))// Recurring: fire at 6:00 AM on weekdayslet weekday:Alarm.Schedule=.relative(.init( time:.init(hour:6, minute:0), repeats:.weekly([.monday,.tuesday,.wednesday,.thursday,.friday])))
Alarm.CountdownDuration controls the visible countdown phases:
preAlert -- seconds to count down before the alarm fires (the main countdown)
postAlert -- seconds for a repeat/snooze countdown after the alarm fires
let countdown =Alarm.CountdownDuration( preAlert:600,// 10-minute countdown before alert postAlert:300// 5-minute snooze countdown if user taps Repeat)let config =AlarmManager.AlarmConfiguration( countdownDuration: countdown, schedule:.relative(.init( time:.init(hour:8, minute:0), repeats:.never
)), attributes: attributes, stopIntent: stopIntent, secondaryIntent: snoozeIntent, sound:.default)
Alarm States
Each Alarm has a state property reflecting its current lifecycle position.
State
Meaning
.scheduled
Waiting to fire (alarm mode) or waiting to start countdown
.countdown
Actively counting down (timer or pre-alert phase)
.paused
Countdown paused by user or app
.alerting
Alarm is firing -- sound playing, UI prominent
Observing State Changes
let manager =AlarmManager.shared
// Get all current alarmslet alarms = manager.alarms
// Observe changes as an async sequenceforawait updatedAlarms in manager.alarmUpdates {
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
