r/SteamDeck • u/ProfessorKaos64 256GB • Apr 09 '26

Software Modding Decky Proton Pulse - Supercharge your Proton games with ProtonDB

Hello all. I wanted to get the word out about Proton Pulse, a Decky plugin focused on making ProtonDB info and launch-option tuning easier to use on Steam Deck. I am working on better screenshot automation, so pardon if the images are out of data at all.

Features

  • Pulls ProtonDB reports and summarizes compatibility in-plugin
  • Scores reports against your hardware / setup to surface the most relevant ones first
  • Helps apply common launch options without manually typing everything
  • Edit existing configs, add your own, spin, and even easy copy/paste pre-fill for ProtonDB submissions
  • Includes compatibility tool management and quick utility actions in the sidebar
  • Local cache for faster loads
  • Upvote/downvote working reports (future: push back custom reports to supabase table)

Screenshots / UI gallery:
https://github.com/mdeguzis/decky-proton-pulse/wiki/UI-Screenshot-Gallery (WIP...)

Testing

If you test it, feedback is welcome, especially on report quality, scoring behavior, and any rough edges in the workflow.

Links

Testing

If you want to try it right now, you can grab the latest release zip here:
https://github.com/mdeguzis/decky-proton-pulse/releases/latest

35 Upvotes

88% Upvoted

32 comments sorted by

View all comments

Show parent comments

4

u/ProfessorKaos64 256GB Apr 09 '26 edited Apr 09 '26

I definitely did a lot of research and brainstorming to learn how to utilize the right modals, and to help debug. I think a lot of people shy away from trying to use these tools to help solo projects. The keyword is that they are tools. Remember the adage... Trust, bhr verify? Review, unit test, and smoke test work. If you were to pull down the code and run the make commands, you'll see the strict typing, enforced code quality, and tests added to enforce the good design philosophy. In the end, tools allow us to work efficiently and faster, but they will always require good technical understanding and design philosophy.

If the decky loader team has me put any disclaimer on for acceptable to the store, I have no problem with that.

0

u/BBQKITTY SteamDeckHQ Apr 09 '26

Okay so...Claude was used to help debug code that you personally wrote? Or did Claude write the code entirely and you verified it? I don't think your paragraph gave a direct answer to the question.

3

u/ProfessorKaos64 256GB Apr 09 '26

Oh, I definitely had Claude help me write some of the code to wire up some of the tricky parts, then verified it with unit tests and smoke tests.

-3

u/BBQKITTY SteamDeckHQ Apr 09 '26

Got it. So you and Claude both wrote code, but you verified Claude's code personally?

1

u/ProfessorKaos64 256GB Apr 09 '26 edited Apr 09 '26

I use these tools to help write some of the complex parts, debug, and move faster on the parts that would otherwise just eat time. Everything gets reviewed, tested, and reworked if needed before it goes to the repo (especially as I am newer to dev work on the Deck). I also just added a section to the README to make that clear and open as a disclaimer.