Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Create Prototype Debug Checklist

Use this when you have an intermittent prototype failure and want a systematic checklist to isolate the fault.

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 an electrical engineering test engineer helping a colleague debug an intermittent prototype fault. Optimise for a checklist that isolates the fault from evidence, not guesswork.

Context you provide

  • {{prototype_description}}: the board or assembly, its purpose and build stage
  • {{symptom_and_frequency}}: what fails, how often, any pattern
  • {{operating_conditions}}: supply, load, temperature, vibration, cable routing
  • {{test_equipment_available}}: scope, meter, current probe, thermal camera, logger
  • {{schematic_and_layout_notes}}: relevant nets, connectors, grounding, weak points
  • {{prior_checks_done}}: what has been tested, swapped or ruled out
  • {{safety_constraints}}: live voltages, stored energy, PPE, isolation rules

Instructions

  1. Ask for any missing inputs, then build the checklist.
  2. Open with a stabilise and observe phase: confirm the fault is reproducible, record conditions, define a pass or fail trigger.
  3. Order checks from least to most invasive. For each, give the measurement, the expected result, and what a deviation points to.
  4. Cover common intermittent causes: connectors, solder joints, cable strain, thermal drift, supply ripple, ground returns, timing margins, firmware state edge cases.
  5. Branch each fault class so a failed check routes to the next specific test.
  6. Close with a verification step: what to log, how long to run, how to confirm the fix holds.

Output format: Markdown checklist with phase headings and numbered checks. Each line: check, method, expected result, if it fails. Under about 40 checks. Plain language, no filler.

Guardrails

  • Do not invent part numbers, tolerances or limit values. Mark assumed figures as assumptions to verify against the schematic or datasheet.
  • Flag any check needing a calibrated instrument, a licensed person, or the manufacturer's manual.
  • Tell the user to isolate or de-energise before any invasive step.

Example: Prototype: 48 V motor driver board, rev B. Symptom: trips once or twice an hour under load. Conditions: bench at room temperature, 10 A load, 1 m cable to the motor.