← Circuitcaster · Case study
Case study · July 2026

An AI designed this solar phone charger from a one-sentence prompt.

Then it labeled every pin, color-coded the wires by net, produced a professional bill of materials, and added a fuse and indicator LED when I asked for them. Zero prompt engineering. A single paragraph, three follow-ups, twelve real components, one working schematic. This is Circuitcaster with an AI in the driver's seat.

Designer: Claude Opus 4.8 Tool: Circuitcaster v1.5 Interface: Claude in Chrome Total prompts: 4 Total actions: 286 in the app Final BOM: 12 components
4prompts
12components
15wires drawn
5nets color-coded
1complete BOM
0prompt engineering

1.The prompt

Pasted verbatim into the Claude side panel next to app.circuitcaster.com. No custom system message, no examples, no schema hints. Just this:

Prompt · verbatim
Design a solar-powered USB cell phone charger circuit in Circuitcaster. Input: a 12V solar panel (2-pin screw terminal or header). Output: USB-A 5V at up to 1A. Use an LM2596 step-down buck converter as the core switching regulator, with its standard support components (input bulk capacitor, output smoothing capacitor, inductor, Schottky flyback diode). Add a reverse-blocking Schottky diode on the panel input so the battery can't drain back through the panel at night. Feed the 5V regulated output to a 4-pin USB-A output header (VBUS, D+, D-, GND). Please open https://app.circuitcaster.com and follow the /llms.txt manual. Organize the schematic so wire crossings are minimal — don't try to eliminate every crossing, just keep them as few as possible.

2.What Opus built (153 actions later)

Opus navigated to app.circuitcaster.com on its own, read the site's /llms.txt AI manual, discovered the window.CIRCUITCASTER driving surface, and built the whole thing. It saved the project as "recharge" and told me how it wired everything.

GND rail J1 · Solar +12V GND D1 A→K F1 2A C1 470µF U1 · LM2596-5.0 VIN GND ON OUT FB C3 0.1µF L1 33µH D2 flyback SS34 C2 220µF R1 1kΩ LED1 J2 · USB-A VBUS D- D+ GND → FB tap D+↔D- (DCP) ON→GND
VIN (12V from panel) Switch node 5V rail GND USB D+/D− detect short
Opus's own words: "Signal path (top): J1 (12V solar panel, 2-pin screw terminal) → D1 (reverse-blocking Schottky) → C1 (input bulk cap) → U1 (LM2596 buck) → L1 (inductor) → C2 (output smoothing cap) → J2 (USB-A output header). The ground rail runs along the bottom, and D2 (the flyback Schottky) sits at bottom-center near the switch node. Every pad is connected — no orphan pins."

3.Then I asked it to label and color-code everything

Prompt: "label all the pins and use wire colors that make sense, label each component also for easy placement". Opus took 100 more actions to apply a net-based color palette (each net = a distinct color) and label every single pin by function. Saved as a new project so the original stayed untouched.

Pin labels applied automatically per Opus's design:

U1
LM2596: VIN, OUT, GND, FB, ON_OFF
J1
Solar panel: +12V, GND
D1
Reverse-block Schottky: A (anode from panel), K (cathode to VIN)
C1, C2
Electrolytic caps: + and − on each
L1
Inductor: IN (from switch node), OUT (to 5V rail)
D2
Flyback Schottky: A (to GND), K (to switch node)
J2
USB-A output: VBUS, D−, D+, GND (D+ ↔ D− shorted for DCP handshake)

4.Bill of materials

Opus produced the BOM with practical notes on values, footprint variants, and current-rating trade-offs — the kind of context a good engineer includes. When I asked to add fuse + bypass cap + indicator LED, it added four more parts to both the schematic AND the BOM in one turn.

RefComponentSuggested value / partQtyNotes
U1Buck regulator (step-down)LM2596S-5.01TO-263-5 / TO-220-5. Fixed 5V so FB ties direct to output.
L1Power inductor33 µH, ≥2 A1Shielded preferred.
D1Schottky diode — reverse-blockingSS34 / 1N58221Blocks night-time back-drain through the panel.
D2Schottky diode — flybackSS34 / 1N58221Fast recovery, low Vf.
C1Input bulk cap470 µF, 25 V electrolytic1Rated above 12V panel voltage.
C2Output smoothing cap220 µF, 16 V electrolytic1Low-ESR recommended.
C3Input bypass cap0.1 µF ceramic, 50 V1Across U1 VIN–GND, placed close to the regulator.
F1Fuse + holder~2 A slow-blow1In series on the panel + line, before D1.
R1LED series resistor1 kΩ, 1/4 W1~3 mA at 5V.
LED1Power/charge indicator3 mm LED (any color)15V → R1 → LED → GND.
J1Panel input connector2-pin screw terminal, 5 mm pitch1+12V and GND from solar panel.
J2USB-A output connectorUSB-A female, 4-pin1VBUS, D−, D+, GND. D+ ↔ D− shorted so phones draw full DCP current.

Rows tinted amber are the four parts Opus added when I asked for optional protection + indicator: bypass cap, fuse, current-limit resistor, indicator LED.

5.What's remarkable about this

Every one of these is a genuine engineering deliverable. None of them required prompt engineering, worked examples, chain-of-thought scaffolding, or agent frameworks. Circuitcaster exposes a machine-readable manual at /llms.txt and a JavaScript surface at window.CIRCUITCASTER. Opus reads them and drives the app the same way an engineer would — just faster.

Even the bug reports are useful. Opus noticed the on-canvas component captions displayed the internal id ("c1") instead of the human-readable designator ("U1") and told me so unprompted. That got fixed in v1.5.6 the same evening.

Try it yourself.

Point any AI browser at Circuitcaster and give it a naked prompt. See what comes out.

⚡ Open Circuitcaster