Workflow
-
Parameter parsing 1.1 Reminder title and content 1.2 Time (e.g. "in 5 minutes", "tomorrow at 3 PM", "in 3 months") 1.3 Reminder method (explicit
--typeor inferred from semantics) -
Route by type, read the corresponding reference and execute:
| --type | App / Mechanism | Use case | reference |
|---|---|---|---|
reminder(default) |
Reminders.app | Task-oriented, requires checking off as complete, stays in a list | reminder-help.md |
calendar |
Calendar.app | One-time, passes once the time arrives, some future day | calendar-help.md |
stickies |
Stickies.app | Desktop always-on sticky note (rich text + images) | stickies-help.md |
break |
Background timed popup (cross-platform) | Forced interruption, catch-up reminder after sleep wake | break-help.md |
type decision guide
- One-time, some future day, only needs to be known when the time arrives("review in 3 months") →
calendar(automatically archived once the event passes, does not linger in a list) - Task-oriented, requires checking off as complete(to-do list) →
reminder - Desktop always-on display(sticky note on desktop) →
stickies - Must force interruption / catch-up reminder after lock screen or sleep / non-macOS platform→
break
No explicit --type , infer from semantics; default reminder. Usage tips, flaws, and pitfalls of each appare all in the corresponding reference, not expanded in this file.
Extending with a new type
In references/ , add <type>-help.md, and add one row to the table above. SKILL.md stays lean as routing.