Skip to content

Add Store Shortcut to Plugin Store - #1173

Open
TassaDarK-MGJ wants to merge 1 commit into
SteamDeckHomebrew:mainfrom
TassaDarK-MGJ:add-store-shortcut
Open

TassaDarK-MGJ wants to merge 1 commit into
SteamDeckHomebrew:mainfrom
TassaDarK-MGJ:add-store-shortcut

Conversation

@TassaDarK-MGJ

@TassaDarK-MGJ TassaDarK-MGJ commented Oct 28, 2026 •

Copy link
Copy Markdown

Add Store Shortcut to Plugin Store

Store Shortcut

Store Shortcut lets you open a library game's Steam store page without entering its game page first:

  • Context menu entry: "Go to store page" in the menu (☰) of a Steam game's capsule, in Home and every Library tab. It is hidden for non-Steam shortcuts.
  • Shortcut button: with a Steam game's capsule focused, press L3 (or R3, configurable, or off) to open its store page. The button bar shows the glyph and a "Store page" hint while such a capsule is focused. The plugin only listens to unhandled button presses, and Steam does nothing with L3/R3 in the library, so no native function is taken over.
  • The plugin's panel can turn each part on or off and shows whether each one is active or why it is unavailable. UI in English, French, Spanish, Italian and German (follows Steam's language by default).

I found no plugin on the store that does this.

Technical notes for reviewers:

  • Frontend only (@decky/ui, @decky/api, @decky/rollup, api_version: 1); main.py only stores the settings. No custom backend, no binaries, no root flag, no network requests of its own: the store page opens in Steam's own web view and B returns to the library.
  • The patches fail open: if a Steam update changes something the plugin does not recognise, that feature turns itself off and reports it in the panel instead of breaking Steam's UI. Both features are independent.
  • 52 unit tests (pnpm test). License 0BSD, with the template's BSD-3-Clause notice kept in LICENSE.

About the Generative AI checkbox

I have left that box unchecked on purpose, because it would not be true: most of the code was written by an AI coding assistant (Claude Code, Claude Opus) working under my direction. It was not "vibe coded", though:

  • Harness engineering: the project is built on the official decky-plugin-template, with the template's toolchain plus a harness around it: a lint that rejects legacy Decky APIs before every build, unit tests, a deploy script, and a CDP tool to inspect and record Steam's UI live.
  • Spec-driven development: I wrote a design document first (requirements, acceptance criteria, risks). Every Steam internal the plugin relies on was first checked with probes, small scripts run live inside Steam, before any of it was implemented in the plugin. The design document is in docs/DESIGN.md and the probe findings in docs/PHASE0-FINDINGS.md.
  • Human review and testing: I set the requirements, made the design decisions, and reviewed and tested all the final code and every feature myself on my device in Game Mode, following a device checklist (docs/device-checklist.md) that I re-run after Steam or Decky updates.

The plugin itself uses no AI or LLM at runtime.

I would rather be upfront about it than tick a box that isn't accurate. If that rules the plugin out, I understand; it stays available from the GitHub releases. If you are open to reviewing it anyway, I'm happy to make any changes you ask for.

About the SteamOS checkbox

I have also left "verified on the Stable and Beta update channels of SteamOS" unchecked: I tested it on Bazzite 44 (Steam client stable channel, build 1792618285, Decky Loader 3.3.0), not on SteamOS itself. That is why a third-party test on SteamOS matters here.

Task Checklist

Developer

  • I am the original author or an authorized maintainer of this plugin.
  • I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.
  • Generative AI was NOT used to write a majority of the code I am submitting.

Plugin

  • I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
  • I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

  • No: I am using a custom backend other than Python.
  • No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
  • No: I am using a custom binary that has all of it's dependencies statically linked.

Community

  • I have tested and left feedback on two other pull requests for new or updating plugins.
  • I have commented links to my testing report in this PR.

Testing

@TassaDarK-MGJ
TassaDarK-MGJ requested a review from a team as a code owner October 28, 2026 18:30
@github-actions github-actions Bot added the not-plugin Not related to plugins themselves label Oct 28, 2026
@github-actions

Copy link
Copy Markdown

Issues Found

No issues with your PR description were found.

Next Steps

  1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
  2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
  3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

@github-actions github-actions Bot added the plugin-addition Adding a plugin to the Plugin Store label Oct 28, 2026
@TassaDarK-MGJ

Copy link
Copy Markdown
Author

