菜单
Use when: adding a meshsa transport, radio driver, Meshtastic path, TAK transport, HaLow/IP link, reconnect logic, transport registry entry, or Transport Protocol implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | meshsa-add-transport |
| description | Use when: adding a meshsa transport, radio driver, Meshtastic path, TAK transport, HaLow/IP link, reconnect logic, transport registry entry, or Transport Protocol implementation. |
| argument-hint | Transport name, medium, config fields, and expected send/receive behavior |
TransportConfig.type value.packages/meshsa/src/meshsa/transports/.AbstractTransport when an async inbox and stream() are
enough; otherwise implement the Transport Protocol exactly.@transport_registry.register("name") and accept
name, queue_maxsize, and **options where appropriate.TransportConfig.options and
Pydantic config. Do not hide ports, intervals, or backoff values in the router.LoopbackBus,
FakeClock, and SeqIdFactory. Do not require real hardware in unit tests.packages/meshsa/README.md and docs/ARCHITECTURE.md if the new
transport changes user-facing setup or the module map.python -m pytest, mypy src, ruff check ., and
ruff format --check . from packages/meshsa.packages/meshsa/src/meshsa/protocols.pypackages/meshsa/src/meshsa/transports/base.pypackages/meshsa/src/meshsa/transports/loopback.pypackages/meshsa/src/meshsa/transports/tak.pypackages/meshsa/src/meshsa/transports/meshtastic_radio.pypackages/meshsa/tests/test_transports.pypackages/meshsa/tests/test_meshtastic.pypackages/meshsa/tests/test_tak.pyUse when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.
Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.
Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.
Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.