Skip to the content
2 layers63 × 70 mmBattery IoT Sensor placement, the printed circuit board in 3D

Battery IoT Sensor placement

mattpainter701/circuit-weaver1

Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

Size
63 × 70 mm
Copper layers
2
Thickness
1.6 mm
Parts
5
Nets
17
Pads
0
Tracks, vias
0, 0
Routed
Not yet
KiCad
KiCad 8 (file 20240108)
Created
27 Mar 2026
Updated
29 Oct 2026

Overview

Battery IoT Sensor placement is an open-source printed circuit board by mattpainter701, from the mattpainter701/circuit-weaver repository on GitHub, published under the MIT licence. It is a 2-layer board of 63 × 70 mm with 5 parts on 17 nets.

It is built around the ESP32-WROOM-32E, MAX17048G+T10 and MCP73831T-2ACI/OT-HXY. Its parts include 4 ICs and 1 connector. It belongs with the power and home automation and IoT boards and the ESP32 boards of this library.

Main components

3

README

README.md

Circuit Weaver

CI PyPI Python 3.10+ KiCad 8+ MIT

Programmatic KiCad schematic generation, strict validation, and manufacturing export
designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.


How It Works

Circuit Weaver full pipeline — from install to KiCad export

Circuit Weaver supports describe the design → validate → generate KiCad artifacts, with additional native placement, routing and review workflows. Start from an agent skill or the CLI and inspect the resulting evidence and blockers before proceeding.

Validated scope

Circuit Weaver is an alpha tool for engineering prototypes. The 0.37.0 workflow corpus covers all 13 shipped samples and three connected mixed-signal boards with 149, 155 and 145 physical parts. Each passes 16 stages, including native routing, DRC, assembled model previews and a real MCP session. These are finite regression fixtures; passing them does not establish arbitrary-circuit electrical correctness or fabrication readiness.

Claude Code, Codex and OpenCode can use the packaged agent skills and CLI. The optional MCP server exposes five focused tools rather than the entire CLI lifecycle. Installer and MCP tests do not constitute a fresh end-to-end test inside every agent client; see agent platform support.

RF research and circuit-generation assistance are available, but controlled-impedance routing, matching networks, antenna performance and RF stability require separate engineering verification. Native DRC and a rendered board are not evidence of RF performance. Review the automation validation guide for prerequisites, evidence and prototype delivery gates.


Capability Contract

This table is generated from the checked-in capability registry. Regenerate it with python scripts/gen_capability_docs.py; do not edit it by hand.

Verification is conservative: a capability only claims the evidence level its public path actually verifies. not applicable means an operational capability makes no design-artifact verification claim; it is not a lower verification level.

