Skip to main content
The Prompt Library gives every user instant access to a curated set of prompt templates right from the Chat home screen. Instead of writing a prompt from scratch, you can browse categories, preview a prompt, and send it in one click.
Prompt Library on Chat Home Screen

​
How It Works

When you open the Chat home screen, category pills appear below the input box. Each pill represents a prompt category. Clicking a category opens a panel with all available prompts in that category.
1

Choose a category

Click on one of the category pills below the input box (e.g., Write, Learn, Code).A floating panel opens with the list of prompts available in that category.
2

Preview a prompt

Hover over any prompt in the list. The first line of the prompt template is previewed directly in the input box, so you can see what it will send before committing.
3

Select and send

Click the prompt you want. The full prompt template is loaded into the input box. You can then:
  • Edit the text to add your own context or details before sending
  • Press Enter to send the prompt as-is to the AI agent

​
Default Categories

The Prompt Library ships with the following default categories, each containing ready-to-use templates. The list is shared per deployment and can be customized through the Category Management API below — translate the labels, add a new pill, or remove one you don’t want.

Write

Professional writing and communication: executive summaries, client emails, meeting notes, business proposals, release notes.

Learn

Knowledge extraction and understanding: explain a concept, summarize a document, compare options, industry briefs, Q&A generation.

Code

Software development assistance: code review, debugging, API design, SQL query building, test case generation.

Coach

Professional guidance and mentoring: constructive feedback, presentation prep, difficult conversations, career strategy, interview preparation.

Brainstorm

Ideation and creative problem solving: idea generation, SWOT analysis, user stories, name generation, risk assessment.
The shipped configuration also includes empty categories ready to be populated: Sales, Support, Marketing, Engineering, and General.

​
Prompt Scopes

Prompts can live at three different scopes. Users always see the union of the scopes that apply to them.
ScopeVisible toEditable byUse case
GlobalEveryone on the platformPlatform administrators onlyCurated, expert-crafted templates shipped with the product
OrganizationAll users in that organizationOrganization administratorsOrg-specific prompts (internal style guides, company processes)
AgentUsers interacting with that specific agentAgent ownersPrompts that only make sense for one agent (e.g. an HR-onboarding agent’s intake questions)
When a user opens the chat home, they see global prompts + their organization’s prompts. When they open a specific agent that has its own prompts, they additionally see that agent’s prompts. Global prompts are read-only — organizations and agent owners cannot modify or delete them, only add their own on top.

​
Prompt Template Structure

Each prompt template includes:
FieldDescription
NameUnique slug used to identify the prompt (e.g. write-executive-summary)
TitleShort, descriptive name shown in the category panel
DescriptionBrief explanation of what the prompt does
ContentThe full prompt text, crafted with expert instructions for the AI
ArgumentsPlaceholders you can fill in (e.g., topic, context, code)
CategoryThe category pill it appears under
TagsSearchable keywords for discovery
ScopeWhich agents or organization the prompt belongs to
Some prompts also include tool guidance — they can suggest or force the AI to use specific tools (e.g., web search, knowledge base) to produce better answers.

​
Example: Using a Prompt Template

Here’s a typical workflow using the Write > Executive Summary prompt:
  1. Click the Write category pill
  2. Click Executive Summary in the panel
  3. The input box fills with the prompt template
  4. Replace the placeholder with your topic or paste your document content
  5. Press Enter to get a professional executive summary
The AI will follow the template’s expert instructions — in this case, producing a concise summary focused on key findings, business impact, and recommended next steps, in a tone appropriate for a C-level audience.

​
Agents Using Prompts as Tools

Beyond the Chat home screen, agents themselves can call the Prompt Library at runtime. The library exposes a prompt_library tool that an agent can use to:
  • Search for relevant prompts by keywords or category
  • Fetch a specific prompt by name
  • Apply the prompt’s expert guidance to its own answer
This means even when the user types a free-form question, the agent can decide on its own to consult the library and produce a higher-quality answer following an expert template. When the agent calls the tool, the search is automatically scoped to:
  • The user’s organization prompts
  • Global prompts
  • The current agent’s own prompts (if any)
The user does not see the tool call directly — they just get a better answer.

​
For Administrators

The Prompt Library is fully manageable through a public REST API. Each operation is authenticated and scoped to the caller’s organization.

List & search

Paginated listing with filters by category and agent. Returns total count, page, and limit.

Create

Add a new prompt scoped to your organization, optionally pinned to a specific agent.

Update

Edit any field of an organization prompt — title, content, arguments, category, tags, or enabled state.

Delete

Remove an organization prompt. Global prompts cannot be deleted via the API.

