Menu
Use when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer — capture must be transparent, local-first, and easy to delete.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when shipping a macOS app outside the App Store — Developer ID signing with hardened runtime, notarization with notarytool, stapling, building a clean drag-to-Applications DMG, and verifying the result launches on a stranger's Mac.
Use when reading, writing, or watching the macOS clipboard — NSPasteboard types and multiple representations, the changeCount polling pattern, the transient/concealed pasteboard conventions clipboard tools must respect, and the Sequoia paste-privacy alerts.
Use when adding or reviewing keyboard shortcuts in a macOS app — in-app vs global, RegisterEventHotKey vs the KeyboardShortcuts package vs NSEvent monitors, user-configurable recording, conflict handling, and which defaults won't collide with the system.
Use when adding, reviewing, or debugging Launch at Login in a macOS app — SMAppService registration, the requiresApproval state, a Settings toggle that reflects reality, and migration off deprecated login-item APIs.
Use when adding or reviewing macOS user notifications — UNUserNotificationCenter permission flow, categories and action buttons, click routing through the delegate, foreground presentation, and rules that keep notifications from becoming spam.
Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.
Based on SOC occupation classification
| name | emergency-switch-app |
| description | Use when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer — capture must be transparent, local-first, and easy to delete. |
Design a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer. Capture must be user-initiated, transparent, local-first, and easy to delete — never silent monitoring.
Use this skill when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer.
Emergency capture must be user-initiated, transparent, local-first, and easy to delete.
Menu bar button
Global shortcut chosen by user
Command palette command
Manual quick capture button
Manual note
Timestamp
Selected project
Current task if app knows it
User-selected files if provided
Optional active app/window title only with clear permission
What I was doing
Why I stopped
Next step when I return
Related project/task
[ ] Capture is user-initiated
[ ] User sees what is captured
[ ] Permissions are explained
[ ] Data stays local unless user exports
[ ] Delete/edit exists
Drop this into any coding agent (Claude Code, Codex, Cursor, …) to apply the skill:
Use the emergency-switch-app skill to design a privacy-first emergency context capture flow. It must be user-initiated, transparent, editable, deletable, and local-first. Do not add silent monitoring.