Put a short instruction file where your coding agent reads repository guidance: CLAUDE.md for Claude Code, AGENTS.md for agents that support it, or the corresponding Cursor or Copilot instruction file. Name your Driver codebase and the branches relevant to the work.
The example below adapts to Basic and Advanced Codebase Context. Keep the availability checks so the agent does not assume that every connected repository has generated maps or relationships.
markdown
# Driver
Use Driver for context from connected repositories. Basic provides source access and search. Advanced adds prepared maps, relationships, impact, history, and task-specific context when enabled.
## Before anything else
- Call get_codebase_names and match this repository by its name or git remote. Use include_metadata=true if needed. Call get_branches to confirm the intended branch.
- Pass the verified codebase_name and branch_name where supported. Driver reads committed repository state; compare the response's revision with the local checkout when recent changes matter.
- Check the tools the connection actually offers. Do not call an unavailable Advanced tool or treat missing prepared context as an empty codebase.
## Orient with the available tools
- With Basic, use glob_files to find paths, grep_source to find identifiers or error strings, and get_source_file to read the relevant code. Narrow a truncated search rather than inferring what the omitted results contain.
- With Advanced context prepared, use get_atlas_index to identify subsystems and get_atlas_detail for the relevant sections. Check completeness and the generated revision before drawing conclusions.
- Use get_code_map when available to select files by purpose. Follow source citations to verify the implementation.
- If request_context is available, describe the task, constraints, verified codebase, and branch. Retain the returned request_id and use poll_context while queued or running; do not start a duplicate merely because the first response has no answer yet.
## Before you change anything
- With Advanced, use get_related on affected files and change_impact on changed symbols. Inspect candidate tests and dependents, using file_hint when a symbol is ambiguous.
- change_impact sees reference coupling, not every string-based contract. Treat no_hits_in languages as unverified and search for configuration keys, schema text, API payloads, and mirrored types.
- With Basic, use source search and direct reads to inspect callers, contracts, and tests. An unavailable relationship tool does not establish that a change has no dependents.
- Verify relevant source and interfaces in the local checkout. Driver's committed context cannot prove the behavior of uncommitted changes.
## When you are done
- Run the tests relevant to the actual change. Use candidate tests from Driver where available and add the checks needed for boundaries that the analysis does not cover.
- Cite source evidence for findings and distinguish implementation, tests, and verified runtime behavior.
## Never
- Treat a search miss or empty relationship result as proof of absence. Check completeness and search scope.
- Claim that a prepared view is newer than the revision it reports or that source code proves a production deployment.
- Add the repository root name to repo-relative file paths. Paths are repo-relative and analysis is per committed branch.