GeneralD

Build the zellij-tabmap bar plugin from a branch (or the current worktree) and launch a throwaway nested zellij session that loads it via file:, without touching the real config.kdl / default.kdl or the release install. Use to try a dev build of the bar before releasing it — triggers: "try the dev build", "preview this branch's bar", "devビルドを試したい", "floatingを体験したい", "このブランチのバーを見たい".

Get visual color-design feedback on the minimap palette from Gemini. Builds the render_active_cue example, takes a screenshot, reads the current blend constants, then delegates to Gemini's tabmap-color-advisor skill for analysis and suggestions. Use when tweaking ACTIVE_UNFOCUSED_BLEND or INACTIVE_LABEL_BLEND and wanting an outside visual opinion.

Visual color-design advisor for the zellij-tabmap minimap palette. Activate with the trigger word "tabmap-color-check" followed by an image path and the current constant values. Analyzes the rendered minimap screenshot and suggests specific numeric adjustments to the blend constants.

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.

Bump lyra's version in Sources/VersionHandler/Resources/version.txt following semver, commit, and optionally push. Use this skill when working in the lyra repo and the user says "bump version", "version上げて", "リリース準備", "patch bump", "minor bump", or "major bump". Also trigger before or after creating a PR that includes meaningful changes.

Bump the project version in version.txt following semver, commit, and optionally push. Use this skill when the user says "bump version", "version上げて", "リリース準備", "patch bump", "minor bump", "major bump", or before/after creating a PR that includes meaningful changes. Also trigger when the user says "バージョン" in a development context.

Generate VSCode color themes, package them as .vsix files, and install to VSCode. Use when creating custom VSCode themes, designing color schemes, or when the user mentions VSCode theme, color theme, dark theme, or light theme.