The Prompt Library (Work Station → Prompt) stores the prompts you use repeatedly, and calls them up inside any chat with a single slash command.
Why prompts
Writing the same detailed request again and again wastes time and produces inconsistent results. A saved prompt guarantees the wording, structure and context stay identical every time — and shares that quality across your team.
Create a prompt
- Open Prompt in the Work Station sidebar.
- Select Create Prompt.
- Fill in:
| Field | Purpose | Example |
|---|---|---|
| Prompt title | What you see when browsing the library. | "Weekly status report" |
| Command | The short slash command that invokes it. Use lowercase letters, numbers and underscores; commands must be unique. | onboarding_helper |
| Content | The full prompt text inserted into the chat. Include placeholders like [project] for the parts you vary. | "Summarise progress for [project] this week: wins, risks, next steps…" |
- Save. The prompt appears in your library and is immediately usable.
Use a prompt in chat
- In any chat, type
/in the message box — available prompts appear. - Select the one you need; its content is inserted into the message.
- Edit placeholders (for example replace
[project]with the real name) and send.
You can combine a prompt with attachments and capabilities as usual.
Shared prompts
Prompts created as public appear in the slash list for other users. Keep public prompts curated and genuinely reusable — too many public prompts make the picker noisy. Private prompts are visible only to you.
User vs Assistant prompts
When composing prompts you can frame content for two purposes:
- User prompts — describe context about you or the task, steering personalisation ("I am a site engineer; answers should assume Australian standards").
- Assistant prompts — instruct the assistant on its behaviour and output ("always reply in the format below"). These take precedence during generation.
Prompt settings that shape results
Saved prompts inherit the conversation's controls — Temperature, Top-P, Thinking (extended reasoning), Streaming display. Tune them in chat controls for best results with each prompt.
Best practices
- Use clear, descriptive titles.
- Make commands short and obvious (
/weekly-report, not/wr2). - Document required inputs in the prompt text.
- Test with a few different inputs before relying on a prompt.
- Share to your team by publishing; point them to this page for usage.
Related
- Templates — for full assistants with knowledge and tools, rather than a single prompt
- Chat Basics — the message box and input menu