Writing & chat · guidance updated 15 Nov 2026
Mistral (Le Chat / Vibe) prompt guide
Work unifies chat and agentic workflows. Use fast/think toggle for conversational or reasoning depth. Always review outputs as drafts—verify facts, dates, names, and source references before use.
How to prompt Mistral (Le Chat / Vibe)
- Start with 'You are a [role]; your task is to [task].'
- Describe the outcome, not steps—Work breaks down and routes automatically.
- Name sources explicitly: Files, Connectors (Gmail, Outlook, Slack, Notion, Linear, GitHub, Stripe, Atlassian, Google Drive, SharePoint), Libraries, Skills (@), or web search.
- State audience, length, tone, format, and deadline as constraints.
- Use objective measures ('200 words', '3 bullets') instead of 'short', 'interesting', 'better'.
- Organize longer prompts into Markdown or XML sections for readability.
- Avoid contradictions; use decision trees (if/then chains) when logic branches.
- Avoid subjective words ('too long', 'many', 'stuff') and blurry adjectives.
- Provide few-shot examples (input/output pairs) to clarify format and behavior.
- Use fast/think toggle: fast for turn-based chat, think for planning and complex reasoning.
- Reference Skills with @ for repeatable templates and methods.
- Treat Work outputs as drafts; verify facts, dates, names, and references before using or sharing.
- Expect approval prompts before sensitive actions; stay in control by monitoring progress and todos.
The shape of a good prompt
You are a [role]; your task is to [task]. ## Context [files, Connectors, Libraries, Skills (@), or web search] ## Audience [who reads this] ## Constraints [length, tone, format, deadline, decision rules as if/then] ## Examples [input/output pairs if format clarity needed] ## Output [format, sections, word-based scales]
Avoid
- Subjective size or quality words ('too long', 'interesting', 'better')
- Contradictory instructions without clear priority or decision tree
- Numeric rating scales; use word-based scales instead
- Micromanaging Work's steps; let it plan and ask approval for sensitive actions
- Blurry quantifiers ('many', 'few', 'stuff', 'things')
- Treating Work output as final before review; always verify facts, dates, and references
- Assuming Work outputs are production-ready without human review
Example
Request make a one page brief on electric bikes for my team
You are a market analyst; your task is to produce a one-page brief on the European e-bike market. ## Context Research the web for sources from the last 18 months. My team is deciding whether to stock e-bikes in our UK bike shops. ## Audience Shop managers with no analyst background. ## Constraints - Under 400 words - Plain, neutral tone - If data is UK-specific, prefer it; otherwise use EU data and say so ## Output Sections: Market size and growth, Top-selling categories, Price bands, Risks, Recommendation. Rate overall opportunity as Low, Medium or High and cite sources for each figure.