CLI capabilityMaturityPublic surfacesVerification contractEvidenceSince
validatebetaCLI: validate; Python: circuit_weaver.dispatcher:validate_design; HTTP: POST /validate; POST /mvp/validate; MCP: validate_design; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
apply-patchbetaCLI: apply-patch; Python: circuit_weaver.dispatcher:apply_design_patch; HTTP: POST /mvp/apply-patchstatic-parse → static-parsecommand-contract, static-parse0.32.1
generateexperimentalCLI: generate; Python: circuit_weaver.dispatcher:generate_artifacts; HTTP: POST /generate; POST /mvp/generate; MCP: generate_artifacts; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse, kicad-load, erc0.32.1
review-reportexperimentalCLI: review-report; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
diffbetaCLI: diff; Python: circuit_weaver.dispatcher:diff_designs; HTTP: POST /mvp/diffstatic-parse → static-parsecommand-contract, static-parse0.32.1
ingest-pcb-feedbackbetaCLI: ingest-pcb-feedback; Python: circuit_weaver.dispatcher:ingest_pcb_feedback; HTTP: POST /mvp/pcb-feedbackstatic-parse → static-parsecommand-contract, static-parse0.32.1
import-placementreview_onlyCLI: import-placement; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
list-templatesbetaCLI: list-templates; HTTP: GET /templatesnot applicable (operational)command-contract0.32.1
scaffoldbetaCLI: scaffold; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
register-icexperimentalCLI: register-icstatic-parse → static-parsecommand-contract, static-parse0.32.1
resolve-symbolexperimentalCLI: resolve-symbolnot applicable (operational)command-contract0.33.0
export-jlcpcbreview_onlyCLI: export-jlcpcb; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
export-gerbersreview_onlyCLI: export-gerbers; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
cost-bomexperimentalCLI: cost-bom; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
import-designexperimentalCLI: import-design; Python: circuit_weaver.design_import:import_design; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
analyze-designexperimentalCLI: analyze-design; Python: circuit_weaver.design_import:analyze_design; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
statusbetaCLI: status; Python: circuit_weaver.project_state:get_project_state_summary; Skill: circuit-weavernot applicable (operational)command-contract0.32.1
resumeexperimentalCLI: resume; Python: circuit_weaver.project_state:resume_project; Skill: circuit-weavernot applicable (operational)command-contract0.32.1
design-wizardexperimentalCLI: design-wizard; Skill: design-wizardstatic-parse → static-parsecommand-contract, static-parse0.32.1
build-pcbexperimentalCLI: build-pcb; Python: circuit_weaver.schematic_pcb:schematic_to_pcb; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, static-parse, kicad-load, external-tool0.35.0
place-pcbexperimentalCLI: place-pcb; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, external-tool, user-supplied0.32.1
plane-pcbreview_onlyCLI: plane-pcb; Python: circuit_weaver.pcb_ground_plane:add_ground_plane; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, kicad-load, external-tool, user-supplied0.35.0
plane-cleanup-pcbreview_onlyCLI: plane-cleanup-pcb; Python: circuit_weaver.pcb_plane_cleanup:cleanup_plane_traces; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, kicad-load, external-tool, user-supplied0.35.0
cleanup-pcbreview_onlyCLI: cleanup-pcb; Python: circuit_weaver.pcb_copper_cleanup:cleanup_copper; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, kicad-load, external-tool, user-supplied0.35.0
refine-pcbreview_onlyCLI: refine-pcb; Python: circuit_weaver.pcb_return_paths:refine_return_paths; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, kicad-load, external-tool, user-supplied0.35.0
preview-pcbreview_onlyCLI: preview-pcb; Python: circuit_weaver.pcb_preview:render_board_preview; Skill: circuit-weaverstatic-parse → kicad-loadcommand-contract, static-parse, kicad-load, external-tool0.35.0
log-statusbetaCLI: log-statusnot applicable (operational)command-contract0.32.1
log-viewbetaCLI: log-viewnot applicable (operational)command-contract0.32.1
autoroutereview_onlyCLI: autoroute; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, external-tool, user-supplied0.32.1
install-skillsexperimentalCLI: install-skillsnot applicable (operational)command-contract0.32.1
schemabetaCLI: schemanot applicable (operational)command-contract0.32.1
harvest-specsexperimentalCLI: harvest-specsstatic-parse → static-parsecommand-contract, external-tool0.32.1
extract-specsexperimentalCLI: extract-specsstatic-parse → static-parsecommand-contract, user-supplied0.32.1
fetch-spiceexperimentalCLI: fetch-spicestatic-parse → static-parsecommand-contract, external-tool0.32.1
cachebetaCLI: cachenot applicable (operational)command-contract0.32.1
cache statsbetaCLI: cache statsnot applicable (operational)command-contract0.32.1
cache clearreview_onlyCLI: cache clearnot applicable (operational)command-contract0.32.1
optimize-placementreview_onlyCLI: optimize-placement; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
placement-viewerreview_onlyCLI: placement-viewer; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
si-constraintsexperimentalCLI: si-constraintsstatic-parse → static-parsecommand-contract, static-parse0.32.1
thermal-analysisexperimentalCLI: thermal-analysisstatic-parse → static-parsecommand-contract, static-parse0.32.1
export-dual-cplreview_onlyCLI: export-dual-cplstatic-parse → static-parsecommand-contract, static-parse0.32.1
panelizeexperimentalCLI: panelizestatic-parse → static-parsecommand-contract, static-parse0.32.1
design-enclosureexperimentalCLI: design-enclosurestatic-parse → static-parsecommand-contract, static-parse0.32.1
check-dfmreview_onlyCLI: check-dfmstatic-parse → static-parsecommand-contract, static-parse0.32.1
generate-docsexperimentalCLI: generate-docsstatic-parse → static-parsecommand-contract, static-parse0.32.1
ercreview_onlyCLI: erckicad-load → erccommand-contract, kicad-load, erc0.32.1
doctorbetaCLI: doctornot applicable (operational)command-contract0.32.1
repairexperimentalCLI: repair; Python: circuit_weaver.repair_service:apply_no_connectstatic-parse → static-parsecommand-contract, static-parse0.35.0
confidencereview_onlyCLI: confidence; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
manufacturing-readinessbetaCLI: manufacturing-readiness; Python: circuit_weaver.manufacturing_readiness:read_manufacturing_readiness; HTTP: POST /manufacturing-readiness; MCP: manufacturing_readiness; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, fabrication-ready0.34.0
simulateexperimentalCLI: simulate; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
discoverbetaCLI: discover; MCP: discover_projects; Skill: circuit-weavernot applicable (operational)command-contract0.32.1
save-researchexperimentalCLI: save-research; Skill: circuit-weaverstatic-parse → static-parsecommand-contract, static-parse0.32.1
log-eventbetaCLI: log-eventnot applicable (operational)command-contract0.32.1

Quick Start

Step 1 — Install

bash
pip install circuit-weaver

Step 2 — Register the skill (one-time, for Claude Code / Codex / OpenCode)

bash
circuit-weaver install-skills            # install for all supported agent platforms
circuit-weaver install-skills --dry-run  # preview without touching disk
circuit-weaver install-skills --force --backup   # resolve conflicts, back up every replaced file

Upgrade safety: each installed skill has a provenance manifest containing hashes for every managed file. A pristine older release upgrades automatically. A file changed or deleted by the user is preserved and reported as a conflict, and the command exits non-zero. Pass --force only after reviewing conflicts; add --backup to preserve every replaced file.

Step 3 — Launch

text
# Claude Code:
/circuit-weaver

# Codex:
$circuit-weaver

# OpenCode: ask it to use circuit-weaver (loaded through its skill tool).

# Or run offline without any agent:
circuit-weaver design-wizard

The skill walks through IC selection, spec validation, schematic generation, and the electrical-PCB handoff.

For a repeatable real-tool demonstration, run python scripts/validate_app_workflow.py --output ./workflow-evidence. The automation validation guide describes native ERC/DRC evidence, optional MCP checks, and the prototype/manufacturing boundary.


Research Traceability

Agentic research runs are expected to persist their output into output/research/. That directory is the source of truth for why an IC was chosen, which citations backed it, and which backend produced the result.

For Codex / Claude / OpenCode workflows, Step 2 IC research should stay in the current agent session. If a premium-research command would delegate to a subagent or fails with a model/tool conflict, use the platform's native web tools instead and persist the backend that actually ran.

bash
# Check which backend and depth are active before research starts
circuit-weaver doctor

# Optional: force backend/depth selection for agent workflows
export CIRCUIT_WEAVER_RESEARCH_BACKEND=standard   # or sonar-pro / auto
export CIRCUIT_WEAVER_RESEARCH_DEPTH=fast         # or normal
# PowerShell: $env:CIRCUIT_WEAVER_RESEARCH_BACKEND="standard"
# PowerShell: $env:CIRCUIT_WEAVER_RESEARCH_DEPTH="fast"

# Persist a completed research result
circuit-weaver save-research --project-dir ./output --file research.json

Each saved run produces {slug}.json, {slug}.md, and summary.md, and the matching design.log entry records the canonical JSON path for later audit.


Branch Maintenance

