shortcuts-applelisted

# Apple Shortcuts: build, sign, deliver A `.shortcut` file is a **binary plist** holding a list of actions. You can generate one in code and hand it over ready to import. The two things that make this fail are documented nowhere and cost two rounds of trial and error in the field; they are in "Pitfalls" below. Read that before generating anything. ## Tool `scripts/new-shortcut.py` builds the file from a spec and signs it: ```bash python3 scripts/new-shortcut.py spec.json --out ./build ``` ```json { "name": "Living room TV", "prompt": "What should I do?", "items": [ {"title": "Lights on", "url": "https://home/lights/on", "notify": true}, {"title": "Lights off", "url": "https://home/lights/off"} ] } ``` You get `Living room TV signed.shortcut` plus, when any item asks for a notification, `Living room TV plain signed.shortcut` (same thing without the notification action). `"menu": false` with a single item builds a one-tap shortcut with no menu. For actions outside the menu/URL/notification pattern, build the plist by hand following "Anatomy" and reuse the script's `sign()`. ## Pitfalls (the two that break everything) **1. Unsigned files are refused.** iOS says the shortcut "could not be opened because it was not signed". Every file has to go through: ```bash shortcuts sign --mode anyone --input raw.shortcut --output signed.shortcut ``` The `shortcuts` CLI ships with macOS (`/usr/bin/shortcuts`) and signs with the Mac's account. `anyone` lets anybody