Prompt name & description
Give your prompt a clear purpose so you can find and reuse it.
AI Playground guide
Start with Quick Build, improve your prompt in the unified Studio, then explore workflows and agents when you are ready. You do not need to configure everything at once.
Open AI PlaygroundYou only need two main screens to get started. Start with a working result, then improve the instructions in one workspace.
Choose Customer Feedback Analyzer or another template. Use sample input, then run.
Replace the sample with your own request and compare the result.
Open Customize in Studio. Edit prompts, variables and run settings, then test in the same workspace.
Edit instructions and test your prompt side by side, without navigating between multiple editor pages.
Give your prompt a clear purpose so you can find and reuse it.
Describe the task, required context and desired output format.
Set the role, rules, boundaries and tone.
Define reusable placeholders, descriptions, defaults and required inputs.
Choose the supported AI model and access method for the run.
Use lower values for consistency and higher values for variation, depending on model support.
Control the upper limit of response length.
Where supported, enable additional reasoning for complex tasks; it can affect latency and usage.
Save improvements as versions and compare iterations.
Enter sample values, inspect the rendered prompt, run and review the result.
Analyze this customer feedback.
Identify sentiment, themes, pain points, urgency and recommended actions. Return clearly labeled sections.
Analyze only the supplied feedback. Do not invent details. Explain urgency using evidence; distinguish facts from assumptions and return prioritized, actionable recommendations.
Step 1
A project keeps related prompts, workflows, agents and execution history together.
Step 2
Write and test reusable AI instructions. Variables make each prompt reusable.
Step 3
Arrange tested prompts into ordered steps and pass one step’s output to the next.
Step 4
Give a tested workflow a clear role, goal, instructions and reusable identity.
Practical examples · Knowledge & RAG
Try a simple FAQ assistant, a policy evidence assistant, and an advanced support knowledge assistant. Includes copy-ready prompts, sample knowledge, test questions, and evaluation checks.
Explore Knowledge & RAG ExamplesEnd-to-end examples
Follow a real use case from Prompt to Knowledge, Workflow, Agent and MCP. Each guide includes copy-ready prompts, mappings, test data and success checks.
Career use case
Compare a candidate profile with a real job, retrieve evidence from the CV, create an improvement plan and optionally enrich the analysis with live company research.
Open case studyProduct operations use case
Turn customer feedback into grounded themes, priority decisions, owners and a safe response while checking related live support signals.
Open case studySample input is an example, not fixed production data. Replace it with your own input before a real run.
Prompt
Use Quick Build sample input first; in Studio, variables and default values make your prompt reusable.
Workflow
Define a sample value for each starting input, then use “Use sample workflow input”.
Agent
The agent starts with workflow examples, which you can customize before saving the agent.
{{variable_name}}.Example 1
Sample input · customer_feedback
The product is useful, but onboarding was confusing and I could not find the export option.
Expected result: Sentiment, friction points and a prioritised action plan with owners and expected outcomes.
Example 2
Sample input · candidate_and_job
Candidate: Senior Python engineer with FastAPI, AWS and ML experience. Role: GenAI engineer requiring Python, Azure OpenAI, RAG and stakeholder communication.
Expected result: Match score, strengths, missing skills and concrete CV/interview improvements.
Example 3
Sample input · topic
How small businesses can use AI agents safely without losing human oversight.
Expected result: A structured research summary followed by a concise, audience-friendly LinkedIn draft.
Example 4
Sample input · support_ticket
Customers cannot export invoices after today’s release. Three enterprise accounts are affected and receive a 500 error.
Expected result: Category, urgency, impact, recommended owner and a safe first-response plan.
Example 5
Sample input · meeting_notes
The team agreed to complete API testing by Friday. Maya will prepare test data. Jonas will review security findings. The release decision is Monday.
Expected result: A concise summary plus action items, owners, deadlines and unresolved decisions.