Use scripts/cleanup_branches.py to audit stale local branches before pruning them. The command is dry-run by default and only targets merged, unprotected branches, so dated work can be reviewed without risking useful code. When run with --delete, deleted branch tips are archived under refs/archive/branches/<name> unless --no-archive is explicitly supplied.

bash
python scripts/cleanup_branches.py                 # audit only
python scripts/cleanup_branches.py --delete        # prune merged stale branches and keep archives
python scripts/cleanup_branches.py --force-unmerged # include unmerged branches only when intentionally forced

What You Get

A successful default generate run produces a complete artifact bundle (--no-placement-review deliberately omits the four placement-review files):

ArtifactFileDescription
KiCad schematic hierarchy{project}.kicad_sch plus functional sub-sheetsReal, loadable hierarchy; explicit block section values remain separate professional sheets and support passives follow their owner
Markdown design report{project}_report.mdValidation results, component summary, and design notes
Placement reviewplacement_result.json, placement_review_context.json, placement.svg, placement_editor.htmlExhaustive, reference-reconciled heuristic proposal with review blockers and official-reference context; never fabrication data
Assembly inventoryassembly_manifest.jsonStable physical-part references, including generated support passives
Evidence ledgerevidence_manifest.jsonStable component, pinout, footprint, parameter, finding, tool, and verification provenance IDs
Canonical spec and IRcanonical_spec.yaml, design_ir.jsonNormalized source of truth and generated design IR
Validation evidencevalidation_report.json, placement_readiness.jsonMachine-readable release/readiness checks
Artifact inventoryartifact_manifest.jsonPortable relative paths, verification state, kinds, and sizes for every generated artifact
Test point map{project}_test_points.csvAuto-detected power, clock, bus, and differential-pair nets
Firmware stubs (when applicable){project}_pinout.csv, .ioc, sdkconfig.defaultsMCU pin map and STM32/ESP32 co-design files

Resume or Analyze an Existing Design

Circuit Weaver keeps restartable state in <project>/.circuit-weaver/project.json. Import is non-destructive: source KiCad, PCB, Gerber, drill, and ZIP files are inventoried and hashed rather than regenerated.

bash
# Import a KiCad project, a single KiCad file, a Gerber directory, or a ZIP
circuit-weaver import-design ./existing_board --analyze

# Inspect durable state or get a deterministic restart plan
circuit-weaver status ./existing_board
circuit-weaver resume ./existing_board

# Re-run every applicable bundled analyzer; unchanged results are cached
circuit-weaver analyze-design ./existing_board

Use --project-dir <dir> when state should live somewhere other than the source directory. Use --force only to intentionally replace a changed import source set, ZIP staging tree, or cached analysis. Netlist-only imports are inventoried, but analysis is reported as unsupported because a netlist alone does not contain schematic or physical-layout evidence.

Bounded no-connect repair

The first experimental imported-design repair is deliberately narrow: it can add one explicit KiCad no-connect marker only when a circuit-weaver-repair-metadata/v1 envelope binds the exact source hash, analyzer component/pin identity, a v2 finding, and its validated evidence manifest. Build that envelope with circuit_weaver.repair_service.build_no_connect_metadata; the matching trusted finding producer is no_connect_finding_from_intent. Both require current, verified user evidence whose exact pin:REF.NUMBER claim says the pin is intentionally unused. Raw analyzer JSON or an unbound boolean is rejected.

The service then independently proves the component UUID/library ID, pin coordinate, and absence of a net, wire, label, junction, bus entry, hierarchical sheet pin, power symbol, or coincident component pin. The plan is reviewable JSON; the apply step will not infer approval from that file.

bash
circuit-weaver repair suggest board.kicad_sch repair-metadata.json \
  --ref U1 --pin 4 \
  --finding-id FND-0123456789ab \
  --evidence-id EV-VALIDATION-0123456789ab \
  --output no-connect-plan.json

# Review the plan and copy its plan_sha256 through the approval channel.
circuit-weaver repair apply no-connect-plan.json repair-metadata.json \
  --approved-plan-hash <approved-plan-sha256> \
  --reviewer <reviewer> \
  --finding-id FND-0123456789ab \
  --evidence-id EV-VALIDATION-0123456789ab

circuit-weaver repair verify board.kicad_sch no-connect-plan.json

The public capability guarantee is static parsing. Run KiCad ERC after review; unsupported topology, geometry, part replacement, and pin-remapping repairs fail closed instead of being improvised. Apply holds cross-process source and audit locks, keeps an exact hard-linked preimage through publication, and uses prepared/committed append-only audit events so an interrupted successful publication can be recovered on retry. Lock hardlinks and reparse aliases are rejected before mutation; the default audit sidecar cannot escape through a directory junction. On Windows, atomic replacement preserves and verifies the target owner, group, and DACL access semantics. Applications that write schematics without honoring Circuit Weaver's lock remain outside the cooperative locking contract; snapshot, identity, and post-image checks still detect ordinary write races and preserve observed user bytes rather than rolling over them.


PCB Placement Workflow

Circuit Weaver generates a review-only placement proposal, then KiCad creates the electrical PCB. The SVG/HTML/JSON proposal is never a PCB, CPL, or other fabrication artifact.

1 — Generate initial placement

generate returns the path to artifact_manifest.json. Resolve that manifest's portable root_schematic and artifact paths relative to the manifest directory instead of guessing filenames. Check verification_status before claiming KiCad verification. Placement review is enabled by default:

bash
circuit-weaver generate design.yaml -o ./output
# → output/{project}.kicad_sch
# → output/placement_result.json
# → output/placement_review_context.json
# → output/placement.svg
# → output/placement_editor.html
# → output/{project}_report.md

placement_result.json must contain the exact assembly_manifest.json reference inventory. It remains fabrication_ready: false by design. Review its overlap, boundary, support-part, geometry, sourcing, and constraint blockers. placement_review_context.json records constraints, targeted research prompts, and official component/reference-layout links available to the agent; manufacturer documentation remains authoritative.

2 — Optimize with simulated annealing

bash
# Basic optimization (5 000 iterations, reproducible with seed)
circuit-weaver optimize-placement design.yaml --iterations 5000 --seed 42 \
    -o output/placement.json

# Thermal-aware strategy (minimizes hotspot proximity)
circuit-weaver optimize-placement design.yaml --strategy thermal --iterations 10000 \
    -o output/placement.json

# Read component thermal/SI specs from YAML files
circuit-weaver optimize-placement design.yaml --specs-dir ./specs/

The optimizer minimizes: overlap, boundary violations, thermal clustering, and DFM zone penalties via simulated annealing. Returns a placement JSON with x/y/rotation/layer per component.

3 — Review in the interactive viewer

Open the generated output/placement_editor.html, or generate a standalone viewer for a different optimizer configuration:

bash
circuit-weaver placement-viewer design.yaml -o output/viewer.html

Opens a self-contained HTML file with:

  • Click-to-highlight nets
  • Component hover tooltips (value, footprint, MPN)
  • Thermal heatmap overlay (blue → red gradient by power dissipation)
  • CSV export button for placement data

4 — Create the electrical PCB in KiCad

Open artifact_manifest.json, then open its root_schematic, assign and verify footprints, and run Update PCB from Schematic. Save that electrically annotated board under a separate name. Only this board has the pads and nets required by routing, DFM, and Gerber export.

Apply reviewed SVG coordinates only to that real electrical PCB. The default import is strict: every PCB reference must appear exactly once in the SVG, and unexpected or missing references block the write.

bash
circuit-weaver import-placement output/placement.svg board.kicad_pcb \
    -o board_placed.kicad_pcb --dry-run
circuit-weaver import-placement output/placement.svg board.kicad_pcb \
    -o board_placed.kicad_pcb

# Intentional subset update only; unknown SVG references still fail.
circuit-weaver import-placement subset.svg board.kicad_pcb \
    -o board_placed.kicad_pcb --allow-partial

5 — Place and route the real board

After forward annotation, add a rectangular Edge.Cuts outline and lock connectors that must remain fixed. Place the actual library footprints, route, import the tracks, and check the final PCB:

bash
circuit-weaver place-pcb board.kicad_pcb -o board_placed.kicad_pcb --seed 7
circuit-weaver autoroute board_placed.kicad_pcb --attempts 3 \
    --routed-board board_routed.kicad_pcb
circuit-weaver preview-pcb board_routed.kicad_pcb -o board-preview.svg

The preview draws actual board layers and footprint body geometry. Use --side back for a mirrored underside or --render-3d for a native assembly-model PNG on KiCad 9+ with the declared model files installed. The workflow demo includes named preview controls and full-size views.

KiCad's native Python is discovered separately from your application Python. Freerouting and a compatible Java runtime are required for routing. The input board must have real pads and nets; padless previews are rejected. Placement currently requires an unrouted rectangular board without zones. It preserves locked footprints and board sides, uses real courtyards and rotated pad locations, and checks physical DRC. Routing publishes the final board only after KiCad DRC passes, preserving project rules. See setup and limits.

6 — DFM check and panelization

bash
# Check clearances, pad sizes, and DFM rules
circuit-weaver check-dfm electrical_board.kicad_pcb --profile jlcpcb

# Get panel layout suggestions for small boards
circuit-weaver panelize --board-width 50 --board-height 40 --qty 100

# Export dual-sided CPL (top + bottom)
circuit-weaver export-dual-cpl design.yaml --pcb electrical_board.kicad_pcb -o ./jlcpcb

# Export a reconciled JLCPCB delivery and inspect its commit manifest
circuit-weaver export-jlcpcb design.yaml --pcb electrical_board.kicad_pcb -o ./jlcpcb
# → bom_jlcpcb.csv, cpl_jlcpcb.csv, README_jlcpcb.txt, delivery_manifest.json

Without --pcb, export-jlcpcb is intentionally BOM-only. A supplied board must match every assembly reference and footprint before CPL publication. Treat delivery_manifest.json as the delivery status/commit marker.


CLI Reference

bash
# ── Design lifecycle ──────────────────────────────────────────────────────────
circuit-weaver validate design.yaml               # Validate spec (no files written)
circuit-weaver generate design.yaml -o ./output  # Full artifact bundle
circuit-weaver erc output/{project}.kicad_sch      # Use root_schematic from artifact_manifest.json
circuit-weaver diff old.yaml new.yaml             # Semantic diff + optional SVG
circuit-weaver import-design ./legacy_board --analyze
circuit-weaver status ./legacy_board
circuit-weaver resume ./legacy_board
circuit-weaver analyze-design ./legacy_board

# ── Placement ─────────────────────────────────────────────────────────────────
circuit-weaver optimize-placement design.yaml --iterations 5000 --seed 42 -o output/placement.json
circuit-weaver placement-viewer design.yaml -o output/viewer.html
circuit-weaver import-placement placement.svg board.kicad_pcb -o out.kicad_pcb
circuit-weaver import-placement subset.svg board.kicad_pcb -o out.kicad_pcb --allow-partial
circuit-weaver check-dfm electrical_board.kicad_pcb --profile jlcpcb
circuit-weaver panelize --board-width 50 --board-height 40 --qty 100
circuit-weaver export-dual-cpl design.yaml --pcb electrical_board.kicad_pcb -o ./jlcpcb

# ── Simulation & confidence ──────────────────────────────────────────────────
circuit-weaver simulate design.yaml -o ./sims      # Run SPICE simulations (ngspice)
circuit-weaver confidence design.yaml --run-sims   # Full design readiness score (0-100)
circuit-weaver confidence design.yaml -o report.html --pcb board.kicad_pcb

Run circuit-weaver --help or circuit-weaver <subcommand> --help for full flag reference.


Python API

python
from circuit_weaver.dispatcher import (
    validate_design,
    apply_design_patch,
    generate_artifacts,
    diff_designs,
    ingest_pcb_feedback,
)
from circuit_weaver.design_import import analyze_design, import_design
from circuit_weaver.project_state import get_project_state_summary, resume_project

# Validate a canonical design spec
report = validate_design(spec)

# Apply a transactional patch and re-validate
result = apply_design_patch(spec, patch)

# Generate the full bundle; require real KiCad for a release-quality claim
bundle = generate_artifacts(spec, output_dir="out/design", require_kicad=True)

# Non-destructively open and analyze KiCad/PCB/Gerber/ZIP sources
opened = import_design("legacy-board.zip", project_dir="work/legacy", analyze=True)
state = get_project_state_summary(opened["project_root"])
restart_plan = resume_project(opened["project_root"])
analysis = analyze_design(opened["project_root"])

Validation groups

validate_design runs five grouped checks and returns a structured ValidationReport:

GroupWhat it checks
structuralTopology, block connections, hierarchy integrity
electricalPower rails, ground nets, net continuity
implementationPart bindings, footprint assignments, pinout verification
placement_readinessHard-gated — dangling buses, missing I2C pull-ups, orphan interfaces, floating enables; never bypassable by --no-require-valid
presentationLabels, pin numbers, sheet readability

HTTP API

bash
uvicorn circuit_weaver.api:app --host 0.0.0.0 --port 5000
EndpointMethodDescription
/healthGETService health
/capabilitiesGETMachine-readable capability maturity and verification contract
/templatesGETAvailable subcircuit templates
/generatePOSTYAML spec → ZIP of .kicad_sch + report
/validatePOSTYAML spec → validation JSON
/mvp/apply-patchPOSTTransactional patch + re-validation
/mvp/diffPOSTSemantic diff between two specs
/mvp/pcb-feedbackPOSTMerge PCB layout feedback into spec
/mvp/generatePOSTJSON/YAML spec to a ZIP with a portable artifact manifest

What's New in v0.33.0

Circuit Weaver v0.33.0 makes electrical recommendations measurable and traceable instead of relying on silent universal defaults.

AreaImprovement
Evidence-backed passivesShared versioned equations, explicit datasheet/equation/bounded-fallback precedence, declared E-series policy, and retained CALC-* evidence for critical support networks.
Fail-closed synthesisInvalid or unsupported regulator, crystal, reset, USB-C, CAN/RS-485, and analog support values are withheld under CW-PSV-* findings before emission.
Typed power accuracyRail limits, direction, current envelopes, sequencing, tolerance, and provenance flow through ingest, validation, reports, placement context, and repair.
Identity safetyExact MPN/package, symbol pin, footprint pad, and two-source reconciliation block physical CPL handoff when identity or pin-to-pad coverage is ambiguous.
Calibrated validationSeverity is separate from detection confidence; actionable findings name the constraint, observation, evidence, and safest next action.
Published scorecardA 40-fixture benchmark covers 33 emitted/contract rule IDs—14 scored and 19 explicitly unsupported—with supported precision/recall at 1.000/1.000.
v0.32.0

Circuit Weaver v0.32.0 is an integrity and compatibility release for agent workflows and programmatic users.

AreaImprovement
Schematic integrityDeterministic sheet/reference allocation, collision-safe symbol naming, strict rendered pin maps, final S-expression checks, and safer label/wire movement for dense designs.
Truthful verificationERC runs against the exact final schematic; results expose kicad_verified and verification_status, while --require-kicad fails closed when verification cannot run.
Durable workflowsAtomic status/resume state plus non-destructive KiCad, PCB, Gerber/drill, and ZIP import with fingerprinted cached analysis.
Professional hierarchyExplicit block sections remain separate functional sheets, support parts retain ownership, and filenames are collision-safe.
Placement reviewExhaustive assembly reconciliation, blocker-aware JSON/context, official-reference links, and editable SVG/HTML; review artifacts are never fabrication data.
Manufacturing and routingJLC/CPL export reconciles real PCB references and footprints; Freerouting publishes validated SES sessions and reports incomplete routing as partial.
Agent workflowsPortable kebab-case skills, narrower triggers, provenance-aware upgrades, and aligned Codex, Claude, and OpenCode installation paths.
Programmatic compatibilityRestored legacy imports and deprecated aliases, strict YAML parsing, exhaustive artifact inventory, and real placement SVG data.
Release reliabilityPython 3.10-3.14, blocking Windows coverage, exact-wheel tests, live MCP tests, and KiCad 8/9/10 generation and ERC gates before PyPI publication.
v0.31.0

Circuit Weaver v0.31.0 collected the Sprint 53-54 schematic layout quality work and graduated the prior 0.30.x sprint-release series into a minor release.

