Decky debugger for Steam UI and plugin runtime issues. Use when D-pad/controller focus is wrong, modals behave oddly, layout clips/drifts, durable styles regress, or logs must prove root cause before fixes. Enforces focus-graph-first triage, evidence-backed geometry fixes, and a self-contained log-capture runbook so…
Design-time focus-graph architect for Decky/Steam UI. Use when planning modals, tab restore, nested Focusable trees, or D-pad routing before implementation — not for runtime debugging (use decky-debugger).
Pre-ship focus gate for Deck-facing UI edits. Run before marking done on component, focus-graph, or control changes — enforces D-pad checklist, section-parent wiring, and on-Deck verification. Triage-only; escalate runtime bugs to decky-debugger.
End-to-end maintainer loop for any Decky plugin on Steam Deck: build/deploy via MCP, watch-deploy, BPM vs Gaming Mode testing, screenshots, optional log tunnel, and when to use decky-screenshot-ingest. Use when changing src/, main.py, plugin.json, or closing Deck-facing UI/RPC work.
Static and preview focus audit for Decky plugins: Focusable callbacks vs DOM keydown, modal cancel/OK, preview.runSequence evidence. Escalate on-device issues to decky-debugger. Use before merging navigation-heavy UI or when reviewing D-pad routing.
First-hour Decky plugin setup with Decky Plugin Studio: Init Pack, deck.configure, preview smoke, first build/deploy, deck.openPlugin checklist, and first screenshot. Use when onboarding a new plugin repo or helping a new contributor get unblocked.
Drive the Decky Plugin Studio in-IDE preview for fast iteration. Use when developing UI/focus behavior, testing hardware simulator scenarios, or verifying state preservation across HMR. Covers preview.start/stop/status, preview.injectFocusEvent, preview.setHardware, preview.runSequence, preview.callRpc, and…
Release checklist for Decky plugins: version bump, plugin.build, plugin.verifyZip, plugin.diffRpc, store packaging, and on-device smoke before publish. Use when preparing a store release or tagged version.
Ingests fresh Steam Deck UI captures from the repo screenshots/ directory for visual debugging of Decky plugins and game-mode UI. Use when debugging layout, focus, QAM, or on-device behavior; when the user runs scripts/screenshot-deck.ps1 or mentions new screenshots; or when verifying UI against what the Deck actually…
Agentic tier-by-tier QA for Decky plugins: preGate → Tier 0 → Tier 1+ preview batches, evidence under docs/test-evidence/, doc writeback when the project defines prompt-testing docs. Pivot to single-scenario runs when a batch is flaky; use deck.deploy for deck-only scenarios.
Mandatory D-pad focus check on every Deck UI change. Invoke before marking done on component, focus-graph, or QAM/Settings control work. Requires on-Deck verification; preview mocks do not validate focus graphs.
Runs after a tool call finishes for Edit, Write, MultiEdit and NotebookEdit tool calls, executing decky-claude-hook.mjs via node with --match, --message, --tier and --run (3 commands). From qd313/decky-plugin-studio.
MCP server "decky-plugin-studio" as configured in qd313/decky-plugin-studio. Runs __DECKY_MCP_ENTRY__ with node.
★not rated 2 2d agoA
tokens not measured
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: