Claude + Diode Zener: Faster, Better PCB Reference Designs

Claude + Diode Zener: Faster, Better PCB Reference Designs

Claude

12 déc. 2025

Two people are focused on electronic circuit design in a modern lab, with computer screens displaying schematics and code, complementing a green printed circuit board on the desk, suitable for Claude PCB Design enthusiasts.
Two people are focused on electronic circuit design in a modern lab, with computer screens displaying schematics and code, complementing a green printed circuit board on the desk, suitable for Claude PCB Design enthusiasts.

Why this partnership matters

Designing reliable PCB reference designs from chip datasheets is painstaking: engineers read hundreds of pages, interpret figures, and wire supporting components correctly. By collaborating with Diode Computers, Anthropic focused Claude on this exact agentic task—reading chip documentation and outputting a complete, configurable Zener schematic.

What’s Zener—and why use it?

Zener is Diode’s domain-specific language (built on Starlark) for describing PCB schematics as code. Diode’s open tooling—including the pcb CLI—compiles Zener to EDA tools like KiCad, bringing software-style linting, versioning, and automation to hardware design.

What’s new: measurable gains with Sonnet 4.5

Anthropic and Diode scoped a realistic, tool-use workflow: Claude reads/writes files, runs the Zener compiler, and consults the language docs—then produces a reference design that’s graded with a testbench (e.g., “≥ 22 µF between power and ground” rather than brittle, component-exact checks). In blind, head-to-head evaluations across Claude models, Sonnet 4.5’s outputs were preferred 8/10 times by Diode’s engineers. Detailed splits: 60% vs 40% vs Opus 4 and 82% vs 18% vs Sonnet 4.

Key benefits (for teams adopting the approach)

  • Fewer datasheet misses: Better capture of small configuration nuances and schematic semantics.

  • Code-first schematics: Zener enables diffs, reviews, CI checks, and templating—then exports to familiar EDA.

  • Agentic workflow readiness: The setup mirrors production agent patterns (tool calling, file ops, graded outcomes).

How it works (at a glance)

  1. Provide Claude with the chip datasheet and a Zener project skeleton.

  2. Allow controlled tool use: Zener docs, pcb compiler, read/write, limited shell.

  3. Ask Claude to generate a full, configurable reference design in Zener.

  4. Grade with a testbench that encodes outcome-level requirements (capacitance, modes).

  5. Export to KiCad for human review, DRC, and BOM checks.

Practical steps you can run this week

  • Set up Zener + pcb: Follow Diode’s quickstart and VS Code extension; create a sample project.

  • Create a grading harness: Encode higher-level requirements (e.g., allowable ranges, placements) so the model gets useful signals.

  • Start with a narrow chip family: Provide 1–2 representative datasheets and a minimal parts library to reduce ambiguity.

  • Run a small H2L loop (human-to-loop): Review Claude’s output, correct misinterpretations, and feed examples back as reference modules.

  • Export and verify in KiCad: Perform ERC/DRC, generate a BOM, and document deltas from the datasheet’s application circuits.

What to watch out for

  • Underspecified datasheets: Some requirements aren’t explicit; the graded testbench approach helps avoid over-fitting to brittle checks.

  • Language semantics: Early failures included misunderstanding Zener conventions—keep a short “style guide” with common patterns for your team.

  • Human sign-off: Treat Claude’s output as a draft; always run engineering review and toolchain verification before fabrication.

Why this is credible

Diode has been building a code-first PCB design stack and recently raised funding to accelerate AI-assisted board design, positioning it as a serious player in EDA-adjacent tooling.

FAQs

What improvements has Claude made in PCB design?
With the Zener workflow and a graded testbench, Claude better captures datasheet nuances and Zener semantics; Sonnet 4.5 designs were preferred 8/10 times versus earlier Claude models. website.claude.com

Who partnered with Anthropic for this enhancement?
Diode Computers, creators of the Zener language and the pcb toolchain that compiles to KiCad. website.claude.com+1

What measurable gains were achieved?
In blind evaluations by Diode engineers: 60% vs 40% over Opus 4 and 82% vs 18% over Sonnet 4; overall, Sonnet 4.5 was preferred 8/10 times. website.claude.com

Can teams try this today?
Yes—install Zener/pcb, set up a controlled agent environment (file I/O, compiler access), and start with a single chip family plus a grading harness. docs.pcb.new+1

Why this partnership matters

Designing reliable PCB reference designs from chip datasheets is painstaking: engineers read hundreds of pages, interpret figures, and wire supporting components correctly. By collaborating with Diode Computers, Anthropic focused Claude on this exact agentic task—reading chip documentation and outputting a complete, configurable Zener schematic.

What’s Zener—and why use it?

Zener is Diode’s domain-specific language (built on Starlark) for describing PCB schematics as code. Diode’s open tooling—including the pcb CLI—compiles Zener to EDA tools like KiCad, bringing software-style linting, versioning, and automation to hardware design.

What’s new: measurable gains with Sonnet 4.5