SprintFeature
54Layout quality zero-crossing gate — all quality-gated sample schematics now target zero wire-through-body crossings, with body-aware stubs, tapped-rail splitting, unrounded keep-outs, and generator-visible layout-quality warnings/reports.
54Density, sheet splitting, and autorouter hardening — connector-heavy layouts now use a continuous density score, oversized sheets split instead of cramming onto A0, and Freerouting preflight/effort/timeout handling fail closed with clearer remediation.
53Schematic readability and passive placement — sidecar passives, passive motifs, and local wiring now use occupancy-aware placement and body-aware routing to remove symbol overlaps and sharply reduce wire-body crossings.
52Part-neutral repair and schema plumbing — normalized pin_roles now flow through ComponentDef, ic_data, EasyEDA imports, generic-builder outputs, and cache round-trips, so SPI/UART repair can operate from shared capabilities instead of exact MPN branches.
52Generation and placement hardening — readiness gating now lives in generate_from_components, generic bypass policy is centralized, orphan non-power nets are hard-gated in placement-readiness, and PCB placement preview now penalizes long connected pairs instead of staying purely zone-based.
51Restart and validation flows are more truthful — log-status works for validate-only sessions, persisted validation summaries now reflect the final verdict, Windows text-mode validation falls back to ASCII, and bad data-driven ic resolution now fails closed instead of silently substituting another part.
51Workflow skills are less brittle under long-running sessions — /circuit-weaver now reports the installed CLI version first, long steps require timeout follow-up checks, and the validate-output recipe now preserves JSON on stdout instead of mixing it with stderr.
50Generic builder parity gate is closed — the data-driven path now covers the remaining sensor-front-end, shared-bus, battery, display, and passive-diode contracts that were blocking the sample/corpus release gate; the full suite passes 1009 passed, 1 skipped.
50CLI/package workflows are hardened for PyPI use — read-only spec directories no longer crash file logging, unreadable ~/.config/secrets.env no longer breaks doctor or unknown-part fallback, and the bundled skill payload is resynced byte-identical with skills/.
49Wizard intake now tiers by experience level — the offline design-wizard asks for experience before requirements, uses compact design-brief intake for advanced/professional users, and no longer forces the same opening question flow on every user.
49Specialized RF workflows are now framed correctly — Circuit Weaver skills now route radar / RF / microwave requests into a research-first custom engineering flow instead of treating the lack of turnkey coverage as an out-of-scope rejection.
45-47Schematic paper over-promotion fix — layout_sheet() now starts from the allocator-selected paper size and only promotes if it doesn't fit. Small IoT-sensor-class designs no longer cascade to A2. Tighter title-block clearance keeps content on A3.
45-47Design log severity mapping — DesignLogHandler maps Python WARNING records to "warning" type instead of "error" in design.log.
45-47BME688 bundled IC data — sensor pin/footprint metadata shipped in ic_data/misc.json. IoT_AQ_Sensor_v2 resolves without local custom.json.
45-47JLCPCB assembly variants — generate_assembly_variants() supports include_refs, exclude_refs, dnp_refs subsets; per-variant BOM/CPL output.
45-47Allocator + placement-readiness tests — 52 new dedicated tests closing Sprint 42 coverage gaps.
44Label collision avoidance — overlapping labels on dense sheets are detected and shifted along wire-stub direction. Same-name labels skipped.
44Validate-all regression gate — 14+1 sample YAMLs now validate clean; CI gate enforces zero hard errors.
44Sourcing auditor alternates — queries LCSC/DigiKey for functionally similar parts when a component has CRITICAL/WARNING risk.
44MCP server — circuit-weaver-mcp entry point for AI agent tool access via FastMCP.
44Wire-crossing minimization — placer penalizes crossing-dense placements; bus signal groups detected for future parallel routing.
43Density-scaled grid spacing — inter-component gaps scale to spread content across available page area, preventing corner-clustering on large sheets.
43Annotation overlap prevention — per-IC annotations shift down when they would collide, with overflow line drops.
43Lane routing counter recycling — capped at 6 with modulo wrap, preventing lanes from drifting 194mm from the IC.
v0.27.0
SprintFeature
40Cache-rebuilt components no longer ship as silent 2-pin stubs — SymbolResolver._rebuild_from_cache now marks cache hits without real pin topology as pinout_source="stub", so the existing pinout-source validator gate catches any multi-pin IC (sensor, MCU, H-bridge, gate driver, regulator) that would otherwise emit as a passive. The EasyEDA tier now persists full pin + power + bypass / strap topology via symbol_cache.component_def_to_cache_payload() so round-tripping a part through the cache preserves everything
40Schematic emission invariant — primitives.assemble_sheet now dedupes structural duplicates before writing (symbol instances, wires, global / hierarchical labels, no-connects, junctions, UUIDs). Catches the placer / topology-dispatcher double-emission class of bug that was causing stacked passives, duplicate wires, and shared-UUID power symbols
40Placement PCB preview never fabricates footprints or synthetic pads — the generator field now reads placement_preview so reviewers can tell the file apart from fab-ready output; missing footprint bindings emit Placement_Preview:Missing_<ref> placeholders instead of the old SOIC-8 fallback; and no synthetic pads are emitted for any component. KiCad's schematic → PCB forward annotation is the authoritative source of pads
40generate enforcement is now deterministic across runs — structural + implementation category errors always raise, regardless of require_valid. --no-require-valid now only bypasses soft electrical warnings (dangling dev signals, crystal load-cap tolerance) and the bypass is logged at WARNING level. Two runs on the same spec + cache state always reach the same verdict
40Report-fidelity diagnostic — report.verify_report_fidelity(report_text, components) flags references to component refs, net names, or annotations that don't exist in the resolved design. Catches the ghost-feature pattern where a report claimed "BME688 I2C + pull-ups" or "LED + current-limit R4" without any backing wires
40Five-archetype generation regression corpus — tests/test_generation_corpus.py runs generate_artifacts end-to-end on LED driver, IoT sensor, motor controller, USB bridge, and FPGA power carrier samples, enforcing all three Sprint 40 invariants. Breadth-guard test keeps the corpus at ≥ 5 archetypes
39Step 2 IC research stays in the current agent session across Codex / Claude / OpenCode instead of delegating to a spawned /research / research-analyst path that could trigger model conflicts; workflow docs and skill prompts now describe the real behavior
39Research-depth latency selector — design-wizard --research-depth {fast,normal} persists into spec metadata; doctor reports the effective depth; Circuit Weaver skill uses a smaller query budget in fast mode
v0.26.1
SprintFeature
38Research workflow is now reproducible end-to-end — design-wizard --research-backend persists the effective backend into spec metadata, save-research records the canonical JSON artifact path in design.log, and the workflow docs now tell agents to treat output/research/ as the source of truth
38Resolver credential diagnostics now match real runtime behavior — DigiKey checks both DIGIKEY_CLIENT_ID and DIGIKEY_CLIENT_SECRET, Mouser honors MOUSER_SEARCH_API_KEY through the shared credential loader, and circuit-weaver doctor now reports both credential states directly
37Research persistence + backend selection shipped in the CLI — circuit-weaver save-research, CIRCUIT_WEAVER_RESEARCH_BACKEND, and circuit-weaver doctor backend reporting are now available in the published package
v0.25.0
SprintFeature
35install-skills collision protection — stopped silently overwriting a curated SKILL.md; added --force, --backup, and --dry-run with collision reporting for review
35All 11 skills bundled in the wheel — the full set, including design-wizard, is kept in sync by scripts/sync_bundled_skills.py with CI and pre-commit drift guards
35Windows CI leg — windows-latest / Python 3.12 smoke run (non-blocking first sprint) covering CLI commands, doctor, skill installer, and python -m circuit_weaver --version
v0.24.0
SprintFeature
34Data-Driven Template Engine — IC data now lives in JSON files under src/circuit_weaver/ic_data/ (11 categories). New topology_builders.py produces schematic fragments dynamically, replacing hardcoded template classes
347 New Subcircuit Templates — RTC (DS3231, PCF8563), EEPROM (24LCxx, 25LCxx), wireless modules (nRF52, ESP32, LoRa), USB-C connectors, SPI bus conditioning, voltage references (REF5025, LM4040), generic connectors — total template count now 37
34IC Registration CLI — scripts/extract_ic_data.py harvests IC entries from datasheet research; register_ic() API persists to custom.json
33Platform Compatibility — full Claude Code / Codex / OpenCode support across all skills, updated shim files, skill trigger disambiguation
32CLI Integration Tests — 24 end-to-end CLI tests; informational output moved to stderr
31Bug Fixes & Hardening — thread-safe logging bridge, correct zero-check scoring, connector MPN validation, SPICE value parser edge cases
v0.22.0
SprintFeature
30Confidence Dashboard — circuit-weaver confidence aggregates 7 data sources into a 0-100 readiness score with HTML report; now a mandatory step in the wizard flow
30Workflow Overhaul — wizard now 9 steps: added auto-detection, confidence check, and PCB layout preparation (placement optimizer, SVG editor, autoroute, DFM check)
29Enhanced Validations — 3 new checks (power budget, thermal limits, signal integrity); cross-reference auditor validates spec-vs-schematic-vs-BOM consistency
28Circuit Simulation Engine — SPICE netlist generation, ngspice runner with graceful degradation, simulation orchestrator with auto-planning and confidence scoring
27Project Discovery — circuit-weaver discover auto-detects projects in CWD; all skills now pre-check before asking for paths
26Logging Overhaul — 13 structured event types in design.log, Python logging bridge, log-event CLI for skill-callable logging, 7 modules instrumented
v0.21.0
SprintFeature
25Component Selection Rationale — HTML review report now includes a per-IC table showing why each part was chosen, key electrical specs, and any reference design cited
25Auto Test Point Generation — generate_artifacts() emits {project}_test_points.csv and test-point report data while leaving the validated schematic bytes unchanged (annotated_schematic: false); detects power, ground, clock, bus, and differential-pair nets
24Firmware Co-Design Export — Auto-generates {project}_pinout.csv, STM32 .ioc skeleton, and ESP32 sdkconfig.defaults when MCU blocks are present
23KiCad CLI ERC Integration — circuit-weaver erc runs KiCad's built-in ERC and surfaces results in the HTML report with a pass/fail badge
22Pinout Verification Gate — ICs using unverified stub pinouts now fail validation before any schematic is emitted

