Once /mcp shows both probe and trace as connected, you can ask Claude questions in plain language. It picks the right tools itself; you do not need to name tools or know how the data is organised.
E-Sharp's demonstration boards contain real defects. The point of these questions is to see whether they get found, so start broad and then push on whatever comes back. The same questions work on your own designs.
Start here
Review this board and give me your top concerns, worst first.
Is there anything here that would stop this board being manufactured?
Do the BOM and the schematic agree on every part?
Is there anything that could damage a component at power-up?
Then press on the answers
Show me the evidence for that finding. How do you know?
What have you not been able to check, and why?
Which of these would you fix before the next spin, and which can wait?
Interconnect (two or more boards)
Check the connections between these two boards. Do the pin assignments and signals match across the connector?
Are the power rails compatible across the interconnect?
Push back on anything that looks thin, and ask Claude to justify a finding. It can follow its own reasoning further and will tell you when the evidence runs out.