Prompts, context, and steering
A useful prompt tells Syntheo what success looks like and gives it enough evidence to work confidently.
Use this prompt shape#
Outcome:
What should be true when the task is finished?
Evidence:
What error, screenshot, example, or reproduction shows the current problem?
Constraints:
What must not change? Are any files, behaviors, or actions off limits?
Done when:
What check or visible behavior proves the task is complete?Example:
Outcome:
Keep the selected billing plan after the page is refreshed.
Evidence:
The selection disappears after refresh but remains when navigating normally.
Constraints:
Keep the guest flow unchanged and do not add a dependency.
Done when:
The selected plan survives refresh and the focused billing checks pass.Add only useful context#
Mention files and folders#
Type @ in the composer to select a file, folder, Skill, or connected tool.
Mention the smallest useful scope. One relevant file is usually better than an entire project folder.
Add images#
Attach an image for visual bugs, target designs, diagrams, or errors that cannot be copied. If you attach more than one, say which image shows the current state and which shows the expected state.
Paste errors carefully#
Include the command or action that caused the problem and the first useful error. Remove secrets, personal data, private URLs, and unrelated output.
Let Syntheo inspect before prescribing a solution#
Describe the outcome and important boundaries. Avoid forcing a specific implementation unless that implementation is a real requirement.
Better:
Fix the duplicate notification after reconnect. Preserve normal completion and
add a focused regression check.Less useful:
Rewrite the notification store with three new hooks.Steer an active task#
You can send another message while Syntheo is working. Send only what changed:
New evidence: this happens only when offline mode is enabled. Keep the public
behavior unchanged and inspect that path first.Good steering adds evidence, corrects an assumption, or changes a priority. If the whole goal or workspace is wrong, stop the task and start a clean thread.
Answer questions and approvals#
When Syntheo asks a question, answer the decision and the reason behind it.
When it requests a tool approval:
- Check the tool.
- Read the full command, path, or URL.
- Confirm it belongs to this task and workspace.
- Use Allow Once unless broader approval is clearly needed.
Keep long threads useful#
Start a new thread when the objective changes or the previous task is complete.
Use context compression when the objective is still the same but the thread has become long. After compression, restate the current outcome, accepted decisions, and remaining check in a short message.
Next#
Set a reliable project boundary in Workspaces and Code Atlas.