Repo Layout

text
circuit-weaver/
├── src/circuit_weaver/      # Core engine
│   ├── dispatcher.py           # Public API: validate, patch, generate, diff, pcb-feedback
│   ├── design_ir.py            # Canonical design intermediate representation (DesignIR)
│   ├── generator.py            # .kicad_sch file emitter
│   ├── validator.py            # 14-check validation pipeline (electrical + thermal + SI)
│   ├── cross_reference_validator.py  # Spec vs schematic vs BOM audit
│   ├── confidence_dashboard.py # Design readiness scoring (0–100) + HTML dashboard
│   ├── simulation.py           # Simulation orchestrator (plan → run → score)
│   ├── spice_netlist.py        # SPICE .cir netlist generator
│   ├── spice_runner.py         # ngspice subprocess runner with graceful degradation
│   ├── symbol_resolver.py      # IC symbol resolution chain (EasyEDA → cache → stub)
│   ├── symbol_cache.py         # Persistent symbol cache with full pin/power map schema
│   ├── research.py             # Research query orchestration (Perplexity / native web)
│   ├── research_store.py       # Research artifact persistence (JSON + summary.md)
│   ├── doctor.py               # Credential + backend diagnostics (circuit-weaver doctor)
│   ├── logging_bridge.py       # Unified logging: Python logging ↔ DesignLogger bridge
│   ├── design_logger.py        # Structured JSON Lines workflow logging (13 event types)
│   ├── project_discovery.py    # Auto-detect circuit projects in directories
│   ├── review_report.py        # HTML review report generator
│   ├── test_point_gen.py       # Auto test-point classification and CSV export
│   ├── firmware_export.py      # MCU co-design stubs (pinout CSV, .ioc, sdkconfig)
│   ├── placer.py               # Topology-aware schematic placement engine
│   ├── placement_optimizer.py  # Simulated annealing PCB placement optimizer

Agent Platform Support

PlatformWhat's included
Claude Code/circuit-weaver global skill via install-skills
Codex$circuit-weaver from the current global ~/.agents/skills location
OpenCodeAgent Skills from ~/.agents/skills, or $OPENCODE_CONFIG_DIR/skills when configured
KiloGlobal skills under $KILO_CONFIG_DIR/skills or ~/.kilo/skills

Install for all platforms at once:

bash
# Bash (Mac/Linux/WSL)
./install.sh --platform all

# PowerShell (Windows)
./install.ps1 -Platform all

The wrappers install the checkout and delegate skill copying, upgrades, dry runs, and conflict handling to the same Python installer. They honor CLAUDE_CONFIG_DIR, OPENCODE_CONFIG_DIR, and KILO_CONFIG_DIR; Codex uses ~/.agents/skills. Use --skills-only / -SkillsOnly to avoid reinstalling the package.


Sample Design

PyPI installs include a portable IoT starter. Copy it into a writable project directory, then run the full workflow:

