Add steam-win-notify plugin

[SnakyWarrior]

steam-win-notify

Intercepts Steam in-client notifications and forwards them as native Windows 11 toast notifications. Also monitors controller connect/disconnect/battery status via XInput polling.

Features

• Native Windows toasts for Steam notifications (downloads, chat, invites, achievements, etc.)
• Controller connect/disconnect/battery level notifications via XInput polling
• Settings panel to toggle which notification types appear
• Works entirely in the background — zero UI footprint

Technical

• Written entirely with AI assistance (opencode / Claude)
• Frontend: TypeScript/React (SP) hooking into Steam's NotificationStore
• Backend: Lua with persistent PowerShell daemon for WinRT toasts + XInput polling
• No C++ compiler needed

Maintainer wanted

I don't know how to code — this was made entirely with AI. If someone wants to take over maintenance, improve it, or fix bugs, please reach out. I'm happy to transfer the repo.

[BambooFury]

If you're creating a plugin using AI, do it right. Otherwise, if you don't understand anything, you shouldn't have created it in the first place. Your project will require a lot of changes, but shdwmtr will check it and give you the answer anyway

[SnakyWarrior]

If you're creating a plugin using AI, do it right. Otherwise, if you don't understand anything, you shouldn't have created it in the first place. Your project will require a lot of changes, but shdwmtr will check it and give you the answer anyway

I created this project for myself simply because I wanted to, but I figured it would be worth sharing with others. I even mentioned that if someone wants to maintain it, I’m happy to transfer the repository. Honestly, who are you to tell me what I can or cannot create?

[BambooFury]

I just stated a fact :) and you got offended

[SnakyWarrior]

"you shouldn't have created it in the first place" Is that your fact?

[BambooFury]

Well, if you don’t fully understand how your own plugin works, why release it publicly? Your commit says version 1.1.0, while the plugin.json still shows 1.0.0 that alone already raises concerns. And if a user runs into an issue, how are you supposed to properly help or debug it if you don’t understand the underlying code behind the plugin yourself?

[BambooFury]

The Millennium project has an audience of over 3 million users, and you want to publish this plugin on the website even though you don’t even understand it yourselves. That’s pretty funny.

[SnakyWarrior]

It seems like you're the one taking offense here. I respect your coding expertise and the plugins you’ve built, but there are people like me who want to contribute to the community even if we aren't developers. I was completely transparent in the description, stating that this was made with AI and that I’m happy to transfer the repo to someone who can maintain it.
The plugin is functional—I’ve tested it and fixed bugs myself using AI. I actually felt relieved when I found a similar plugin made by an experienced coder because it proved the idea was solid. I shared this as a working concept. If a user has concerns, they can see my disclaimer in the description; I’m not sure why that bothers you more than it would the people actually using it.