AI Agent Workflow Collection

Turn a project into one or more real macOS Dock-launchable .app bundles. Use when the user asks to make something clickable from the Dock, package it as an app, give it an icon, or put it in MyApps. Chooses sensible packaging defaults, creates repeatable scripts, installs to ~/Applications/App It/, and verifies click-to-open behavior, port handling, warm reattach, window-close vs Cmd+Q behavior, and cleanup. Generated apps ship with a full standard macOS menu bar (Cmd+Q quit, Cmd+W close window, Cmd+M minimize, Cmd+H hide, Cmd+- / Cmd+= / Cmd+0 page zoom, Cmd+R reload, Cmd+Ctrl+F toggle full screen, plus standard Edit-menu shortcuts) — these are wired into wrapper.swift's menu bar, not relied on as AppKit defaults (the defaults only cover Cmd+Q). Generated apps also ship a desktop:doctor command that self-diagnoses one launcher (config, install, signature, ports, stale PID, server ownership, template drift) read-only, with a narrow --fix-safe that only cleans up app-it's own generated state.

Turn a finished or buildable web app into a macOS Dock-launchable .app that serves the built output — with no dev server. Use when the user asks to make a built site, a finished app, or a dist//build//out/ bundle clickable from the Dock, or wants a lighter launcher for an app that no longer needs live editing. Detects the build command and output directory, builds once, then serves the result from a tiny static server (~15 MB) or directly via file:// (~0 MB) — instead of the 300-700 MB a dev server holds. Reuses app-it's native Swift WebKit window, icon pipeline, and one-folder Dock install. The served output is a snapshot — desktop:rebuild refreshes it. macOS only. For apps that still need a live dev server (half-built, reading local files, no build step), use the app-it skill instead.

Turn a project into one or more real Windows desktop launchers — a self-contained .exe with its own Taskbar identity and a Start Menu shortcut. Windows beta · maintainer wanted · scaffolded but not battle-tested on real hardware. Use when the user asks to make a local web project clickable on Windows, give it an icon, package it as a Windows app, or put a launcher in the Start Menu. Mirrors the macOS app-it contract (native shell that owns its icon, warm dev-server reuse, soft-close vs quit, multi-resolution icon, one-folder install) using Windows primitives: a C WPF + WebView2 host, PowerShell lifecycle scripts, a multi-resolution .ico, and a Start Menu .lnk. Because the author runs only macOS, every decision that needs real Windows hardware to confirm fails loudly with a pointer to docs/WINDOWS.md instead of guessing. Do not present this skill as a finished feature.