IsolaPurr Developer Operations
Use this skill for source checkout work, maintenance, release engineering, HIL/debug sessions, and implementing missing user-facing capabilities.
This skill inherits isolapurr-user-operations: ordinary hardware operation still prefers released-style CLI/devd flows, target evidence, hardware memory, Web Serial as an official path, and command-availability gates.
Checkout Gate
Before project commands, prove the current directory is an IsolaPurr checkout:
git rev-parse --show-toplevel
test -f Justfile
test -f Cargo.toml
test -d web
test -d desktop
Source Commands
- Build firmware:
just build
- Build host tools from source:
just host-tools-build
- Test host tools from source:
just host-tools-test
- Run IPC devd from source:
just devd-serve; use just devd-serve --idle-timeout-secs 0 only for a deliberately persistent development session.
- Run the explicit localhost HTTP bridge for browser/debug UI only:
just devd-http-bridge --bind 127.0.0.1:<port>
- Run CLI from source over IPC:
just isolapurr <args>
- Web checks:
cd web && bun run check && bun run build && bun run test:unit
- Storybook checks when UI changes:
cd web && bun run build-storybook && bun run test:storybook
- Desktop checks:
cd desktop/src-tauri && cargo test
Hardware Safety
- Never auto-select a serial port.
- For development flashing, use owner-confirmed
.esp32-port only after the exact path is approved or selected through the project selector.
- First-time full flash requires explicit confirmation and post-flash identity capture.
- Do not use
mcu-agentd except as a legacy/emergency path.
- Keep Web Serial as an official product path. Do not downgrade it to debug-only while implementing devd.
- Treat the owner-visible hardware interfaces as
USB-A, USB-C, and the 2 mm banana jack.
- The
2 mm banana jack is a bench output on the same TPS/SW2303 power channel as USB-C; it is not an independent supply for HIL, debugging, calibration, monitoring, development flashing, or bench testing.
- For manual TPS / bench output that uses only the
2 mm banana jack, keep the USB-C SW2303 VBUS path disconnected by default. Only leave USB-C powered when the owner explicitly requests shared output and accepts the attached-load risk.
Release Maintenance
- Release assets must include desktop bundles, host-tools archives with
isolapurr and isolapurr-devd, firmware catalog, and referenced firmware artifacts.
- Do not document a user workflow as available until the released CLI exposes it and the release contains the required assets.
- Firmware catalog changes must preserve target, address, hash, version, and build provenance.
Validation
- Match validation to the changed surface, but PR-ready work for CLI/devd alignment must run full Rust/Web/Desktop/Firmware/Release gates when practical.
- HIL evidence must identify transport, target, session or lease, artifact identity, and observed protocol result.
1---2name: isolapurr-developer-operations3description: Develop, maintain, release, and debug IsolaPurr USB Hub as a superset of isolapurr-user-operations: verify source checkout, use Just, build firmware/Web/desktop/host-tools, run isolapurr-devd and isolapurr from source, maintain firmware catalogs and release assets, perform HIL, first-flash, calibration, Web Serial, Local USB, and CI/PR validation.4---56# IsolaPurr Developer Operations78Use this skill for source checkout work, maintenance, release engineering, HIL/debug sessions, and implementing missing user-facing capabilities.910This skill inherits `isolapurr-user-operations`: ordinary hardware operation still prefers released-style CLI/devd flows, target evidence, hardware memory, Web Serial as an official path, and command-availability gates.1112## Checkout Gate1314Before project commands, prove the current directory is an IsolaPurr checkout:1516```bash17git rev-parse --show-toplevel18test -f Justfile19test -f Cargo.toml20test -d web21test -d desktop22```2324## Source Commands2526- Build firmware: `just build`27- Build host tools from source: `just host-tools-build`28- Test host tools from source: `just host-tools-test`29- Run IPC devd from source: `just devd-serve`; use `just devd-serve --idle-timeout-secs 0` only for a deliberately persistent development session.30- Run the explicit localhost HTTP bridge for browser/debug UI only: `just devd-http-bridge --bind 127.0.0.1:<port>`31- Run CLI from source over IPC: `just isolapurr <args>`32- Web checks: `cd web && bun run check && bun run build && bun run test:unit`33- Storybook checks when UI changes: `cd web && bun run build-storybook && bun run test:storybook`34- Desktop checks: `cd desktop/src-tauri && cargo test`3536## Hardware Safety3738- Never auto-select a serial port.39- For development flashing, use owner-confirmed `.esp32-port` only after the exact path is approved or selected through the project selector.40- First-time full flash requires explicit confirmation and post-flash identity capture.41- Do not use `mcu-agentd` except as a legacy/emergency path.42- Keep Web Serial as an official product path. Do not downgrade it to debug-only while implementing devd.43- Treat the owner-visible hardware interfaces as `USB-A`, `USB-C`, and the `2 mm banana jack`.44- The `2 mm banana jack` is a bench output on the same TPS/SW2303 power channel as `USB-C`; it is not an independent supply for HIL, debugging, calibration, monitoring, development flashing, or bench testing.45- For manual TPS / bench output that uses only the `2 mm banana jack`, keep the `USB-C` SW2303 VBUS path disconnected by default. Only leave `USB-C` powered when the owner explicitly requests shared output and accepts the attached-load risk.4647## Release Maintenance4849- Release assets must include desktop bundles, host-tools archives with `isolapurr` and `isolapurr-devd`, firmware catalog, and referenced firmware artifacts.50- Do not document a user workflow as available until the released CLI exposes it and the release contains the required assets.51- Firmware catalog changes must preserve target, address, hash, version, and build provenance.5253## Validation5455- Match validation to the changed surface, but PR-ready work for CLI/devd alignment must run full Rust/Web/Desktop/Firmware/Release gates when practical.56- HIL evidence must identify transport, target, session or lease, artifact identity, and observed protocol result.
ivanli-cn