Have Claude Code review your hardware design before you build it
A maker added a MOSFET to switch 48V power to each port under firmware control and asked Claude Code to review the circuit. Its feedback found real problems and he had to add more components.
Source
@tlberglund on X · 2026-10-21
Written in our own words. Credit to the original author. Link checked 2026-10-22.
What they did
A maker added a MOSFET to switch 48V power to each port under firmware control and asked Claude Code to review the circuit. Its feedback found real problems and he had to add more components.
Result (as claimed)
Caught design flaws before the board was made.
Tools they used
Cost: Claude Code: from $17/mo.
Set it up
Gather your sources
Collect the papers, notes, links or files you want to work from in one place.
Load them into the tool
Open Claude Code, KiCad and add your sources. Keep the original files so you can check claims later.
Ask focused questions
Ask for summaries, comparisons or connections with citations to the source passages.
Verify and save
Spot check claims against the sources, then save the output as notes you can reuse.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Have Claude Code review your hardware design before you build it What the original author did: A maker added a MOSFET to switch 48V power to each port under firmware control and asked Claude Code to review the circuit. Its feedback found real problems and he had to add more components. Reported result (as claimed by the author): Caught design flaws before the board was made. Source: https://x.com/tlberglund/status/2112920382948679974 Tools they used: Claude Code, KiCad Category: Research & learning Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Have Claude Code review your hardware design before you build it What the original author did: A maker added a MOSFET to switch 48V power to each port under firmware control and asked Claude Code to review the circuit. Its feedback found real problems and he had to add more components. Reported result (as claimed by the author): Caught design flaws before the board was made. Source: https://x.com/tlberglund/status/2112920382948679974 Tools they used: Claude Code, KiCad Category: Research & learning Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Have Claude Code review your hardware design before you build it What the original author did: A maker added a MOSFET to switch 48V power to each port under firmware control and asked Claude Code to review the circuit. Its feedback found real problems and he had to add more components. Reported result (as claimed by the author): Caught design flaws before the board was made. Source: https://x.com/tlberglund/status/2112920382948679974 Tools they used: Claude Code, KiCad Category: Research & learning Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to build hardware projects with AI agents · How to vibe code an app with Claude Code · How to design a PCB and electronics with AI · How to automate work with n8n and AI
Related use cases
Let Claude Code run browser research in its own space while you keep working
Instead of stopping work to watch Claude Code click around his own browser, a creator gave the agent its own logged-in space in the browser with ego (lite), so it runs a research task while he keeps writing.
Run an autonomous science loop in Claude Code for three days with Codex checking the evidence
A creator ran an autonomous science workflow in Claude Code for three days straight, with Codex driving it and checking the evidence each round. The loop is open source on GitHub.
Measure how much time Claude Code actually saves from your logs
After five weeks of using Claude Code for most work, the author went through the logs: 159 sessions, 754 requests and about 70 hours of Claude working, compared against a by-hand estimate.
Design a circuit board from a chat with the HeyPCB MCP server
HeyPCB is an MCP server that lets a coding agent design circuits, route the PCB, run checks, export a real KiCad project and generate an enclosure. It plugs into Claude Code, Codex, Cursor, ChatGPT and other MCP clients, so you describe the board you want in chat.