ee-circuit-draw-simulator 0.0.0-stage → 0.2.1

package/AGENTS.md

@@ -0,0 +1,45 @@
+# AGENTS.md
+
+This repository is an **Agent Skill** for circuit work: real simulation, real numbers, real waveforms.
+`SKILL.md` is the single source of truth for the workflow. Read it before answering any circuit question.
+
+## When this applies
+
+Any request that needs circuit behaviour rather than a textbook formula — 电路仿真、波形、滤波器、
+555、运放、振荡器、分压、整流、RC 充放电、生成电路图、可交互电路 — and any request to *do* something
+with a circuit file.
+
+Skip it for pure concept questions ("what is Ohm's law") and for decorative diagrams that need no
+simulation.
+
+## Non-negotiables
+
+1. **Numbers come from the CLI**, from `measurements` / `sample` / `sweep`. Never quote a formula result
+   as a measured value. If you compare theory with simulation, label both.
+2. **Do not re-implement the bridge.** `scripts/circuitlab.mjs` already wraps attach → load → set →
+   step → measure → sample → sweep → SVG → share. If it lacks a capability, extend the CLI.
+3. **Deterministic stepping only** (`sim.step`). `sim.run` is wall-clock driven and irreproducible.
+4. **Never hand-write element coordinates.** Author circuits as netlist JSON (see
+   `references/netlist.md`) or modify built-in circuits with `--set`.
+5. **Multi-terminal parts** (op-amp, 555, transistors) belong to built-in circuits plus `--set`;
+   auto-routing a hand-written netlist with them can stall the solver.
+
+## First run
+
+```bash
+node scripts/circuitlab.mjs probe    # engine present? backend reachable?
+node scripts/circuitlab.mjs setup    # if the engine is missing: clone + build (one time)
+```
+
+`stdout` is JSON only; diagnostics go to `stderr`. During development the CLI starts and stops its own
+static server, so there is no daemon to manage.
+
+## Layout
+
+| Path | Purpose |
+|---|---|
+| `SKILL.md` | skill entry: preconditions, delivery shapes, workflow, hard rules |
+| `scripts/circuitlab.mjs` | the CLI (`setup` / `probe` / `corpus` / `run` / `share` / `shot`) |
+| `scripts/lib/` | engine discovery, SVG rendering, engineering-unit parsing |
+| `references/` | netlist schema, corpus index, MCP tool map, troubleshooting |
+| `vendor/` | gitignored engine checkout created by `setup` |

package/LICENSE

@@ -0,0 +1,339 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

package/README.md

