Generate macOS/iOS Shortcuts by creating plist files. Use when asked to create shortcuts, automate workflows, build .shortcut files, or generate Shortcuts plists. Covers 1,155 actions (427 WF*Actions + 728 AppIntents), variable references, and control flow.
Use when running AI coding agents in Docker Sandboxes, setting up sbx CLI, managing sandbox network policies, creating templates or kits for custom environments, handling sandbox secrets and credentials, or troubleshooting sandbox issues. Triggers: sbx, docker sandbox, isolated agent, microVM, sandbox network policy, sandbox template, sandbox kit.
Consumes task files from a shared .ai/inbox directory left by a collaborator agent. Reads inbox files, presents choices when multiple exist, and triggers brainstorming for complex tasks. Activate when the user mentions inbox, collaborator, tasks, picking up work, or checking for new tasks. Requires an AGENTS.md with an Agent Collaboration section defining the inbox path and sibling project.
Writes task/instruction files to a shared inbox for a sibling project's agent. Activate when implementing something the sibling project needs to know about, porting patterns, requesting context, or when the user explicitly asks to write instructions for the other project. Requires an AGENTS.md with an Agent Collaboration section defining the inbox path and sibling project.
Consumes task files from the .ai/inbox directory left by a collaborator agent. Reads inbox files, presents choices when multiple exist, and triggers brainstorming for complex tasks. Activate when the user mentions inbox, collaborator, tasks, picking up work, or checking for new tasks. Only applies to yulo projects (yulo and yulo-web).
Writes task/instruction files to the sibling collaborator's inbox. Activate when implementing new endpoints, features, or adjusting API/component contracts that the sibling project needs to know about. Also activate when the user explicitly asks to write instructions for the other project. Only applies to yulo projects (yulo and yulo-web).
Use when encountering PHPStan static analysis errors that need systematic resolution, especially when dealing with multiple errors (>30) or complex type inference issues
Use when the user says 'hotfix' or asks to create a hotfix branch, commit a quick fix, or merge a hotfix. Covers the full hotfix flow: branch, commit, merge back.