Fresh off GitHub, a VS Code extension just closed the gap between prompt chaos and prompt control. A Redditor who goes by Ge0rge3 built it after noticing their prompts were scattered everywhere. Some lived in Obsidian, some sat in a pile of notepad.exe windows, and some hid in random VS Code tabs that got closed and lost the moment the laptop restarted. One commenter on the original post joked that the “notepad.exe graveyard” felt way too real, and honestly, most of us have lived there at some point, squinting at a half-remembered prompt buried in browser history or a Slack DM to ourselves. The extension, called “vscode-prompt-studio,” is the fix for that exact mess.
Here’s the twist: this isn’t just a fancier notes app bolted onto your editor. The extension treats your prompts like first-class citizens of your codebase, not scraps you keep somewhere else. They live in a Markdown editor right next to your code, in the same window you’re already staring at for eight hours a day. On top of that, it plugs directly into Claude skills and lets you fire a saved prompt straight to Claude without ever leaving VS Code, which means no more alt-tabbing to a browser tab, pasting, waiting, and tabbing back.
That single change fixes the real problem behind the mess. Obsidian and notepad.exe are great at storing text, but they don’t know anything about the project you’re working in. Prompts sitting inside your repo get versioned with your code, so when you pull a branch, you also pull the prompts built for it. That means when a teammate opens the same repo six months from now, the prompt that debugged that gnarly race condition is sitting right there in git history, not lost in someone’s personal notes app. No more digging through three different apps to find the one reusable prompt that handled a tricky edge case last month, and no more that sinking feeling when you know you wrote the perfect prompt once and can’t remember where.
This setup makes the most sense for anyone building with Claude day to day. Think developers running the same debugging prompt across projects, teams sharing a house style for code review comments, or solo builders who keep reinventing the same “explain this function” prompt from scratch every single time a new file confuses them. Instead of hunting for a prompt you wrote three weeks ago, you scroll to the right section of a file you already have open, and it’s right there, tuned to this exact repo’s quirks.
Here’s the mini-workflow if you want to try it yourself:
- 📥 Install “vscode-prompt-studio” from the VS Code marketplace or straight from the GitHub repo.
- 📝 Create a Markdown file inside your project to hold your prompts, organized by task.
- 🔗 Wire up the Claude skill integration so the extension knows which skills to call.
- ⚡ Highlight a saved prompt and send it to Claude with a single command, no copy-paste required.
- Keep the file open while you work so your prompts stay in sync with the code they support, and update them the moment you notice a phrasing that works better.
A few pro tips before you build your own library:
- Name your prompt sections by task, not by date. “Refactor helper” beats “Prompt 3” every time you go looking for it weeks later, especially once the file grows past a dozen entries.
- Keep one prompt file per repo instead of one giant master file. It’s tempting to build a mega-library, but a scoped file stays fast to scan and easy to hand off to teammates who don’t want to wade through prompts for projects they’ve never touched.
- Test the Claude skill integration with a throwaway prompt first, so you know exactly what gets sent before you wire it into a real workflow. A quick “summarize this file” test tells you fast whether the wiring actually works.
- If you work across several repos, mirror the same section names in each one so switching projects doesn’t mean relearning your own system. Consistency here saves you the exact kind of hunting this extension is supposed to kill.
One caveat worth flagging: this is a young project, so expect some rough edges around syncing large prompt libraries or handling very long Markdown files. A small young project also means the template library is still thin, so you’re mostly building your own system from scratch, which is honestly half the point. Check the GitHub repo for the current feature list before you build a whole workflow around it, since issues and pull requests are moving fast right now.
If you’ve been keeping prompts in a mess of apps like the original poster was, this is worth ten minutes of your afternoon. Go grab “vscode-prompt-studio” from Ge0rge3’s GitHub, drop it into your next project, and see if it finally replaces your notepad.exe graveyard for good! 🚀
Built a VS Code extension for managing prompts to fix my mess
by u/Ge0rge3 in PromptEngineering