Use when the cardputer MCP tools (notify, ask, confirm, show, progress) are available in the session, or the user mentions their Cardputer / handheld / "buzz me" / "page me". Governs runtime etiquette for the pocket device — mandates a physical confirm gesture before irreversible operations (passing the real action diff as details), buzzes the device on completion of long tasks, asks quick questions when blocked and the user is away from the keyboard, shows ambient status for long work, and formats all device output for the 240×135 LCD. This is the behavioral counterpart to the cardputer MCP server: the server is the hands, this skill is the manners. Trigger even when the user doesn't name the skill — if the `cardputer` MCP tools are registered, these rules are in force.
End-to-end onboarding for a freshly-plugged-in M5Stack ESP32 device — detect it on USB, identify the exact model, flash UIFlow 2.0 firmware, and install a MicroPython app bundle (e.g. the Claude Buddy + Hello + Snake payload) so the device boots into user software instead of UIFlow's pairing screen. Works on macOS, Linux, and Windows; Python, esptool, and pyserial are auto-installed by the skill if missing. The apps we ship run over BLE / USB. Use this skill whenever the user mentions an M5Stack, M5Core, M5Stick, Cardputer, Cardputer-Adv, CoreS3, Core2, UIFlow, "flashing" or "provisioning" an ESP32 dev board, or plugs in "a new device" after previously working with M5Stack hardware. Also use it if the user asks to push app .py files onto an already-flashed device, install "the games" or "buddy" onto a board, or reset one to factory UIFlow. Trigger even when the user doesn't explicitly name the skill — "I have another one of these", "same thing for this device", "put the game on this one too", "m5-onboard", or