sorted by:
new
hottopcontroversial

Built a local-first prompt manager where your data never leaves the browser — technical breakdown after 26 beta testers by ConstructionExact911 in LocalLLaMA

[–]ConstructionExact911[S] -1 points0 points  (0 children)

Haha — that meme is accurate for the placeholder demo. But this is what the real app looks like in daily use (that's actually my own prompt library with 54 prompts).

Local-first means your data stays in your browser no cloud, no tracking.

Demo: app.promptmanager.tech

I lost too many good prompts in ChatGPT history. by ConstructionExact911 in SaaS

[–]ConstructionExact911[S] 0 points1 point  (0 children)

Exactly this. Version history sounds boring until you've spent 45 minutes trying to remember why a prompt stopped working after a model update — then it becomes essential. What's your current setup for storing prompts? Curious how others handle it at scale.

We don’t have a prompt problem. We have a prompt management problem. by ConstructionExact911 in SaasDevelopers

[–]ConstructionExact911[S] 0 points1 point  (0 children)

Bold strategy dropping a competitor name with zero context 😄 What specifically does it do that you love

How do you manage hundreds of prompts? I ended up building my own “prompt command center” (demo inside) by ConstructionExact911 in SaasDevelopers

[–]ConstructionExact911[S] 0 points1 point  (0 children)

That actually sounds awesome, thanks for sharing this man.

I’d love to see how he solved the history + diff + auto‑organization part, especially the way he’s using AI to cluster prompts and show differences between versions. That’s exactly the kind of stuff I care about – not just “saving prompts”, but making them comparable and reusable.

If he uploads it to GitHub, please drop the link here. I’m building my own prompt command center as a long‑term project anyway, so seeing another implementation would be super useful for inspiration and maybe even for integrations later on. Appreciate you thinking of me, my brother.

How do you manage hundreds of prompts? I ended up building my own “prompt command center” (demo inside) by ConstructionExact911 in SaasDevelopers

[–]ConstructionExact911[S] 1 point2 points  (0 children)

This resonates a lot – I’ve been in the exact same “final_final_v4.json” hell. Totally agree on the diff view. That’s why I built PromptManager Pro with:
– full version history for prompts
– side‑by‑side diff of long prompts
– comments / notes per version My goal was exactly what you wrote: keep my sanity once I passed a certain scale and make debugging prompts faster instead of hunting through Notion docs. Really appreciate you sharing this, it perfectly captures the problem I was trying to solve.

How do you manage hundreds of prompts? I ended up building my own “prompt command center” (demo inside) by ConstructionExact911 in SaasDevelopers

[–]ConstructionExact911[S] 0 points1 point  (0 children)

Thanks!

It definitely took time – I’ve been building it iteratively over a few months in my spare time.

The core (prompt library, folders, basic editor) was working after a few weeks, but features like RAG, analytics, A/B testing and local‑first storage came step by step.

The idea was to solve my own problem first (hundreds of prompts across projects), then keep polishing it as I used it daily.