Development Guide
This section explains how development work is organized in the repository and where the operational guidance lives.
Read This Section In Order
- Development Conventions explains the project-wide engineering expectations for contributor workflow, module design, dependency management, and documentation upkeep.
- Tooling and Validation explains the practical commands for environment setup, CLI entrypoints, quality checks, and sanity checks. It is the documentation-facing version of
.github/prompts/tooling.prompt.md. - Backlog and Internal Docs explains how to use Backlog.md for planned work and how to read the developer-oriented documents under
backlog/docs/.
Repository Landmarks
lav2/: package source for controllers, dynamics, trajectories, tasks, and runtime helperslav2/assets/: MuJoCo MJCF, meshes, and USD assetsscripts/: thin wrappers for backend-specific launch flows.github/prompts/: operational prompts used by contributors and coding agentsbacklog/: project planning, milestones, tasks, and internal reference docs
Engineering Conventions
Project-wide contributor expectations now live in Development Conventions. That page covers workflow requirements, module design, dependency management, export policy, documentation upkeep, and the interface consistency rules that apply across the repository.
Scope of This Guide
The pages in this section intentionally focus on development workflow rather than implementation theory. They summarize and organize the operational content that was previously scattered across CONTRIBUTING.md, .github/prompts/, and backlog/docs/.