Fresh drop from r/PromptEngineering: a small browser extension called Quib just hit 500+ installs and shipped v0.1.5. It tackles a problem most of us have and rarely talk about.
The problem is that your prompt library grows, and you use it less. Notion pages, text expanders and bookmarks all add friction. Every one of them asks you to leave the chat box, hunt through a list, copy something, come back and paste. Once finding the prompt takes longer than retyping it, the library is dead weight. Most of us have at least one folder of “great prompts” we haven’t opened in months, and the honest reason is that opening it costs more than it saves.
The twist is that Quib doesn’t try to be a better place to store prompts. It moves the library to where you’re already typing. In ChatGPT, Claude, Gemini or a Playground, you type / and your prompts show up right there under the cursor. You never leave the chat box. If you’ve used slash commands in Slack or Notion, the muscle memory is identical. There’s no new app to open and no new tab to keep pinned. The library meets you at the exact moment you need it, which is the only moment it matters.
The part I like most is the dynamic variables. Two of them are live right now:
{{selection}} wraps whatever text you’ve highlighted on the page.
{{clipboard}} drops in whatever you last copied.
So a prompt stops being a static block of text. It becomes a little template that grabs context for you. Think about how many times you’ve written “Summarize the following article” and then spent ten seconds pasting the article in. With a variable, that second half happens on its own. Highlight, slash, enter. The prompt already knows what you’re looking at.
Here’s the mini-workflow:
- 🔹 Install Quib. It comes with 7 starter prompts that already use the variables, so you can poke around before writing your own. Open a couple of them and read how the placeholders are placed. That’s the fastest way to learn the pattern.
- 🔹 Highlight a paragraph on any page, then open your AI chat. A news article, a contract clause, a confusing error message and a long email thread all work fine.
- 🔹 Type / and pick a prompt that contains {{selection}}, like a rewrite or summarize persona.
- 🔹 Hit enter. Your highlighted text is already inside the prompt. Skim it once to confirm the right text landed, then send.
- 🔹 For multi-step prompts, copy a snippet first and use {{clipboard}} to feed it in without any paste gymnastics. This works well when you’re comparing two things. Put one in the selection and the other on the clipboard, and a single prompt can reference both.
Pro tip: Write your best prompts once with a placeholder where the messy input goes. A good system prompt with {{selection}} at the bottom is basically a one-key tool for whatever you’re reading. Put your instructions and output format first, then the variable last, so the model reads the rules before it meets the content. A “turn this into three bullet points and one question I should ask” prompt is a good first candidate.
Pro tip: Keep the library small and sharp. If you only reach for six prompts a week, those six are the ones worth turning into variable-based templates. Name them with short, memorable words so you can type a few letters after the slash and filter straight to the right one. Retire the ones you never touch. A library you actually use beats a library that’s complete.
The builder is also asking the community which variables they’d want next. Ideas floated so far are {{url}} and {{tab_title}}, plus custom placeholders. If you’ve ever wished a prompt knew what page you were on, that’s your chance to say so. Imagine a research prompt that automatically cites the page it came from, or a prompt that tailors its tone to the site you’re on. Small additions like these are what would turn a handy shortcut into a real workflow layer.
It’s free to try with up to 25 local prompts, which is plenty to test whether the slash habit sticks. My suggestion is to start with your three most-used prompts, convert them to use variables, and see how your week feels. Find it at arkisoul.in/quib. And tell me in the comments: what variable would save you the most time?
Stopping prompt clutter: How I organize and trigger dynamic prompts ({{selection}}, {{clipboard}}) inline using /
by u/arpit-jain87 in PromptEngineering