Be Specific
A useful prompt says what you need, where the work belongs, what may change, and how you will review it. More words are not necessarily better; concrete constraints are.
Start with this pattern:
Task: [explain, plan, or make this change]
Target: [open sheet/board, references, and nets]
Conditions: [actual input, supply, output load, and limits]
Preserve: [parts, connections, drawings, or fixed placements]
Exclude: [work you are not requesting]
Review: [saved result, relevant checks, and unresolved gaps]
Select Ask, Agent, or Plan in the composer. Saying “do not edit” is useful scope, but it is not a reason to leave an editing mode selected for a read-only task.
Provide Context
Include the conditions that materially change the design:
- Actual supply range, signal amplitude, frequency range, and load.
- Exact orderable part number and package, or a clear request to compare options.
- Assembly method, board dimensions, connector access, and mounting constraints.
- Existing parts or routes that must remain.
- Required checks and performance criteria.
Call unknown conditions unknown. Do not let a convenient assumed supply or load become a requirement.
An MCU module is not interchangeable with its bare chip. If you want a module, name the module or ask for clarification before acquisition.
Ask Questions
Use Ask to understand the existing design before changing it:
Explain the RC filter on this sheet. R1 is 1 kΩ and C1 is 100 nF.
Assume an external 0–1 V signal source with negligible resistance
and an external 1 MΩ load. Calculate the nominal unloaded cutoff
and explain the effect of the load. Do not edit files.
The nominal unloaded result is approximately 1591.55 Hz. The known source and load matter; the response is not established by values alone.
Request Modifications
Choose Agent for a bounded edit:
Change only R1 to 1 kΩ on the open sheet.
Keep its footprint, placement, and pin-to-net connections.
Do not update or route the PCB. Report the saved value and findings.
For presentation, distinguish an amendment from a full redraw:
Improve readability on the selected sheet using more wires.
Preserve all components and electrical connections.
Amend the existing drawing; do not replace the layout of other sheets.
See Schematic drawing.
Iterate
Break larger work into reviewable stages:
- Resolve circuit requirements and part choices.
- Create or amend the schematic.
- Review connectivity, footprints, and ERC.
- Update and prepare the board.
- Place, route, and review DRC.
- Inspect exported files before fabrication.
Use Plan when you want the proposed steps approved first. Avoid vague instructions such as “fix everything” that can expand beyond the intended change.
Attach Context
Attach a supported PDF or image and name the relevant page, figure, or region:
Using the attached datasheet, review the pinout for the exact
package I selected. Cite the relevant figure and identify any
symbol-to-footprint mapping I still need to check.
Do not install or place a part yet.
The shared picker accepts images and PDFs, not direct text/CSV/Markdown uploads. Put reusable BOMs or text specifications in the appropriate Artifacts workflow, or paste a short relevant excerpt. See Attachments for limits and model-dependent image support.
Uploading a file provides context; it does not authorize reproducing a circuit, installing parts, or editing the design.
Check Component Availability
Ask for the exact part, required quantity, and preferred suppliers:
Check these exact part numbers for 50 units from my preferred
suppliers. Report package, stock, price, and source date where
available. Mark failed lookups as unknown.
Propose alternatives separately; do not substitute them in CAD.
Availability and pricing can change. A reported match is not proof of pin compatibility or an orderable package; verify before buying.
Placement and Simulation Requests
State whether you want placement, routing, or both. Trace's advanced engines operate globally; asking about one net or one footprint does not authorize a whole-board run. See Placement and routing.
For simulation, provide real stimulus, supply, load, and evaluation criteria. Ask for actual saved observations and gaps—not an unsupported “design verified” statement. See Simulation.
Use Your Preferred Language
You can write requirements in your preferred language. Keep exact part numbers, reference designators, units, and net names unambiguous, and review the assistant's interpretation.
When a Request Fails
A failed or uncertain response is not an invitation to resend an edit unchanged. Inspect the chat and current design and use the matching recovery control. See Chat.
Available tools and models depend on your build and host; better wording cannot enable an unsupported workflow. Check Availability.