the signals and their derived score are provisional and subject to change.
validate manually before sharing.
7d3cc4bebd1efe951e0adc38c053d417260867c0none
# AGENTS.md
The working rules for this repository live in [`CLAUDE.md`](CLAUDE.md) — commands, the
architecture worth knowing before editing, and the conventions that are not visible from any one
file. They are not Claude-specific; read that file first whatever agent you are.
## Start here
Jumper is the shared entry point for Train and Design. Read
[`docs/WORKFLOWS.md`](docs/WORKFLOWS.md) to select the route. Movement training uses the root
repository. Appearance and environment creation use the indepe# Instructions for this URDF directory
Read URDF_CONVENTIONS.md before generating or modifying robot assets under this directory. It records the user's accepted naming and export conventions. The user's latest explicit instruction takes precedence.
- Reference model: jumper/urdf/jumper.urdf. Robot/product name is Jumper; identifier is jumper.
- Keep LF/RF/LM/RM/LR/RR case. Movable joints use <PREFIX>_J<index>_joint, starting at J0 per limb (LF/RF: J0-J4; walking legs: J0-J2). Links and fixed joints k# CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
The reference documents are thorough and worth reading rather than rediscovering:
[`docs/WORKFLOWS.md`](docs/WORKFLOWS.md) for Train and Design routing from the shared root,
[`README.md`](README.md) for the tour, [`docs/DESIGN.md`](docs/DESIGN.md) for why the framework is
shaped this way, [`docs/USAGE.md`](docs/USAGE.md) for tasks / assets / defaults,
[`docs/TUTORIAL.md`](docs/TUTORIAL.md) fo---
name: new-task
description: Create a new training task in this repository -- the directory, the registration, the config skeleton and the operator controls, with every control name taken from the gamepad dictionary. Use this whenever someone wants a new task: "创建一个 task", "新建一个任务", "add a task for a bounding gait", "I want a new locomotion task that jumps", "make a task like tripod but slower", or a request that names a gait, a behaviour or a robot and asks for training to be set up ---
name: controls
description: Define what a gamepad or keyboard control means -- a task's stick, button and key bindings, an FSM mode switch on either device, or the button that starts a recorded motion -- with every word taken from the control dictionary. Use this whenever a control is being given a meaning: "A 按下起跳", "用 LB 切进去", "Ctrl + 1 进舞蹈", "把摇杆绑到转向", "add a button to switch into the dance", "which stick drives yaw", "Shift + J 扭身", writing or editing a `contr---
name: bundle-manual
description: Translate a built bundle's manual.en.json into Chinese as manual.zh.json and pack it into the .app. Use right after `python scripts/deploy.py` writes a bundle -- every bundle an agent builds ships with the Chinese manual as well as the English one -- and whenever a bundle is found with manual.en.json and no manual.zh.json, or when asked for "操作说明", "中文说明", "按键说明" or "manual" of a bundle/app.
---
# The bundle's manual, in Chinese
`scripts/deploy.---
name: setup-env
description: Set up, verify or repair the mjrl-lab development environment on Linux, Windows or macOS, with or without an NVIDIA GPU -- the Python environment and the Rust toolchain the controller (deploy/fsm) builds with. Detects the machine, picks the right torch build, finds which of cargo, the wasm target, wasm-bindgen and CycloneDDS are missing, installs, and runs six verification gates. Use this whenever someone is getting this repository running on a new machine, onboarding, or hi---
name: deploy
description: Take a trained policy from a checkpoint to a running robot -- the hardware path specifically, not the browser or `play`, which need no board and no NPU. Export the contract, convert the ONNX to RKNN for the RK3576 NPU, assemble the upload bundle, cross-build the controller and check the board before touching it. Use this for anything on that path: "deploy this policy", "convert to rknn", "why won't the robot run my model", "the robot stands there doing nothing", a DDS topic thanone