bash
python -c "from importlib.resources import files; from pathlib import Path; d=Path('iot_sensor_example'); d.mkdir(exist_ok=True); d.joinpath('design.yaml').write_bytes(files('circuit_weaver').joinpath('examples','iot_sensor.yaml').read_bytes())"

# Validate
circuit-weaver validate iot_sensor_example/design.yaml

# Generate schematic + report + test points + firmware stubs
circuit-weaver generate iot_sensor_example/design.yaml -o ./output

# Export a BOM-only delivery (no heuristic CPL is invented)
circuit-weaver export-jlcpcb iot_sensor_example/design.yaml -o ./output/jlcpcb

# After creating a real electrical PCB, export a reconciled BOM + CPL
circuit-weaver export-jlcpcb iot_sensor_example/design.yaml \
    --pcb ./output/iot_sensor.kicad_pcb -o ./output/jlcpcb

A source checkout also includes the larger reference gallery under samples/.


Contributing

bash
# Install with dev dependencies
pip install -e ".[dev]"

# Install pre-commit hooks
pre-commit install

# Lint
python -m ruff check src tests

# Test
python -m pytest tests -q

Pre-commit hooks run ruff, YAML validation, and circuit-weaver validate --strict on changed design specs automatically.


License

MIT. See LICENSE.

Parts

5
QtyValueFootprintReferences
1ESP32-WROOM-32ERF_Module:ESP32-WROOM-32EU4
1MAX17048G+TDFN-8-EPU2
1MCP73831T-2ACI/OTSOT-23-5U1
1TLV75518SOT-23-5U3
1USB-CConnector_USB:USB_C_Receptacle_GCT_USB4085J1

More from mattpainter701/circuit-weaver

8
  • 2 layers102 × 70 mmIoT Sensor Node placement, the printed circuit board in 3D

    IoT Sensor Node placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    5 parts1MIT
  • 2 layers68 × 73 mmUSB UART Bridge placement, the printed circuit board in 3D

    USB UART Bridge placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    5 parts1MIT
  • 2 layers50 × 40 mmFPGA Power Carrier placement, the printed circuit board in 3D

    FPGA Power Carrier placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    4 parts1MIT
  • 2 layers71 × 70 mmOLED Display Module placement, the printed circuit board in 3D

    OLED Display Module placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    4 parts1MIT
  • 2 layers50 × 70 mmUSB Regulated Supply placement, the printed circuit board in 3D

    USB Regulated Supply placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    3 parts1MIT
  • 2 layers71 × 43 mmZigbee Humidistat placement, the printed circuit board in 3D

    Zigbee Humidistat placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    3 parts1MIT
  • 2 layers50 × 70 mmLED Power Indicator placement, the printed circuit board in 3D

    LED Power Indicator placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    2 parts1MIT
  • 2 layers64 × 44 mmMotor Controller placement, the printed circuit board in 3D

    Motor Controller placement

    mattpainter701/circuit-weaver

    Programmatic KiCad schematic generation, strict validation, and manufacturing export designed for AI-assisted hardware workflows — Claude Code, Codex, and offline CLI.

    2 parts1MIT

Similar boards

  • 4 layers92 × 56 mmREIN R1, the printed circuit board in 3D

    REIN R1

    rein-baremetal/REIN_R1_KiCad

    Dual-MCU baremetal embedded development board featuring high-speed QSPI storage, hardware USB hub, and flexible power management. Open for PCB trace routing collaboration

    177 parts2
  • 2 layers96.2 × 129.6 mmPendant, the printed circuit board in 3D

    Pendant

    cumhuronat/mr-1-openpendant

    An opensource pendant project MR-1 CNC

    62 parts1
  • 4 layers60 × 40 mmRCcar, the printed circuit board in 3D

    RCcar

    jeffreydthompson/Open_Roadster

    Support files for course creating BLE remote controlled car from scratch.

    95 parts1
  • 4 layers75 × 59.2 mmData logger, the printed circuit board in 3D

    Data logger

    Mutzi1211/Wasserrakete

    Ein Überblick über alle Projektbestandteile – von CAD über Code bis zu Anforderungen und Abgaben.

    65 parts1
  • 4 layers80 × 60 mmCore, the printed circuit board in 3D

    Core

    abolambA/Luxera

    Luxera One is a from-scratch attempt to build what the big labs keep teasing: AR glasses that look like actual glasses. Everything — compute, batteries, optics, sensors, audio — seals inside a chunky acetate frame.

    56 partsMIT
  • 4 layers96 × 96 mmMusicPlayer, the printed circuit board in 3D

    MusicPlayer

    JoshuaSLE/stm32g-music-player

    Standalone embedded audio system engineered with an STM32G031K8 microcontroller using HAL drivers for peripheral management and a VS1053B codec for real-time decoding and playback.

    79 partsMIT
  • 2 layers42 × 85 mmKasa remote, the printed circuit board in 3D

    Kasa remote

    Paumanok/kasa-remote

    An ESP32 based remote control device for manipulating and monitoring TPLink Kasa devices.

    47 parts
  • 2 layers65 × 56 mmTeamc carrier, the printed circuit board in 3D

    Teamc carrier

    SantiBarrios2002/mtp-f26-teamc

    MTP F26 (UPC) Team C workspace: radio link budget, RFM69 firmware, protocol simulator

    94 parts

Questions

How big is the Battery IoT Sensor placement PCB?

It measures 63 × 70 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Battery IoT Sensor placement use?

5 parts, built around the ESP32-WROOM-32E, MAX17048G+T10 and MCP73831T-2ACI/OT-HXY. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Battery IoT Sensor placement KiCad files?

From the mattpainter701/circuit-weaver repository on GitHub, at the commit this page was made from: the board is samples/battery_iot_sensor/Battery_IoT_Sensor_placement.kicad_pcb and its schematic samples/battery_iot_sensor/Battery_IoT_Sensor.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Battery IoT Sensor placement design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).