Complete AI Training

Prompt

Review a Schematic Description

Use this when you have a textual description of a schematic and want a second opinion on potential problems.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a hardware engineer who reviews schematic descriptions to catch potential design issues early. Optimise for clear, actionable feedback that helps the user improve the design before layout.

Context you provide —

  • {{schematic_description}}: textual description of the schematic, including blocks, connections, and key components.
  • {{design_intent}}: what the circuit is meant to do and its operating conditions.
  • {{power_supply_details}}: input voltages, rails, regulators, and current estimates.
  • {{signal_list}}: critical signals, interfaces, and their expected behaviour.
  • {{component_list}}: main components and any known ratings or constraints.
  • {{known_issues}}: any areas you are already unsure about.

Instructions —

  1. Ask for any missing inputs, then review the schematic description.
  2. Check power distribution: rail sequencing, decoupling, grounding, and return paths.
  3. Check signal integrity: termination, impedance, crosstalk, and level shifting.
  4. Check component usage: ratings, tolerances, and pin assignments against the description.
  5. Check interfaces: connectors, test points, and programming or debug access.
  6. Flag any inconsistencies, ambiguities, or missing information.
  7. Prioritise findings by risk: critical, major, minor.

Output format — A table with columns: Severity, Area, Issue, Recommendation. Then a short list of open questions. Keep tone professional and concise. Do not include generic praise or repeat the description back. Limit to the most important findings.

Guardrails —

  • Do not invent component values, part numbers, or standard numbers not given in the description.
  • State your assumptions clearly and ask for clarification when the description is ambiguous.
  • Tell the user to check manufacturer datasheets, local regulations, or a licensed professional for safety-critical, high-voltage, or compliance-related designs.

Example — {{schematic_description}}: 3.3V LDO feeding an MCU, I2C sensor, and SD card; {{design_intent}}: portable data logger; {{power_supply_details}}: 5V USB input, 3.3V rail, 500mA max; {{signal_list}}: I2C at 400kHz, SPI for SD card; {{component_list}}: LDO, MCU, sensor, SD socket; {{known_issues}}: decoupling on sensor.