Task guides
Pick a task and go through the full cycle: give the agent the initial context, limit the scope of its work, ask for a check, and review the result. You can adapt the example prompts on each page to your own project.
Working with code
| Task | When to choose it |
|---|---|
| Understand unfamiliar code | You need to figure out how the code works without changing anything |
| Work with a large or legacy project | You need to explore a large codebase and split a change into verifiable steps |
| Get to grips with a library API | You need to check the API and behavior of a specific version of a dependency |
| Change code safely | You have a well-understood edit and it matters that nothing else is touched |
| Refactor code | You need to improve the structure of the code while preserving its behavior |
| Fix a bug | The error reproduces, and the cause needs to be confirmed rather than guessed |
| Review the agent's changes | The agent has made edits, and you need to review and accept them deliberately |
| Check code security | You need to find and analyze vulnerabilities before a commit, a release, or an audit |
Testing
| Task | When to choose it |
|---|---|
| Add tests | You need to lock in the behavior of the code with tests |
| Increase test coverage | You need to close uncovered lines and branches or pass a quality gate |
| Fix a flaky test | A test passes sometimes and fails other times without any changes |
| Create a test from a real execution | A complex scenario is easier to record while the application is running |
Preparing the project
| Task | When to choose it |
|---|---|
| Prepare Explyt to work with your project | You need to give the agent persistent context and check the restrictions before a large task |
| Connect an external tool | The agent needs access to a browser, a knowledge base, an issue tracker, or another service |
After your first task
A few general settings and reference pages are useful for day-to-day work:
- Context, chats, and memory — when to continue the current chat and when to start a new one;
- Permissions and safety — how to restrict access to files and tools;
- Plans and balance — how to estimate and reduce usage;
- MCP and external tools — how to connect knowledge bases, a browser, and other services;
- Active configuration — what affects the current chat;
- Troubleshooting — routes organized by the symptom you observe.
The general definition of done
For any route, the result must be verifiable. The agent's answer should contain the paths to the files it examined or changed, the checks it ran, and their results. If the agent changed code, also review the diff and make sure the changes did not go outside the agreed scope.