Create a reusable Prompt

Use Studio›Prompts ↗ to save prompt templates your team can reuse in Studio and in applications that reference shared prompt definitions.

• Reusable instructions: store system instructions, task templates, and output formats in one place.
• Versioning: update a Prompt without losing earlier versions.

By the end you will have a saved Prompt ready to test and reuse.

Time to complete: ~5 minutes

• An active Studio account.
• A prompt you want to reuse. Good first candidates are support tone guidelines, extraction instructions, or a structured summary format.

1. Open Studio›Studio ↗.
2. In the sidebar, open Build > Prompts.
3. Click New prompt.

Give the Prompt a clear title and description so teammates know when to use it.

Keep the description task-oriented. Explain the use case instead of restating the title.

Add the prompt text. Keep the instructions specific enough that another teammate can reuse the Prompt without extra context:

You are a customer support assistant. Acknowledge the issue, answer clearly, and propose the next action. Use a calm, concise tone for enterprise administrators.

1. Click Save or Create prompt.
2. Open the saved Prompt and review its first version.
3. Test it in a supported Studio surface, such as the Playground, before using it in an application.

Create a new version when you want to change the Prompt without overwriting the version that teammates or applications already use. Studio creates the new version after you save changes.

1. Open the Prompt from the Prompts list.
2. Update the prompt text.
3. Add version notes that explain what changed, such as Shorter support replies or Adds escalation guidance.
4. Click Save.
5. Confirm the version history shows the new version.

Older versions stay available for review and rollback. Test the new version before promoting it for production use.

If your workspace uses aliases, promote the tested version to an alias such as stable.

Your Prompt is ready if:

• It appears in the Prompts list with the right title and description.
• A test run produces the expected tone, structure, and constraints.
• The version history shows your original version and the updated version.