Agent Skills › dartsim/dart › dart-build

dart-build

GitHub

指导DART项目的构建流程，涵盖CMake配置、pixi依赖管理及常见错误排查。支持CUDA环境检测与验证、锁文件规范，以及Filament GUI的无头渲染视觉检查，确保代码格式与测试通过。

.claude/skills/dart-build/SKILL.md dartsim/dart

Trigger Scenarios

需要配置或构建DART项目时遇到CMake或依赖安装错误时进行CUDA编译或测试时修改依赖或提交PR涉及lockfile时验证Filament图形渲染效果时

Install

npx skills add dartsim/dart --skill dart-build -g -y

More Options

Non-standard path

npx skills add https://github.com/dartsim/dart/tree/main/.claude/skills/dart-build -g -y

Use without installing

npx skills use dartsim/dart@dart-build

指定 Agent (Claude Code)

npx skills add dartsim/dart --skill dart-build -a claude-code -g -y

安装 repo 全部 skill

npx skills add dartsim/dart --all -g -y

预览 repo 内 skill

npx skills add dartsim/dart --list

SKILL.md

Frontmatter

{
    "name": "dart-build",
    "description": "DART Build: CMake, pixi, dependencies, and build troubleshooting"
}

DART Build System

Load this skill when working with DART's build system.

Quick Commands

pixi run configure    # Configure CMake
pixi run build        # Build
pixi run test         # Run tests
pixi run test-all     # Full validation (lint + build + tests)
pixi run -e cuda test-all # CUDA-enabled full validation on Linux CUDA hosts
pixi run lint         # Format code

Full Documentation

For complete build instructions, read: docs/onboarding/building.md

For build system internals (CMake, dependencies): docs/onboarding/build-system.md

Common Issues

Issue	Solution
CMake not found	`pixi install`
Missing dependency	Check `pixi.toml`
Build failure	`pixi run configure` then `pixi run build`
Linking error	Check CMakeLists.txt in relevant module

CUDA Notes

On Linux hosts with visible NVIDIA GPUs, the CUDA Pixi config auto-detects compute capabilities for DART_CUDA_ARCHITECTURES; set DART_CUDA_ARCHITECTURES=<arch> only when overriding that detected list.
If CUDA runtime tests fail with unsupported PTX/toolchain errors, verify the generated CUDA flags include the local GPU architecture before assuming a kernel bug.

Pixi Lockfiles

Do not edit pixi.lock by hand. Change dependency constraints in pixi.toml, then run a Pixi command such as pixi install to let Pixi regenerate the lockfile.
If pixi.lock changes format or has broad solver churn, keep the generated output and call it out in the PR rather than attempting to splice lockfile entries manually.

Filament GUI Visual Checks

For Filament GUI rendering changes, run a bounded headless capture through pixi run ex dartsim --headless --frames ... --width ... --height ... --screenshot .... Prefer at least 1280px width when judging visual quality.
Inspect the rendered image yourself; do not rely only on command success. The headless smoke analyzer under the private Filament test helpers is useful for a smoke signal, but it is not a substitute for visual inspection.
If the user explicitly asks for pixi run ex dartsim, also run that exact entry point and terminate it after confirming the GUI binary launches.