Best Practices

Give cloud agents clear work, bounded authority, and verifiable completion criteria.

Describe the outcome

Ask for observable behavior, not just an implementation technique. Include the relevant feature, constraints, and the checks that define completion. Attach files only when they are needed for the task.

For unfamiliar repositories, begin with orientation: ask the agent for entry points, key modules, and project instructions before requesting a broad change.

Keep related work together

Continue corrections in the same conversation so the agent retains context. Use a project and durable tasks when work spans conversations or people. Split overlapping or incompatible changes into separate worktrees, and claim exact shared files before editing them concurrently.

Review evidence, not confidence

An agent response is not proof that a change works. Review the diff and ask for the project’s real tests, type checks, lint, or build. For visible UI changes, require a recording of the actual interaction and verify the hosted playback link.

Publish deliberately

Confirm the selected repository, worktree, and branch before committing. Commit only the intended files. Treat commit, push, and pull-request creation as separate steps, and verify the remote result after publication.

Use the narrowest credential and network access that completes the task. Never paste secrets into prompts, repository files, terminal history, or demo recordings.