VS Code / Cursor extension for Decky plugin development — live QAM preview, MCP tools for Deck debug & deploy, and an agent pack for your plugin repo
This repository also configures its own agents. See what decky-plugin-studio tells them →
Skill Cursor needs its repo
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.
Skill Cursor
Static focus audit for Decky plugins: Focusable callbacks vs DOM keydown, modal cancel/OK, plugin.lintFocus evidence. Escalate on-device issues to decky-debugger. Use before merging navigation-heavy UI or when reviewing D-pad routing.
Skill Cursor
First-hour Decky plugin setup with Decky Plugin Studio: Init Pack, deck.configure, focus lint, first build/deploy, deck.openPlugin (opens the panel on the Deck), and first screenshot. Use when onboarding a new plugin repo or helping a new contributor get unblocked.
Skill Cursor
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.
Skill Cursor
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…
Skill Cursor
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.
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: