Prompt Studio
Prompt Studio is the section of the web dashboard where you configure personal templates for AI responses. A template defines the tone, style, and focus of the assistant: one setting for interviews, another for sales, another for technical discussions.
Why use Prompt Studio
By default the assistant responds in a general style. If you set a template, every response will account for your role and context: instead of "explain the Singleton pattern" — "explain the Singleton pattern briefly, no UML, as if I'm a Python developer."
Where to find it
Open the web dashboard → Settings → Prompt Studio.
📸 [Screenshot: Prompt Studio section — list of templates with a "Create" button]
Creating a template
- Click "Create template".
- Enter a name (visible only to you).
- Choose the model role the template applies to:
responses,coding,system_design, or another. - Write the template text — the system instruction for the assistant.
- Click "Save".
📸 [Screenshot: template creation form — name, role, and text fields]
Activating a template in a session
- Dashboard or client → session settings: select the desired template from the dropdown.
- The template applies to all requests in the current session.
- If no template is selected, the assistant works in standard mode.
What makes a good template
A good template answers: "Who am I, who am I talking to, and how should the response be formatted?"
Example — template for technical interviews:
You are an assistant during a Python technical interview.
Answer concisely: lead with the key point (1–2 sentences), then show a code example.
Avoid theoretical introductions — get straight to the point.
For architecture questions, give a structured answer without digressions.
Example — template for negotiations and sales:
You are an experienced negotiator.
When handling a client objection: first acknowledge it, then reframe, then propose a next step.
Keep answers short — no more than 3 sentences.
Managing templates
- Edit: click the template → change fields → "Save".
- Delete: click the delete button next to the template; this action is irreversible.
- Order: templates appear in the order they were created.
Common issues
| Issue | Cause | Fix |
|---|---|---|
| Template not affecting responses | Not selected in session settings | Make sure the right template is activated before starting |
| Responses got worse | Template restricts the model too much | Reduce constraints or remove conflicting instructions |
| Template didn't save | "Save" button not clicked | Always click "Save" after making changes |
Best practices
- One template, one task: create a separate template for each meeting type.
- Keep it short: 3–5 sentences is enough; long templates dilute focus.
- Test it: create a session with the new template and ask a couple of questions before your real call.
- Combine with user context: the template sets style, the context provides facts — together they produce precise answers.