Native schematic generation

Generate a real KiCad schematic from design intent

Go from hardware requirements to an editable .kicad_sch file, with structured design state, component evidence, and validation reports alongside it.

A generated schematic is only useful if it remains a real engineering artifact. Circuit Weaver produces native KiCad schematic files instead of an image, PDF, or isolated diagram. The generated project can be opened, edited, reviewed, and carried into PCB layout with KiCad.

How to generate a KiCad schematic

  1. Describe the design. Capture input voltage, regulated rails, interfaces, current requirements, critical parts, connectors, and environmental constraints.
  2. Resolve the parts. Bind each component to supported symbol, footprint, package, and pin information. Weak or missing evidence should remain visible.
  3. Compile to DesignIR. Convert the requirements into the typed intermediate representation shared by the design tools.
  4. Validate before generation. Check structure, power domains, interface rules, thermal constraints, and placement blockers.
  5. Write and verify the schematic. Generate the exact KiCad file, review it in KiCad, and keep the reports with the project.

Quick start

pip install circuit-weaver
circuit-weaver design-wizard

The wizard is the simplest offline entry point. You can also install skills for Claude Code, Codex, and OpenCode, call the HTTP API, or import the Python package into another workflow.

What the generated project contains

The schematic is part of a broader artifact set designed for review and continuation:

Native output matters. A picture of a schematic cannot prove connectivity or carry exact symbol and footprint data. Circuit Weaver writes a file KiCad understands, then verifies the generated artifact rather than treating rendering success as electrical correctness.

What to include in your requirements

Power

State the input source, acceptable voltage range, polarity or surge protection, each rail voltage, expected current, and any isolation requirement.

Digital and analog interfaces

Name buses and protocols, voltage levels, speed where relevant, connector destinations, termination, pull-ups, ESD needs, and sensitive analog signals.

Mechanical and sourcing constraints

Include board size, connector placement constraints, preferred packages, assembly process, distributor or fabrication preferences, and parts that must or must not be used.

Where human review still matters

Generated output is a starting point for engineering review, not a fabrication guarantee. Review datasheet limits, safety and compliance requirements, RF and high-speed layout, unusual analog behavior, thermal design, creepage and clearance, component lifecycle, routing, and the final manufacturing package.

Why generate through an intermediate model?

DesignIR separates the electrical design from the interface used to create it. A CLI wizard, agent conversation, HTTP request, or Python script can all build the same model. Validators and generators read that shared state, which reduces drift and makes it possible to resume or audit the project later.