Primary navigation

Prompting

How to write good prompts in Chat, ZeroTwo Work, and Code

Prompting overview

A prompt may be a question, a request or a goal, phrased in plain words and refined through follow-ups. For larger tasks, cover whichever of Goal, Context, Output and Boundaries matter; none is mandatory.

Describe the result you need

Lead with the outcome and mention the audience or format when they matter, rather than listing steps.

Summarize these meeting notes as a short update, with decisions and next steps first.

Prescribe a procedure only if the procedure itself is the point.

Add useful context

Share only information that changes the outcome and say what to use from each source.

  • Attach documents, spreadsheets, slides or PDFs from the + menu (files).
  • Add an image for visual work.
  • Turn on web search when freshness matters.
  • Group shared files in a project.

Use connected sources

Name where to look and what to find. This needs the matching connector to be installed and signed in under Customize > Connectors.

Use the latest plan in Drive and the project Slack channel to draft a status update.

Use plugins

Plugins bring reusable instructions and tool links from a shared directory. Describe the result, or type @ to pick one; see plugins.

Personalize ZeroTwo

Standing preferences belong in Settings > Personalization, such as tone and custom instructions; one-off details belong in the prompt. See personalization settings.

Set boundaries that prevent real problems

Add one or two limits where a wrong change would hurt or you want to review first: keep approved figures fixed, rely only on supplied sources, stay in budget, or draft without sending.

Make the result ready to use

State how the output will be used so length and structure fit, such as a skimmable one-pager or an email with owners and dates. For important work request a final check, then verify it yourself.

Improve the result with follow-up messages

Iterate with targeted requests instead of restarting: add a source, change direction, ask for alternatives or adjust detail.

Steering and queuing

While a Work or Code run is in progress, a message you send can Steer the current run or wait in the Queue for the next turn. Queued messages show above the composer, where they can be edited or deleted. The default is set under Settings > General > Follow-up behavior.

Put the pieces together

A strong prompt names the goal and sources, the output and its ordering, the boundaries (keep dates, flag gaps, send nothing), and finishes by asking that every next step be given an owner and a due date.

Use voice dictation

Press the microphone in the composer, or Ctrl+Shift+D, to dictate into the message and edit it before sending.

Prompting examples for Chat

Chat suits questions, drafts and everyday decisions; state the outcome first.

Understand a topic

Explain compound interest to a beginner with one concrete example.

Draft and refine writing

Draft a warm decline to this invitation, under 120 words.

A draft can arrive as a writing block. Expand it to edit in a viewer tab, or select text and ask for changes. Add to Space saves it as a Page, after which its menu offers Open in Space, Download as Markdown, PDF or Word, and Version history, which keeps the last 10 saved versions with Restore this version.

Compare options

Weigh these two phone plans for occasional travelers in a table, then recommend one.

Make a practical plan

Plan five quick weeknight dinners, peanut-free, with one shopping list.

Prompting for Work

Choose Chat for quick questions and light drafts; choose Work for multi-source, multi-step jobs that change things or produce larger deliverables. Describe the result, supply sources, name the audience and say how you will review.

Use Work efficiently

Work runs spend credits, so it pays off most on recurring or time-heavy tasks. Aim for one reviewable result: limit sources and dates, set audience, format and length, separate required from optional, require approval before anything is sent or changed, and stop drift early. Refine after the first output.

Turn source material into finished files

From the attached reports, build an executive brief and six-slide deck, tying every number to its source.

Research a decision

Compare three support platforms for 50 people and write a recommendation memo with links.

Coordinate a launch

Build a launch plan with owners, risks, drafts and a checklist, flagging missing decisions first.

For recurring jobs, perfect the prompt in a chat, then schedule a task from Scheduled. A scheduled task can continue the same chat or start a fresh one on each run.

Prompting Code

Name the behavior, point to code or repro steps, state constraints and say how to verify. For multi-step work turn on Plan mode (/plan-mode) before editing, then use /goal to keep the agent on a standing objective (slash commands). Code mode is available where it has been enabled for your account.

How to read these examples

Each workflow gives the best surface, the steps, what to attach, and a verification step.

Mention files and folders with @ to bring them in. On desktop, local commands follow your permission preset; the OS sandbox exists on macOS only, so on Windows and Linux approvals are the safeguard (sandboxing).

Explain a codebase

Good for onboarding. Attach the relevant files with @, or run /explain with a file, symbol or topic, or /recap for the repository's structure. Ask for each module's responsibility and flow, and verify with a numbered flow plus the files involved.

Explain how a request flows through the selected code and note gotchas.

Fix a bug

Give repro steps, suspect files and constraints, which beat a vague description. Ask the agent to reproduce first, patch, rerun the repro, and report lint and test results.

Save on /settings doesn't persist; reproduce it, make a minimal fix and add a regression test.

Write a test

Name the function and file and ask for a test that follows local conventions, covering the happy path and edge cases.

Prototype from a screenshot

Attach the image, then add what it cannot show: framework, routing, hover and validation behavior. Ask the agent to start the dev server and give the route, then open it in the built-in Browser tab on desktop.

Build a dashboard matching this image with React, Vite and Tailwind, plus a README.

Iterate on UI with live updates

Run the dev server, ask for a few styling options, pick one and iterate in small prompts. In the desktop Browser tab, Annotate lets you drop numbered comments on the page and send them back as a change request. Commit what you like, revert the rest, and tell the agent about manual edits.

Delegate refactor to the cloud

Plan locally first: commit or stash, then ask for a refactor plan in Plan mode with goals, constraints and milestones. For the long implementation, set up an environment under Settings > Coding > Code Cloud, switch the environment pill to Cloud (or run /cloud on desktop) and send the next prompt, then review the diff. Internet access in cloud runs is limited by the environment's setting (details).

Do a local code review

Run /code-review on desktop to review unstaged changes or compare against a branch, optionally focused on edge cases or security, fix issues and rerun.

Review a GitHub pull request

Open a pull request in the Code Review page on desktop and press Review with ZeroTwo, or run /pr-comments with a PR number or URL to summarize its comments. Reviews happen when you ask; there is no automatic review of every pull request.

Update documentation

@ mention the docs, state scope and validation such as checking links, then review the draft and the rendered page.