What makes a request easy to build
- What you want to see or press, in your own words. A key that does the thing, a number on a dial, a page that opens.
- What you would use it for. This matters more than the feature itself: the shape of a key usually falls out of the job it does, and knowing the job often changes the answer.
- Which Stream Deck you have — Mini, Standard, XL, Neo or the + — and whether the idea wants a dial.
- What it talks to, if the plugin talks to something: AMP, Proxmox, Plex, Jellyfin, Emby, a Pi, a game, and which version of it.
- A screenshot or a scribble of the layout, if you have one. A photo of the deck with sticky notes on it is clearer than a paragraph.
Nothing you send is published, and it goes nowhere but the inbox it arrives in. If a request turns into a feature, the release notes say what changed, not who asked for it.
Something broken instead?
That goes to the same address. It helps to say which Stream Deck you have, the plugin version from the Stream Deck app, and what you saw. Most of these keep a log beside the Stream Deck logs; each setup guide says where to find it.