Prompt Library

Organize reusable prompts by owner, use case, version, evaluation status, and where each prompt is used in production. The screen connects Prompts and Collections so platform and engineering teams can find the “New prompt” action while checking prompts and production.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Support triage · v12 and Meeting summary · v8, rather than an empty visual shell.

Prompt Library
Use this template in Figr

Template facts

Screen

Workspace

Primary action

New prompt

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Platform and engineering teams need a clear “New prompt” action without losing sight of prompts, production and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New prompt is clearly available where the task happens.
  • Main view: Prompts keeps the starting point obvious.
  • Connected view: Collections supplies nearby context.
  • Metric: Prompts is visible with a meaningful value.
  • Another signal: Production helps people judge what to do next.
  • Representative record: Support triage · v12 makes the example specific.
  • Second record: Meeting summary · v8 shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading prompts without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for collections; clarify who can continue.
  • Success after choosing New prompt; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Prompts → Collections → New prompt → Review outcome

Patterns used

Workspace, Prompts, Collections, Versions, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Support triage · v12 with Meeting summary · v8. Make prompts clear, then use production to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New prompt” action. The happy path alone is not enough.

Related UI examples: Model Playground, AI Evaluation, Feature Flags.

Start from this in Figr

Design a prompt library screen for our existing software product. Use our real design-system tokens, components and product language. Show Prompts and Collections, include believable records such as Support triage · v12, and make new prompt easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr