Docs

Using Prompts

Tips for writing effective prompts to get the best results from Trace.

Be Specific

Include relevant details like voltage levels, current requirements, and component preferences.

Less EffectiveMore Effective
"Add a power supply""Add a 5V to 3.3V linear regulator with 500mA capacity"
"Connect the sensor""Connect the BME280 sensor via I2C to the ESP32's GPIO21 (SDA) and GPIO22 (SCL)"

Provide Context

Explain the purpose of your circuit. This helps Trace make appropriate design decisions.

This is a battery-powered sensor node that needs to run for 6 months on a CR2032. Power efficiency is critical.

Ask Questions

Trace can explain concepts and help you understand design tradeoffs.

  • "Why did you choose that capacitor value?"
  • "What's the difference between these two regulators?"
  • "How can I reduce noise on this signal?"

Iterate

Start with a high-level description and refine. You don't need to specify everything upfront.

  1. "I need an ESP32-based IoT sensor board"
  2. "Add a temperature and humidity sensor"
  3. "Include a battery charging circuit for a LiPo cell"
  4. "Add an LED to indicate charging status"

Request Modifications

After Trace generates something, ask for specific changes:

  • "Change R1 to 4.7k"
  • "Move the decoupling capacitor closer to the IC"
  • "Use a different footprint for the connector"

Example Prompts

Power Supply

Design a 12V to 5V buck converter using the MP1584. Target 2A output with good efficiency. Include input protection and output filtering.

Microcontroller Circuit

Set up an STM32F103C8T6 with: - 8MHz crystal oscillator - SWD debug header - USB device connector - 3.3V LDO from 5V USB power - Reset button and power LED

Sensor Interface

Add an analog front-end for a load cell: - INA125 instrumentation amplifier - 5V excitation for the load cell - Low-pass filter with 10Hz cutoff - Connect to ADC input on pin PA0