jlc-cli 是做什么的？
Operate the JLC China website via a business CLI. This is an unofficial community project without official endorsement from JLC. Use commands for routine workflows; only interact with the reserved CDP page when a command returns a pending human takeover status.
Installation Check
Before executing any business command, first run jlc-cli --version, and after success, run jlc-cli --help. Installing this Skill does not automatically install the CLI.
If the command is not found (command not found or not recognized), inform the user that the CLI is not installed or not in PATH, and provide a link to the project repository and installation instructions. The CLI is not currently published on npm; do not install third-party packages with the same name. After preparing Node.js 22.12 or higher, npm, Git, and Google Chrome, install from source:
git clone https://github.com/TXyy2023/jlc-cli.git
cd jlc-cli
npm ci
npm run build
npm pack
npm install -g ./jlc-com-cli-1.0.0-dev.1.tgz
jlc-cli --version
jlc-cli --help
The package name corresponds to the current development version; when the version changes, use the actual filename generated by npm pack. If a source directory already exists, verify the path first without overwriting the user's directory. After installation, re-check the version and help, then continue the original task. If the command exists but fails to start, report the actual error and check Node.js version and PATH; do not treat startup failure as "not installed" and blindly reinstall.
Getting Started
After completing the installation check, run jlc-cli browser doctor --json to verify browser availability. jlc-cli skill path returns the Skill delivered with this CLI; prefer using the same version documentation.
For first use, present the initialization scope returned by jlc-cli init --json to the human, obtain explicit consent, then run jlc-cli init --accept --confirmed-by human. The human may also run init interactively. Then configure the browser, initiate login, and verify auth status. When scanning a QR code, display the current QR code returned by the command to the human. Login completion is determined by the account status verification result, not by page navigation or scan action alone. After login, a query can be performed with jlc-cli account show --json.
The current real-world workflow explicitly uses jlc-cli browser configure --clear-endpoint --engine chrome. The default Obscura runtime has been verified, but there are still compatibility issues with the real customer center SPA and login iframe; do not treat runtime connectivity as business availability, and do not claim automatic browser switching. If the CLI has its own session-switching engine, stop the current session first; see Browser and Login Commands for details.
Business Index
| Requirement | Command Group & Reference |
|---|---|
| Installation discovery, initialization, browser, account configuration, multi-method login, QR code, success callback | Commands & Login |
| Upload/parse/preview, parameters, quotes, inspection & order creation | PCB Workflow |
| PCB/FPC orders, balance payment, Jia Xiaozhi | Orders & Payment |
| JSON status, exit codes, task observation, CDP takeover, unknown results | Results & Recovery |
Mandatory Decision Boundaries
default: Ask the user when production parameters are not decided by the user. Website presets, previous configurations, and parsed facts are not automatically treated as user choices.auto: Only after the user expresses an intention for the Agent to help fill in parameters, then suggest and fill in according to their constraints; explain the reasoning, and ask if there is a conflict. The mode flag itself is not authorization.- After setting parameters, read the actual effective values. If the website changes or resets a user's choice, report the discrepancy; do not accept replacement values on the grounds that the workflow can continue.
- Upload, preview, and quote do not automatically authorize order creation. When the user has authorized order creation, first check the summary, then explicitly submit; do not treat a quote as an order or payment.
- Each balance payment requires human confirmation of the current account, order, amount, and payment method. Only pass
--human-confirmedwhen the current summary has received explicit human consent; do not fake confirmation or modify local confirmation records. The CLI validates binding, timeliness, and single-use; the flag itself does not prove the conversation fact. Initialization,auto, and takeover cannot substitute for payment confirmation. - When the result is unknown, first verify the original task and order; do not re-submit or re-pay. Maintain the correspondence between tasks, files, account configurations, and pages; takeover cannot extend existing business authorization.
Only report results actually verified by the command. QR delivery, login completion, parse completion, order creation, and payment are different statuses. Do not fabricate missing fields; do not fill in obfuscated site information. Available capabilities and actual acceptance boundaries are based on the current CLI help and project verification records.