Operate and debug the distributed teleop infrastructure (Mac+Quest operator node, GCP cloud relay, Orin+YAM robot node, and remote GPU model services). Use when: something is down or stale (video, joints, input, policy, tracker); choosing/provisioning hardware for inference; restarting/deploying any tier; remote-managing a GPU or the Orin over ssh; or when a new infra issue gets root-caused — append it to the Issue log here so it is never re-debugged from scratch.
Logging conventions + latency instrumentation for the teleop stack. Use when: adding log lines or latency probes to any tier; diagnosing teleop lag from [lat] lines; hunting for the right log file on the Mac/Orin/relay; or when a new logging convention is adopted — record it here so every tier stays greppable the same way.
Read the docs BEFORE writing code whenever we start using a new external project, library, framework, tool, or file format — or try a new part of one we already use. Vendor the authoritative docs into docs/refs/<project>/ as a persistent, searchable reference, then do an in-depth search of those docs + the project's own examples for OUR specific use case to see whether guidance already exists, and only then implement. Use when: adding/integrating a new dependency or format; doing something new with an existing one; or when files/APIs "don't add up" and we're trial-and-erroring against an external tool. The project's docs are the source of truth — not assumptions, not training-data memory, not "it looks like a one-liner."
Quick symptom -> fix lookup for known teleop papercuts (no re-debugging). Use when: a familiar small failure appears (dead joystick/menu, stale saved IP, NO SIGNAL flash, B-button surprises, headset doze fallout) — check here FIRST before investigating; or when a small error gets a confirmed quick fix — add it here. Deep root-caused outages belong in the infra skill's Issue log instead; link entries there when one exists.
Project coding and deployment hygiene for blupe-evals/LeLab/Jetson work. Use when Codex is modifying blupe-evals, patching installed LeLab, changing Jetson setup, adding scripts, running services, or deciding where code/configuration should live. Enforces that durable code lives in the repository, environment changes are reproducible from repo-owned scripts or patches, and Jetson state can be wiped and rebuilt without losing work.
Logging conventions + latency instrumentation for the teleop stack. Use when: adding log lines or latency probes to any tier; diagnosing teleop lag from [lat] lines; hunting for the right log file on the Mac/Orin/relay; or when a new logging convention is adopted — record it here so every tier stays greppable the same way.
Operate and debug the distributed teleop infrastructure (Mac+Quest operator node, GCP cloud relay, Orin+YAM robot node). Use when: something is down or stale (video, joints, input); restarting/deploying any tier; remote-managing the Orin over ssh; or when a new infra issue gets root-caused — append it to the Issue log here so it is never re-debugged from scratch.
Add a robot arm to XRoboToolkit MuJoCo teleop in blupe-evals — the recipe plus the EE tool-frame gotcha that cost us a day on YAM. Use when integrating a new arm or debugging "gizmo/wrist orientation is wrong" teleop.