Designing a Prompt Marketplace

Public prompt marketplace as a foundation

By introducing a public prompt marketplace where users can publish, browse, and save prompts into their own workspace, we unlocked the foundations for a managed prompt ecosystem and future playground features that reuse the same prompt assets across the web app, extension, and team accounts.

+

Product goals

• Launch the first version of a public prompt marketplace where users can publish prompts and save them into their own workspace.
• Increase user productivity and time on platform by offering a curated prompt library directly inside the product.
• Support cross-surface usage (web app and extension) with a single source of truth for all prompts.

UX goals

Make saving a prompt from the marketplace into a structured workspace a one-step alternative to existing ways of adding new prompts.

Make it easy to find relevant prompts in the marketplace and add them to a personal library for future use.

Make the transition from public library to personal space seamless when a user starts working with a marketplace prompt.

Keep marketplace interactions lightweight so they fit naturally into the existing prompt creation flow.

Success criteria

Events to track:

• prompt_saved
• prompt_published
• prompt_used_from_marketplace
• prompt_saved_from_marketplace

Inputs

Existing prompt management (private library, editor, history, variables) defined the data model and main workflows the marketplace had to align with.

Business requirements to plug marketplace publishing and "add from marketplace to library" into this system set the minimum surface the design needed to cover.

Constraints

New marketplace flows had to be embedded into the current Prompt Manager, which limited how much navigation and information architecture could change in one iteration.

The UX needed to blur the line between editing a prompt in the marketplace and in the private library, while still making ownership and state explicit, which pushed the design toward clear status labels, badges, and history views.

Users had to see a reliable history and current status for each prompt, which drove decisions around versioning, status changes, and how destructive actions (hide/delete) are communicated in the UI.

Patterns

• Category-grid marketplace landing
• Faceted filters (model, language, difficulty) + search
• Category cards with subtopic chips
• Timeline-based version history
• Timeline-based usage history
• Version/usage cards with inline primary actions
• Unified modal for enhance / save / publish
• Single metadata form for marketplace publishing

Prompt marketplace

I went with a familiar search-and-filter layout, with filters for model, language, and difficulty. On the main page, topics are grouped into clear categories; tapping a category drills down into a scoped view with a topic list and prompt previews. Users can also run a separate search scoped by author to quickly find prompts from specific creators.nngroup+2

Save prompt from marketplace

The prompt action buttons mirror the personal workspace pattern, so users don't have to relearn the flow. Saving a prompt from the marketplace is streamlined to just three clicks end-to-end.

Prompt details

The prompt details page surfaces what the prompt does, the prompt content itself with primary actions, a worked example, and a strip of similar prompts to explore related use cases.

Publish prompt

The flow supports smart auto-fill for title, category, subcategory, compatible models, and tags, so creators start from a sensible default rather than a blank form. They can accept, regenerate, or completely override any suggested metadata and enter their own details manually.

Edge case. Saved prompt was hidden or deleted

• If the marketplace author hides or deletes a saved prompt, its details page becomes an empty state.
• When the prompt was saved without local edits, the user also loses the option to restore that original version.