​
Endpoints

MethodPathAction
GET/v1/promptsList prompts (with page, limit, category, agent_id filters)
POST/v1/promptsCreate a new prompt
GET/v1/prompts/:nameFetch a single prompt by name
PATCH/v1/prompts/:nameUpdate fields on an existing prompt
DELETE/v1/prompts/:nameDelete a prompt
All endpoints require authentication. Organization prompts are visible only to members of the same organization; global prompts are visible to everyone but read-only.

​
Permissions

OperationGlobal promptsOrganization promptsOther org’s prompts
Read (list / get)VisibleVisibleNot visible
CreateNot allowed (admin-seeded only)AllowedNot allowed
UpdateNot allowedAllowedNot allowed
DeleteNot allowedAllowedNot allowed

​
Use Cases

Internal Style Guide

Create org-wide prompts that enforce your company’s tone, formatting, and terminology in every generated email or document.

Per-Agent Specialization

Pin prompts to a specific support, HR, or sales agent so they only appear when users interact with that agent.

Compliance Templates

Provide vetted templates for regulated workflows (legal disclosures, customer notifications) that users can run in one click.

Bulk Onboarding

Seed a new agent with a curated set of prompts at creation time, scoped to that agent only.
Prompt and category management are entirely driven by the REST API documented on this page. There is no dedicated admin UI today — call the endpoints from your own tooling, scripts, or an HTTP client.

​
Category Management

The category pills shown on the chat home screen are read from the deployment’s configured category list. Administrators can list them, rename them (for example to translate the default English labels), add new ones, or remove ones they don’t want.

List & inspect

Read the current category list with GET /v1/categories. Each item is a string used both as the slug stored on prompts and as the label rendered in the UI.

Rename

Use PATCH /v1/categories/:value to replace a category by its translated label (e.g. rename write to Écrire).

Add

Use POST /v1/categories with { "value": "<string>" } to append a new category to the list.

Remove

Use DELETE /v1/categories/:value to remove an entry from the list.

​
Category Endpoints

MethodPathAction
GET/v1/categoriesList configured categories (returns { items: string[], total })
POST/v1/categoriesAdd a new category. Body: { "value": "<string>" }. 409 if already present
GET/v1/categories/:valueFetch a single category. 404 if unknown
PATCH/v1/categories/:valueRename a category. Body: { "value": "<new>" }. 404 if unknown, 409 if the new value is already taken by another entry
DELETE/v1/categories/:valueRemove a category. 404 if unknown. 204 No Content on success
Renaming a category with PATCH updates the configured list only — it does not rewrite the category field of existing prompts. To fully localize the library, also update each prompt with PATCH /v1/prompts/:name so its category matches the new value.

​
Example: translate the default categories

To switch a deployment from the default English labels to French, do it one category at a time so users never see a half-translated UI:
  1. Pick one category (e.g. write).
  2. PATCH /v1/prompts/:name on every prompt that has category: write to set the new value (e.g. Écrire).
  3. PATCH /v1/categories/write to rename the pill itself.
  4. Move on to the next category.
If you do all the /v1/prompts updates first and the /v1/categories updates after, there is a window where users click the old pill (write) and see nothing because every prompt has already moved to Écrire. Doing it per category, or during a low-traffic window, avoids that. 
# Base URL convention used in all examples below
export PRISME_API_BASE="https://api.studio.prisme.ai/v2/workspaces/slug:prompt-library/webhooks/prompt-library"
# (use https://api.sandbox.prisme.ai/... on the sandbox environment)

curl -X PATCH "$PRISME_API_BASE/v1/categories/write" \
  -H "Authorization: Bearer $WORKSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "value": "Écrire" }'

​
Permissions

  • GET endpoints (list / single) accept any authenticated caller (user session or workspace API key).
  • POST, PATCH, DELETE require a workspace API key (Authorization: Bearer <workspace-api-key>). User sessions are rejected with 403, even for admin users, because the configured list is shared across the whole deployment and must be managed by a service credential.
  • Concurrent mutations are serialized: a second admin call that arrives while another mutation is in flight is rejected with 429. Retry after a few seconds. In practice this only matters if you script bulk renames in parallel.
The configured list is shared across the whole deployment — every user in every organization sees the same pills.

​
Privacy & Security

Prompts are stored in a secured library with strict scoping rules:
  • A user only sees prompts that belong to their organization, or globals shared with everyone.
  • An organization cannot read or modify prompts of another organization.
  • An agent’s prompts are only visible when interacting with that agent.
Authentication is required for every prompt operation, both from the chat UI and from the API.