@@ -1,3 +1,226 @@
-# Temporary Holding Version
+# EE Circuit Draw & Simulator
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**English** · [简体中文](README.zh-CN.md)
+
+An [Agent Skill](https://skill.md) that makes your coding agent **actually simulate circuits** instead of describing them from memory. Load or author a circuit, change a resistor, step the simulator deterministically, read node voltages, sample waveforms, sweep a parameter, render an SVG — and hand back a link that opens a live circuit.
+
+```
+your prompt ──▶ agent ──▶ circuitlab.mjs ──▶ headless Chrome ──▶ real nodal-analysis simulator
+                    ◀── numbers · waveforms · SVG · share link ──
+```
+
+Numbers come from the engine, never from a formula the model recalled. Every value in this README was produced by this skill.
+
+- Engine: [ExtCircuitJS](https://github.com/blankwy/ExtCircuitJS) — a CircuitJS1 fork with a JSON netlist layer and an MCP bridge, GPL-2.0-or-later
+- Skill: pure Node ≥ 22, no runtime dependencies, one CLI, JSON on stdout
+- CLI on npm: [`ee-circuit-draw-simulator`](https://www.npmjs.com/package/ee-circuit-draw-simulator)
+- Works with any agent that reads `SKILL.md` (Claude Code, Codex CLI, DeepSeek Harness, WorkBuddy, …)
+
+## What it answers
+
+| Ask | You get |
+|---|---|
+| "What's the cutoff of this RC filter?" | Swept frequency response, −3 dB point from measured Vpp |
+| "What frequency does this 555 run at?" | Measured 239.5 Hz, duty 49.6% (window t=0.2–0.8 s) |
+| "What happens if R2 becomes 22 kΩ?" | Same run, both circuits, comparable numbers |
+| "Show me the waveform / the schematic" | Inline SVG, axes and legend included |
+| "I want to play with it" | Share URL — the circuit opens in the simulator, sliders live |
+| "Why won't this oscillator start?" | `engineSteps`, flat-channel and convergence warnings |
+
+Measured examples (reproducible with the commands below):
+
+| Circuit | Result |
+|---|---|
+| RC low-pass, R=1 kΩ, C=100 nF | Vpp 9.98 → 2.40 V across 100 Hz–6.4 kHz; 0.707× at 1.6 kHz (theory 1591 Hz) |
+| 555 astable, R2 = 10 k / 22 k / 47 k | 239.5 Hz / 108.8 Hz / 50.8 Hz, duty 48–50% |
+| Op-amp non-inverting, R2/R1 = 2 k/1 k | Gain 3: 1 V in → 3.00 V out; the stock 5 V source clips at the ±15 V rail |
+| Divider 9 V, 1 k/2 k | 6 V at the tap |
+
+## Install
+
+### 0. Prerequisites
+
+- **Node ≥ 22**
+- **Chrome or Edge** on the machine (the engine runs in headless Chrome through a page bridge)
+- `git`
+
+### 1. Get the skill and its engine
+
+**As an agent skill (recommended).** The agent needs the files on disk to read `SKILL.md`, so clone:
+
+```bash
+git clone https://github.com/blankwy/ee-circuit-draw-simulator.git ~/ee-circuit-draw-simulator
+cd ~/ee-circuit-draw-simulator
+node scripts/circuitlab.mjs setup
+```
+
+**As a plain CLI.** Also published on npm — no clone, good for scripts and CI:
+
+```bash
+npx ee-circuit-draw-simulator@latest setup     # engine → ~/.ee-circuit/ExtCircuitJS
+npx ee-circuit-draw-simulator run --circuit lrc --step 0.005 --measure all
+```
+
+`setup` clones the engine, installs its build dependencies plus the headless-browser driver (`playwright-core`), and builds `dist/`. One time, ~2–4 minutes. With a clone the engine lands in `vendor/ExtCircuitJS`; installed from npm (0.2.1 and later) it goes to `~/.ee-circuit/ExtCircuitJS`, so upgrading the package never throws away a 2-minute build. Already have an engine checkout? Skip both and point at it:
+
+```bash
+export EXTCIRCUIT_HOME=/path/to/ExtCircuitJS
+```
+
+### 2. Register the skill with your agent
+
+A skill is just a folder with `SKILL.md` at its root, so every agent below uses the same content — only the search path differs. Clone once, then link it in (symlink keeps one copy; a copy also works):
+
+| Agent | User-level path | Project-level path |
+|---|---|---|
+| Claude Code | `~/.claude/skills/` | `.claude/skills/` |
+| Codex CLI | `~/.codex/skills/` | `.codex/skills/` |
+| DeepSeek Harness (`dsh`) | `~/.dsh/skills/` or `~/.agents/skills/` | `.dsh/skills/` or `.agents/skills/` |
+| WorkBuddy | `~/.workbuddy/skills/` | `.workbuddy/skills/` |
+
+```bash
+mkdir -p ~/.claude/skills
+ln -s ~/ee-circuit-draw-simulator ~/.claude/skills/ee-circuit-draw-simulator
+```
+
+Windows (PowerShell; symlinks need Developer Mode or an elevated shell):
+
+```powershell
+New-Item -ItemType SymbolicLink -Path "$env:USERPROFILE\.claude\skills\ee-circuit-draw-simulator" -Target "$env:USERPROFILE\ee-circuit-draw-simulator"
+```
+
+No symlink permission? Copy the folder instead — everything is relative to the skill root.
+
+#### Claude Code
+
+```bash
+ln -s ~/ee-circuit-draw-simulator ~/.claude/skills/ee-circuit-draw-simulator
+```
+
+Ask a circuit question in any session; Claude Code loads the skill when the task matches. Project-scoped: link into `.claude/skills/` and commit it for your team.
+
+#### Codex CLI
+
+Skills are behind a feature flag:
+
+```toml
+# ~/.codex/config.toml
+[features]
+skills = true
+```
+
+```bash
+ln -s ~/ee-circuit-draw-simulator ~/.codex/skills/ee-circuit-draw-simulator
+```
+
+Then either describe the task, or invoke it explicitly with `$ee-circuit-draw-simulator`. `/skills` lists what Codex found. Codex also reads `AGENTS.md`, which this repo ships, so a plain `codex` session in the repo gets the workflow without the flag.
+
+#### DeepSeek Harness (`dsh`)
+
+```bash
+mkdir -p ~/.dsh/skills
+ln -s ~/ee-circuit-draw-simulator ~/.dsh/skills/ee-circuit-draw-simulator
+```
+
+`dsh` scans project `.dsh/skills/` → `.agents/skills/` → `~/.dsh/skills/` → `~/.agents/skills/`, one level deep, exact folder name, `SKILL.md` at the root — this repo already complies (kebab-case name, description under the 500-character render cap). Invoke with `/ee-circuit-draw-simulator`.
+
+#### WorkBuddy
+
+```bash
+mkdir -p ~/.workbuddy/skills
+ln -s ~/ee-circuit-draw-simulator ~/.workbuddy/skills/ee-circuit-draw-simulator
+```
+
+Or drop the folder into a project's `.workbuddy/skills/` to scope it to that workspace.
+
+#### Any other Agent Skills client
+
+Point its skills directory at this folder. Nothing else to configure — no MCP server, no background daemon.
+
+### 3. Check it
+
+```bash
+node ~/ee-circuit-draw-simulator/scripts/circuitlab.mjs probe
+```
+
+`ok: true` means the engine is present and a backend is reachable. If a backend is missing, the next `run` starts a static server itself and shuts it down afterwards.
+
+## Use
+
+```bash
+CLI=~/ee-circuit-draw-simulator/scripts/circuitlab.mjs
+
+# 367 built-in circuits, searchable
+node $CLI corpus --search 555
+
+# one full round: load → measure
+node $CLI run --circuit lrc --measure all
+
+# waveform: 0.6 s of a 240 Hz square wave, SVG out
+node $CLI run --circuit 555square --sample n2 --span 0.6 --points 2000 --settle 0.2 --svg
+
+# parameter sweep: same run, three values, comparable
+node $CLI run --circuit 555square --sweep e14.resistance=10k,22k,47k \
+  --probe n2 --settle 0.2 --span 0.6 --points 2000 --svg
+
+# frequency response, log axis
+node $CLI run --netlist ~/ee-circuit-draw-simulator/references/examples/rc-lowpass.json \
+  --sweep e1.frequency=100,200,400,800,1600,3200,6400 --probe n1 \
+  --settle 0.02 --span 0.02 --points 100 --logx --svg
+
+# share link — no browser needed
+node $CLI share --circuit lrc
+
+# schematic export
+node $CLI shot --circuit lrc --out lrc.svg
+```
+
+`stdout` is always one JSON object; diagnostics go to `stderr`. That is deliberate: an agent can pipe the result straight into its reasoning without parsing prose.
+
+Key flags:
+
+| Flag | Meaning |
+|---|---|
+| `--circuit <name>` / `--netlist <json\|@file>` / `--text` / `--file` | Circuit source. Netlists describe topology only — the compiler lays it out, no coordinates |
+| `--set <ref>=<value>` | Change a part; `e14.resistance`, `ResistorElm#2.resistance`; values accept `4.7k`, `100n`, `2.2M` |
+| `--step <seconds>` | Deterministic advance (chunked internally — the bridge silently truncates long single steps) |
+| `--measure all \| n1,n2` / `--components` | Instantaneous node voltages / element currents |
+| `--sample` `--span` `--points` `--settle` | Time-domain sampling, independent of the engine's scope buffer |
+| `--sweep <ref>=v1,v2,…` `--probe` `--logx` | Parameter sweep, one row per value |
+| `--svg` `--shot` `--share` `--dump` | SVG plot, schematic, share URL, circuit text |
+
+## Layout
+
+```
+ee-circuit-draw-simulator/
+├── SKILL.md                  agent entry: preconditions, delivery shapes, workflow, hard rules
+├── AGENTS.md                 same workflow for agents that read repo instructions
+├── scripts/
+│   ├── circuitlab.mjs        the CLI (setup / probe / corpus / run / share / shot)
+│   └── lib/
+│       ├── backend.mjs       engine discovery, liveness probe, auto-spawn
+│       ├── svg.mjs           waveform/sweep → inline SVG, faceted by unit
+│       └── units.mjs         4.7k / 100n parsing and formatting
+├── references/               netlist schema, corpus index, MCP tool map, troubleshooting
+└── vendor/                   engine checkout from `setup` (gitignored)
+```
+
+## Honesty rules baked into the skill
+
+1. Numbers may only come from `measurements` / `sample` / `sweep` — never from a formula quoted as a measurement.
+2. Only `sim.step` (frozen wall clock). `sim.run` is wall-clock driven and not reproducible.
+3. No hand-written coordinates: hand-written XML that is 1 px off is a silent open circuit.
+4. Multi-terminal parts (op-amp, 555, transistors) use built-in circuits plus `--set`; auto-routing a hand-written netlist with those can stall the solver, and the CLI reports it.
+5. Sparse sampling is reported, not hidden: `resolutionWarning` means "raise `--points` and rerun".
+
+## Limitations
+
+- No interactive canvas in a chat turn: anything clickable is a share link.
+- Share links carry the circuit, not simulation state — the recipient starts at t=0.
+- Offline single-file HTML (`ext bundle-single`) has no circuit library and no Chinese language pack (CORS on `file://`); simulation itself works.
+- The engine is GPL-2.0-or-later; this skill keeps the same licence and does not bundle engine code.
+- Deep-reference files under `references/` are written in Chinese (they carry the author's lab notes); `SKILL.md`, `AGENTS.md` and this README are in English.
+
+## Credits
+
+Built on [CircuitJS1](https://github.com/pfalstad/circuitjs1) by Paul Falstad / Iain Sharp, via the [ExtCircuitJS](https://github.com/blankwy/ExtCircuitJS) fork. Skill text and CLI: GPL-2.0-or-later, see [LICENSE](LICENSE).