How Flempy works

What actually happens when you type a prompt and hit Generate.

The big picture

Flempy is an AI-driven schematic editor. You describe what you want in plain English. A coordinator agent dispatches to specialist sub-agents (intent classifier, topology planner, component selector, netlist generator, placement planner). Each one reads and writes a shared netlist in the Circuit JSON format. The browser re-renders the schematic live as each tool call lands.

The pipeline

  1. Intent classifier — decides whether you want to build something new, tweak the current design, ask a question, or start over.
  2. Topology planner — sketches the circuit structure without committing to specific parts. Decides "I need a boost converter, then an LDO, then the MCU rail."
  3. Component selector — picks real parts for each slot (ESP32-WROOM-32, LM2577, AMS1117-3.3, etc.).
  4. Netlist generator — emits the components and wiring via tool calls — add_component, connect_pins, emit_netlist_patch.
  5. Placement planner — assigns each component a position on the schematic canvas so the layout reads top-down.
  6. Trace solver — routes the wires orthogonally between pins, avoiding component bodies.

The netlist as source of truth

Everything in Flempy reads from one data structure: Circuit JSON (an open standard maintained by tscircuit). Schematic canvas, 3D breadboard, and BOM all project from the same netlist — there's no separate rendering state to drift out of sync. When the AI calls a tool that mutates the netlist, every view updates atomically.

Why this matters for you

  • You can inspect any part of the design. Click a component for its pins and part number. Click a wire to see its full net.
  • Edits are surgical. Ask for "change R1 to 1kΩ" and the AI emits a one-field patch, not a regeneration.
  • The BOM is always current. Every tool call that adds or removes a component is reflected in the BOM tab in the same frame.

Where it fits

Flempy targets low-voltage electronics — battery-powered IoT, audio devices, custom keyboards, retro-computing builds, and art installations. Stay clear of mains voltage, unprotected lithium chemistries, and safety-critical systems (medical, aerospace, automotive).

Next up: how to write prompts Flempy understands.