菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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 shows.
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.
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.
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 preview.readLog MCP tools.
| name | decky-focus-audit |
| description | 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. |
Focusable, onMoveLeft/onMoveRight, or footer buttonsSearch src/ for anti-patterns:
| Anti-pattern | Prefer |
|---|---|
window.addEventListener("keydown" as primary D-pad | Focusable onMove* / onOKButton |
modal.contains(activeElement) gating alone | Ancestor walk from known shell ref |
el.style.* via ref on React-managed nodes | CSS vars on scope root + !important rules |
Confirm every interactive control is reachable via focus-graph callbacks.
With Decky: Open Preview open:
preview.runSequence — record focusPath after Down/Right sequences.preview.snapshotDom — confirm activeElement matches expected control.preview.compareScreenshot — coarse layout regression vs tests/preview-baselines/ when baselines exist.node scripts/run-preview-suite.mjs --filter=focus
Preview cannot reproduce Steam Input chords or real CEF focus. After static + preview passes:
deck.deploydeck.openPlugin checklistdeck.captureScreenshot or decky-screenshot-ingest for evidence| Finding | Route to |
|---|---|
| Design-time graph gaps (new modal flow) | decky-focus-architect |
| Runtime bug with logs/measurements | decky-debugger |