Anthropic and Diode scoped a realistic, tool-use workflow: Claude reads/writes files, runs the Zener compiler, and consults the language docs—then produces a reference design that’s graded with a testbench (e.g., “≥ 22 µF between power and ground” rather than brittle, component-exact checks). In blind, head-to-head evaluations across Claude models, Sonnet 4.5’s outputs were preferred 8/10 times by Diode’s engineers. Detailed splits: 60% vs 40% vs Opus 4 and 82% vs 18% vs Sonnet 4.

Key benefits (for teams adopting the approach)

  • Fewer datasheet misses: Better capture of small configuration nuances and schematic semantics.

  • Code-first schematics: Zener enables diffs, reviews, CI checks, and templating—then exports to familiar EDA.

  • Agentic workflow readiness: The setup mirrors production agent patterns (tool calling, file ops, graded outcomes).

How it works (at a glance)

  1. Provide Claude with the chip datasheet and a Zener project skeleton.

  2. Allow controlled tool use: Zener docs, pcb compiler, read/write, limited shell.

  3. Ask Claude to generate a full, configurable reference design in Zener.

  4. Grade with a testbench that encodes outcome-level requirements (capacitance, modes).

  5. Export to KiCad for human review, DRC, and BOM checks.

Practical steps you can run this week

  • Set up Zener + pcb: Follow Diode’s quickstart and VS Code extension; create a sample project.

  • Create a grading harness: Encode higher-level requirements (e.g., allowable ranges, placements) so the model gets useful signals.

  • Start with a narrow chip family: Provide 1–2 representative datasheets and a minimal parts library to reduce ambiguity.

  • Run a small H2L loop (human-to-loop): Review Claude’s output, correct misinterpretations, and feed examples back as reference modules.

  • Export and verify in KiCad: Perform ERC/DRC, generate a BOM, and document deltas from the datasheet’s application circuits.

What to watch out for

  • Underspecified datasheets: Some requirements aren’t explicit; the graded testbench approach helps avoid over-fitting to brittle checks.

  • Language semantics: Early failures included misunderstanding Zener conventions—keep a short “style guide” with common patterns for your team.

  • Human sign-off: Treat Claude’s output as a draft; always run engineering review and toolchain verification before fabrication.

Why this is credible

Diode has been building a code-first PCB design stack and recently raised funding to accelerate AI-assisted board design, positioning it as a serious player in EDA-adjacent tooling.

FAQs

What improvements has Claude made in PCB design?
With the Zener workflow and a graded testbench, Claude better captures datasheet nuances and Zener semantics; Sonnet 4.5 designs were preferred 8/10 times versus earlier Claude models. website.claude.com

Who partnered with Anthropic for this enhancement?
Diode Computers, creators of the Zener language and the pcb toolchain that compiles to KiCad. website.claude.com+1

What measurable gains were achieved?
In blind evaluations by Diode engineers: 60% vs 40% over Opus 4 and 82% vs 18% over Sonnet 4; overall, Sonnet 4.5 was preferred 8/10 times. website.claude.com

Can teams try this today?
Yes—install Zener/pcb, set up a controlled agent environment (file I/O, compiler access), and start with a single chip family plus a grading harness. docs.pcb.new+1

Get practical advice delivered to your inbox

By subscribing you consent to Generation Digital storing and processing your details in line with our privacy policy. You can read the full policy at gend.co/privacy.

Prêt à obtenir le soutien dont votre organisation a besoin pour utiliser l'IA avec succès?

Miro Solutions Partner
Asana Platinum Solutions Partner
Notion Platinum Solutions Partner
Glean Certified Partner

Prêt à obtenir le soutien dont votre organisation a besoin pour utiliser l'IA avec succès ?

Miro Solutions Partner
Asana Platinum Solutions Partner
Notion Platinum Solutions Partner
Glean Certified Partner

Génération
Numérique

Bureau au Royaume-Uni
33 rue Queen,
Londres
EC4R 1AP
Royaume-Uni

Bureau au Canada
1 University Ave,
Toronto,
ON M5J 1T1,
Canada

Bureau NAMER
77 Sands St,
Brooklyn,
NY 11201,
États-Unis

Bureau EMEA
Rue Charlemont, Saint Kevin's, Dublin,
D02 VN88,
Irlande

Bureau du Moyen-Orient
6994 Alsharq 3890,
An Narjis,
Riyad 13343,
Arabie Saoudite

UK Fast Growth Index UBS Logo
Financial Times FT 1000 Logo
Febe Growth 100 Logo

Numéro d'entreprise : 256 9431 77 | Droits d'auteur 2026 | Conditions générales | Politique de confidentialité

Génération
Numérique

Bureau au Royaume-Uni
33 rue Queen,
Londres
EC4R 1AP
Royaume-Uni

Bureau au Canada
1 University Ave,
Toronto,
ON M5J 1T1,
Canada

Bureau NAMER
77 Sands St,
Brooklyn,
NY 11201,
États-Unis

Bureau EMEA
Rue Charlemont, Saint Kevin's, Dublin,
D02 VN88,
Irlande

Bureau du Moyen-Orient
6994 Alsharq 3890,
An Narjis,
Riyad 13343,
Arabie Saoudite

UK Fast Growth Index UBS Logo
Financial Times FT 1000 Logo
Febe Growth 100 Logo


Numéro d'entreprise : 256 9431 77
Conditions générales
Politique de confidentialité
Droit d'auteur 2026