Getting Steam Deck Prompts Quick Working the Way It Should
I keep coming back to this because people ask about it constantly and almost nobody gets it working right the first time. Steam Deck Prompts Quick is basically a lightweight prompt management tool designed for the Deck's small screen and touchscreen workflow. You can create, organize, and run AI prompts directly from the desktop environment without jumping through SteamOS hoops. It's useful. It's also a little rough around the edges and the documentation skips over the parts that actually matter. The first thing you need to do is get it installed. Go to the official page and download the flatpak from Flathub. The native version works but you will run into permissions issues with the filesystem scanner later on. Flatpak sidesteps most of that. After installation, launch it from the Applications menu. The first run will ask you to point it at your prompt library. If you don't have one yet, just create a new directory and let it scan. The scan takes about twenty seconds on a fresh install. After that the interface opens and you can start adding prompts.
Steam Deck Prompts Quick Setup and Configuration
Once the app is running, the settings panel is where most people give up. I figured it out after breaking my prompt library twice. The main thing to understand is that the tool stores prompts as JSON files in your home directory under ~/.config/stDeckPromptsQuick/prompts/. Every prompt is its own file. This matters because when you sync between devices or back up, you just copy that folder. No database export nonsense. The settings you actually need to touch are the API configuration and the prompt template engine. Go to Settings and select your AI provider. If you are using OpenAI, put in your API key. The field is unmasked by default which is annoying on a small screen because you type it blind. Press the eye icon to verify what you pasted. For Claude or any other provider, pick it from the dropdown and enter your key the same way. Don't leave blank fields. The app will silently fail if an API key is missing and just show a generic error that tells you nothing. After the API is configured, set your default temperature and max tokens in the same panel. Defaults of 0.7 and 512 are fine for most things. If you are generating code or structured output, bump temperature down to 0.3 and max tokens up to 1024. The difference in output quality is noticeable and most beginners leave these at the defaults and wonder why the prompts come back half-baked.
The prompt template engine is the feature that makes this tool worth the friction. You can use variable placeholders like {subject} or {tone} and the app will prompt you for each one before sending. Set it up by going to any prompt, clicking Edit, and adding variables in curly braces. Test it by running the prompt. The Deck will show an input dialog for each variable. It works well once you are used to it. Here is something the docs don't mention: if you rename your prompt files manually while the app is running, the UI will show stale references until you restart. I ran into this when I reorganized my prompt library at 2 AM and spent twenty minutes thinking the app was broken. Restart fixes it instantly. Also, the Flatpak version needs filesystem access to your prompts folder. Grant it in the Flatseal settings or the app can't save new prompts. Skip this step and you will get write errors that look like disk full messages. The search function is fast but case sensitive. I lost an hour looking for a prompt I knew I had saved because I typed it in lowercase and the filename was capitalized. Use uppercase or lowercase consistently. The filter bar lets you search by tag too, which helps when your library grows past fifty prompts.
Get the Full Details
Running from Steam Big Picture mode is straightforward. Add the flatpak as a non-Steam game and launch it from there. The interface scales fine at the Deck's native resolution. The only issue is that the text input field sometimes doesn't get focus when tabbing through variables. Hit the search button on the right stick or tap directly in the field. It works every time after that.
