EvoX Docs
  • Product
  • Pricing
  • Docs
  • Marketplace
Back to EvoMap
Log InSign Up
Overview
Get started
Get EvoXUse EvoXImport experience
Available on
Desktop appEvoX CLIEvolver CLI
Foundations
PromptingPersonalize EvoXMemory and identitySkills and pluginsPermissions
Explore
PricingGlossary
Practice cases
Features
Configuration
Developers
Security
Administration
Overview
Get started
Get EvoXUse EvoXImport experience
Available on
Desktop appEvoX CLIEvolver CLI
Foundations
PromptingPersonalize EvoXMemory and identitySkills and pluginsPermissions
Explore
PricingGlossary
Practice cases
Features
Configuration
Developers
Security
Administration
EvoX docs/Introduction/Prompting

Prompting

Tell EvoX clearly about the goal, context, constraints, and expected result.

Prompt overview

Prompts tell EvoX what you want to learn, create, or change. A prompt can be a question, instruction, or goal. You do not need technical syntax or a fixed formula. Explain the need in your own words, review the response, and refine it with follow-up messages.

Short prompts are often enough. For larger or more important tasks, include the parts that truly matter:

  • Goal: What should EvoX do?
  • Context: What information or sources would help?
  • Output: What format, length, or level of detail do you need?
  • Boundaries: What must stay unchanged, what should EvoX avoid, and what requires confirmation?

Include only what helps. You do not need every item or a prescribed format.

Describe the result you need

Start with the desired result rather than listing every step. Include the audience or format when it changes what EvoX should produce.

Turn these meeting notes into a short update for the project team.
Put the decisions and next steps first.

This prompt explains what to create and who it is for. Describe a specific process only when the process itself matters; otherwise, leave EvoX room to search, compare information, and adjust its approach.

Choose the right way to work

Use Conversation for quick questions, Collaboration for substantial multi-step deliverables, and Coding for work that needs repository context and developer tools.

ConversationQuestions, explanations, summaries, and small revisions
CollaborationResearch, analysis, documents, presentations, spreadsheets, and workflows
CodingDevelopment, tests, debugging, and review with repository context

Add useful context

Add uploaded files, projects, memory, EvoX knowledge, and installed plugins. Include only task-relevant context and state boundaries for sensitive data and external actions.

Use voice dictation

When typing is inconvenient, select the microphone in the message composer and speak your prompt. EvoX converts it into editable text so you can review the transcription, add files or context, and revise it before sending.

Dictation is useful for longer ideas, quick context, and follow-up revisions. State names, numbers, and file names clearly for a more accurate transcription.

Ask EvoX

Listening…1s
Confirm each stepSwarm off
GPT-5.6 Terra High
Interactive · select the red button to stop

Common prompt patterns

Summarize and extract

Example request

Summarize the supplied material and extract conclusions, evidence, owners, dates, and open questions.

Compare options

Example request

Compare options by cost, benefit, risk, effort, and evidence quality, then recommend one.

Create a deliverable

Example request

Create a document for the named audience and check its structure and facts before finishing.

Research a question

Example request

Research the topic, separate facts from inference, and provide traceable sources.

Improve existing content

Example request

Preserve intent and facts, improve structure and wording, and list important changes.

Plan the work

Example request

Break the goal into steps with dependencies, owners, checkpoints, risks, and completion criteria.

Improve the result through conversation

The first prompt does not need to be perfect. Review the result and say what to preserve, remove, add, or reorganize. For larger tasks, ask EvoX for a plan, assumptions, and open questions before producing the final deliverable.

  • Make it shorter.
  • Give me three alternatives.
  • List the assumptions you made.
  • Ask me questions before continuing.
  • Check the facts and mark unsupported conclusions.

Review and finish

Before using the result, review key facts, numbers, sources, file contents, and execution outcomes. Require approval before publishing, deleting, paying, messaging, or changing production data.

PreviousFoundationsNextPersonalize EvoX