Yep, that’s the idea. You just type what you’re trying to do — like “debugging prompt for React errors” or “explain code to a junior dev” — and it finds the best one you’ve saved for that use case.

Super handy if you’re jumping between projects or tools and don’t want to reinvent prompts every time.

Out of curiosity — how are you currently managing your own prompts?

Just saving them on side notes.. so are you also injecting parameters for templates?

Nice — that’s what I used to do too (Notion, Apple Notes, random files everywhere).

And yeah, you can create templates with parameters — for example, something like:

Write a {tone} product description for a {product_type} targeting {audience}

Then when you reuse it, you just fill in the values. Makes it super easy to adapt prompts without rewriting the whole thing.

Would love to know how you would use that — have any prompt templates you always reuse?

Totally get that — I felt the same with most prompt libraries. That’s why I built EchoStash to be more like a “prompt memory” — quick search, AI retrieval, and no clutter.

I have many obviously, i rather not say. I just found prompt libraries to be inefficient for me. It’s just another place that I’m loosing my prompts in.