Collections
Your best prompts, organized
Build a library of reusable prompts. Group them by task, project, or whatever makes sense to you.
Playbooks, not bookmarks
Collections aren't just saved prompts. They're reusable toolkits you build over time.
Debugging playbook
Collect the prompts that reliably help you debug race conditions, memory leaks, or flaky tests. Next time, start with what works.
Code review checklist
Save prompts that catch common issues—security gaps, performance problems, missing edge cases. Run them against new PRs.
Migration toolkit
Keep the prompts that generated clean migration scripts, schema changes, and data transforms. Reuse them for the next migration.
Build as you go
No upfront organization needed. Star good prompts. Organize later.
Star first, organize later
When a prompt gives you a great result, star it. When you have a few starred prompts on a theme, group them into a collection. Natural workflow, no planning required.
Cross-project collections
A "debugging" collection can include prompts from any project. A "project-X" collection can include prompts from any tool. Organize by whatever dimension matters.
One-click reuse
Open a collection, find the prompt you need, copy it with one click. Paste into your current session. No friction between finding and using.
Frequently asked questions
What are prompt collections?
Collections are curated groups of prompts you organize by purpose. Think of them like playlists for your best prompts — a debugging collection, a code review collection, a migration toolkit. You build them from prompts you've already captured.
How do I add prompts to a collection?
Star a prompt from your timeline, then add it to a collection. You can create collections for any purpose and add prompts from any tool or project. Each prompt can belong to multiple collections.
Can I have multiple collections?
Yes. Create as many collections as you need. Common examples: 'Debugging playbook', 'Code review prompts', 'Migration scripts', 'Architecture decisions'. Organize by project, task type, or however you think.
What's the difference between search and collections?
Search is for finding a specific prompt when you know roughly what you're looking for. Collections are for curating prompts you know you'll want again. Search is reactive; collections are proactive.
Are collection names encrypted?
Yes. Collection names are encrypted with your vault key, just like prompt content. The server stores encrypted blobs for both.
Build your prompt library
Star, organize, reuse. Free to start.
Get Started Free