Yuuzu-IDE

Prepare, validate, tag, inspect, publish, or troubleshoot Yuuzu-IDE releases. Use this whenever the user mentions Yuuzu-IDE release work, version tags such as v0.1.0, changelog dates, release gates, GitHub draft releases, latest.json, updater artifacts, macOS Apple Silicon, Windows x64, portable zip assets, or asks whether it is safe to publish.

Run Yuuzu-IDE packaged debug app smoke verification with Tauri build, Computer Use, temporary workspaces, Git Graph stability probes, browser screenshot permission checks, clipboard checks, and process cleanup. Use this whenever the user says tauri-debug-build, asks to reverify a smoke-report finding in the real app, or reports visual/runtime behavior that unit tests cannot prove.

Add or update focused Yuuzu-IDE regression tests for v2 React, store/controller/bridge logic, CodeMirror editor behavior, and Rust IPC. Use this whenever a Yuuzu-IDE bugfix or feature needs TDD, a failing test before implementation, adjacent Bun/Cargo coverage, or faster test authoring.

Evaluate and improve repo-local Yuuzu-IDE testing skills. Use this when creating or updating skills under .codex/skills/, adding evals/evals.json, comparing with-skill and baseline outputs, or collecting feedback on which Yuuzu-IDE test methods are slow, flaky, redundant, unsafe, or missing runtime coverage.

Plan and select Yuuzu-IDE verification commands for bugfix, ui-runtime, release, docs-status, smoke-report, and review tasks. Use this whenever a Yuuzu-IDE task mentions verification, testing, tauri-debug-build, smoke reports, Git Graph revalidation, focused or broad gates, or when code changes need an evidence-backed closeout.