Platform

Organizing Prompts with Collections

Learn how to create, curate, and share prompt collections on fireflare. Build topical libraries, collaborate with others, and use collections to grow your audience.

Organizing Prompts with Collections

Collections are fireflare's answer to bookmark folders — but more powerful. You can save prompts you've written or discovered into named, curated sets, share those sets publicly, and follow other users' collections. For power users, collections become a way to build an audience around a specific domain or workflow.

What Is a Collection?

A collection is a named, ordered set of prompts with:

  • A title and description explaining the theme
  • Any number of prompts — yours or others'
  • A visibility setting — public, unlisted, or private
  • A follow count — how many users have subscribed to updates

When you add a new prompt to a public collection, followers are notified.

Creating a Collection

  1. Navigate to your Library from the navigation bar
  2. Click New Collection
  3. Enter a title and description
  4. Set visibility (default: private, change to public when ready)
  5. Click Create

Your collection is created empty. Now add prompts to it.

Adding Prompts to a Collection

From a prompt page: Click the bookmark dropdown → select a collection (or create a new one on the spot).

From your Library: Open the collection → click Add Prompts → search for prompts to add.

From your own published prompts: Go to any prompt you've published → click Add to Collection → select or create a collection.

Curating a Great Collection

The best collections are more than just a pile of saved prompts. They have a clear purpose and are organized to be useful to someone with a specific goal.

Principles of Good Curation

Define a clear scope. "Useful prompts" is too broad. "Prompts for technical blog writing using Claude" is specific enough to be genuinely useful to a specific person.

Sequence matters. Order prompts from foundational to advanced, or in workflow order. If someone is following a process (research → outline → draft → edit), sequence your collection to match.

Quality over quantity. 10 excellent prompts beats 50 mediocre ones. Be selective. A collection that consistently delivers quality earns followers faster than a large but noisy one.

Keep it current. Remove prompts that no longer work well (e.g., prompts optimized for an older model that don't work as well with current ones). Add new prompts when you find strong ones.

Write a useful description. The collection description is searchable and shown in discovery. Be specific about:

  • Who this collection is for
  • What workflows it supports
  • What tools the prompts work best with

Example: A Well-Structured Collection

Title: Full-Stack Code Review Toolkit

Description: 12 battle-tested prompts for code review across the stack. Covers PR review, security audit, performance analysis, and documentation review. Works best with Claude Opus or GPT-4. Maintained weekly.

Contents (in order):

  1. Security audit prompt — SQL injection and auth
  2. Security audit prompt — dependency vulnerabilities
  3. Performance analysis — database query review
  4. Performance analysis — frontend bundle audit
  5. Architecture review — API design
  6. PR review — quick check (under 100 lines)
  7. PR review — thorough review (100+ lines)
  8. Documentation gap finder
  9. Test coverage analysis
  10. Accessibility review (frontend)

This collection tells a clear story and follows a logical structure.

Sharing Collections

Making a Collection Public

  1. Open the collection settings
  2. Change visibility from Private to Public
  3. Click Save

Public collections appear in search results and on your profile. They can be followed by other users.

Sharing a Direct Link

Every collection has a unique URL you can share directly. Unlisted collections are accessible only via this link — they won't appear in search.

Collections on Your Profile

Public collections appear on your profile page. Curators who build valuable collections often get more followers from their collections than from individual prompts.

Following Collections

When you follow a collection:

  • New prompts added to the collection appear in your feed
  • You receive a notification when the collection is updated (configurable)
  • The collection is saved to your Library for easy access

To follow a collection: Open any public collection → click Follow.

Collaborative Use Cases

Team Shared Library

Create a collection for your team's workflow (e.g., "Marketing Team Prompts"). Set to unlisted and share the link with your team. Everyone can access and save from the same curated set.

Course or Workshop Companion

If you're teaching a course or running a workshop on AI tools, create a collection of all prompts covered. Share the collection link with attendees — it's a living reference they can follow for updates.

Prompt Research

Building a comparison of different approaches to the same task? Create a private collection as a research workspace. You can make it public once you've organized your findings.

Collection Analytics

For public collections, you can see:

  • Follower count — how many users are subscribed
  • View count — how many users have opened the collection
  • Top prompts — which prompts in the collection are most liked/saved

Use this data to understand what your audience values and double down on those prompt types.

Key Takeaways

  • Collections are curated sets of prompts with a clear theme and audience
  • Sequence your collection — order matters for usability
  • Quality beats quantity; prune regularly
  • Public collections are discoverable and buildable into audiences
  • The collection description is SEO and discoverability real estate — use it well
All Guides