cyberboard-cli

Interactively author a Custom LED *display* animation for the AngryMiao CyberBoard R4 and write it to the board. Choose an effect, tune it through a Japanese AskUserQuestion dialogue, preview the result as a GIF, iterate, then pick a slot and write it on explicit confirmation. Use whenever the user wants to "make / change the LED animation", "set the keyboard's screen", "put text / a pattern / a GIF on the CyberBoard display", or similar. Orchestrates the `cyberboard` CLI (`anim` / `led` / `write`). Converses in Japanese; every write is confirmed first because it overwrites the whole config.

Detect and inspect a physically-connected AngryMiao CyberBoard over USB CDC serial — list devices and read their identity/status (product_id, firmware version, page count) without modifying any keyboard config. Use whenever you need to answer "is the board connected", "which serial port is it on", "what firmware is on the R4", "show device info", or before any write so you've confirmed the right device. READ-ONLY and safe to run anytime the hardware is plugged in. Backed by tools/cb_device.py, the reusable foundation the CLI's `devices` / `device info` commands are built on.

Reverse-engineer a PyInstaller-packaged Python application (a Mach-O / ELF / PE "onefile" or "onedir" bootloader) back to readable Python source. Use this whenever you need to understand, audit, or interoperate with a closed-source app that turns out to be PyInstaller-frozen Python — e.g. "decompile this .app / .exe", "how does this packaged Python tool work", "recover the source from this binary", "extract the .pyc and decompile it", or when you spot PyInstaller/pyinstxtractor/pycdc/.pyc/CArchive/PYZ in the task. Trigger even if the user doesn't name PyInstaller but describes a Python GUI/CLI app shipped as a single binary they want to read the logic of. Captures the two-decompiler fallback (pycdc → decompyle3) and the non-obvious gotchas that otherwise cost hours.