Use Rivya prompt templates, showcase pages, prompt cards, public starts, Studio handoffs, favorites, source tracking, and return context.

Use this prompt library and showcase guide when you need to understand how Rivya turns templates, examples, and prompt cards into real workflow starts.

Prompt pages and showcase pages are easy to underestimate in Rivya.

They are not just content surfaces. They are part of how the product turns inspiration into a runnable workflow.

The Two Main Public Page Types

Rivya currently exposes two prompt-oriented public page types across chat, image, video, and audio:

prompt hubs such as Chat Prompts, Image Prompts, Video Prompts, and Audio Prompts
showcase hubs such as Chat Showcase, Image Showcase, Video Showcase, and Audio Showcase

They are related, but not identical.

What Prompt Pages Are For

/{mode}/prompt is the prompt-library surface.

It is the right place when you want to:

browse prompt templates by mode
see featured prompts
search prompt examples
choose a template with a recommended model already attached

Prompt pages are more about reusable prompt patterns than finished public outputs.

What Public Prompt Pages Actually Show Today

Public prompt pages are currently driven by published prompt templates.

In practice, that means:

the list only shows templates from the current mode
only templates with status = published are visible
featured prompts are surfaced first
draft and ready templates stay internal to the admin console

So if a prompt template is still being edited, localized, or reviewed internally, it should not appear on the public /{mode}/prompt page yet.

What Showcase Pages Are For

/{mode}/showcase is the public example surface.

For image and video, showcase pages are more output-oriented and gallery-shaped.

For audio and chat, the current implementation can behave more like a prompt-first showcase, because prompt templates are often more useful than a static gallery in those modes.

That is why showcase is not one identical page type across every mode.

How Prompt Cards Work

Prompt cards carry more than a title and a sample.

They include things like:

the prompt itself
a summary and preview
a recommended model
preview media or transcript/output snippets
usage metrics such as views and favorites

That matters because the card is not just a content teaser. It is already part of the path into execution.

How “Use” Sends Work Into Public Start Pages Or Studio

This is one of the most important implementation details.

Prompt cards currently generate a useHref based on the viewer’s access level:

signed-out users are routed toward the matching public start page quick-start block
signed-in users can be routed toward studio

The prompt, recommended model, and optional reference asset can all be carried into that next path.

That is why prompt templates in Rivya are not passive reading material. They are launch points.

What Source And Return Context Do

Prompt pages and showcase pages also preserve context through fields such as:

source
returnTo

Those values help Rivya:

track where a prompt was launched from
preserve the page the user came from
return the user to the right listing or showcase context later

This may sound small, but it is one of the reasons the prompt layer feels connected to the product instead of detached from it.

Prompt templates also support favorite behavior, but that action depends on sign-in.

Right now:

prompt browsing is public
using a prompt can path toward public quick start or studio
favoriting requires account context

That is another example of the public start layer flowing naturally into the signed-in product.

Why Prompt Pages Matter

Prompt library pages help Rivya in three ways:

they reduce blank-page friction
they attach examples to real model paths
they let users move from inspiration into action without rebuilding setup from scratch

That is why they deserve to be documented as part of the user workflow, not treated as simple promotional pages.

Prompt And Showcase Checklist

This checklist helps decide whether the need is a prompt pattern or proof browsing:

Use prompt pages for a reusable starting structure.
Use showcase pages for examples, samples, or a better sense of output direction.
Check whether the card sends work into a public start or a signed-in Studio path.
Preserve source and return context when a prompt moves into execution.
Treat favorites as an account feature, not a public anonymous guarantee.

Recheck When A Card Becomes Actionable

Recheck when prompt cards, showcase examples, favorites, or use links change behavior. These pages sit close to conversion, so small routing changes can alter expectations.

Rivya Prompt Library and Showcase Guide