Hi! The not-plugin label was added by mistake: I first opened the PR without the # Add heading in the description and fixed it right after, so the labeler then added plugin-addition. I don't have permission to remove labels; could a maintainer remove not-plugin, please? Thanks!

@github-actions

Copy link
Copy Markdown

This pull request is stale as no updates or testing reports have been posted within the last 14 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

@github-actions github-actions Bot added the stale label Nov 12, 2026
@felixhirschfeld

Copy link
Copy Markdown

Hi! The not-plugin label was added by mistake: I first opened the PR without the # Add heading in the description and fixed it right after, so the labeler then added plugin-addition. I don't have permission to remove labels; could a maintainer remove not-plugin, please? Thanks!

Guess you have to ping a maintainer to get this recognized

@github-project-automation github-project-automation Bot moved this to Ready for review in Plugin Review Nov 12, 2026
@TassaDarK-MGJ

TassaDarK-MGJ commented Nov 12, 2026 •

Copy link
Copy Markdown
Author

Not stale: still interested in getting this reviewed.

@AAGaming00 @sidharthify sorry for the ping. Could one of you please:

  1. Remove the not-plugin label (added by mistake on my first submission, before I fixed the # Add heading).
  2. Approve the build workflow (first PR, so it is waiting on testing_env).
  3. Re-run it once I push a fix: the last run failed in "Find plugins to be built" with fatal: No url found for submodule path 'plugins/decky-ssh' in .gitmodules. That's my fault: when I updated my branch from main, the .gitmodules conflict resolution dropped the decky-ssh entry. I'll fix the branch and note it here.

I also saw the clarification in #1176 and #1178 about plugins developed mostly with an LLM. As I said in the description, I left that checkbox unchecked because it applies to this plugin. If that makes it ineligible, please just let me know and I'll close the PR myself; it stays available from the GitHub releases. If you're willing to look at it anyway, I'll make any changes you ask for.

I'm also looking for someone to test it on SteamOS Stable/Beta.

@TassaDarK-MGJ

Copy link
Copy Markdown
Author

Fixed: rebased the branch on current main as a single commit, so the diff is back to just the new submodule and its .gitmodules entry. "Find plugins to be built" now passes; "Build plugin" is waiting for testing_env approval.

@github-actions github-actions Bot removed the stale label Nov 13, 2026
@ynhhoJ ynhhoJ removed the not-plugin Not related to plugins themselves label Nov 16, 2026

@ynhhoJ ynhhoJ left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@github-project-automation github-project-automation Bot moved this from Ready for review to Approved, needs testing in Plugin Review Nov 16, 2026
@felixhirschfeld

Copy link
Copy Markdown

Hey, this is a really good plugin idea and also your methodology with using LLM or agents is quite interesting. I had some comments and then decided to fork it and open a Pull request with the changes: TassaDarK-MGJ/decky-store-shortcut#1 😀

  • The two fixes are actually necessary to make the layout look correct
  • The status refactor improves the accessibility because you could not see them without using your finger on touch screen
  • the last one is using the newly added explainer property from @decky/ui instead of the description because at least from my point of view this is the intended method for adding descriptions in the quick access menu. The Steam UI only uses the description on settings pages but not in the QAM.

@TassaDarK-MGJ

Copy link
Copy Markdown
Author

Thanks @felixhirschfeld! Replied in the plugin repo: your changes will go into 1.1.4, which I'll submit as an update once this PR is merged, so the current review isn't restarted.

@felixhirschfeld

Copy link
Copy Markdown

Plugin Testing Report

Installed Plugins

Store Shortcut - 1.1.3
MagicPods - 2.0.24
TabMaster - 3.0.1
HLTB for Deck - 2.0.12
SteamGridDB - 1.8.1
ProtonDB Badges - 1.3.4
Battery Tracker - 0.3.3

Specifications

OS Version 3.9.5 (Beta)
Steam Version 1793235415 (Beta)
Decky 3.3.1

Issues

Has the following major blocking issue(s): None
Has the following minor non-blocking issue(s): titleView className and some UI stuff as written in my other comment

Summary

The plugin works. Really nice idea.

This branch was successfully deployed

1 active deployment
testing_env — a44e0c0e Deployed Nov 12, 2026 by TassaDarK-MGJ via Build plugin (decky-store-shortcut, true) #4220
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugin-addition Adding a plugin to the Plugin Store

Projects

Status: Approved, needs testing

Development

Successfully merging this pull request may close these issues.

3 participants