dart-references
GitHub用于管理DART实验仿真研究的参考目录,支持添加、更新和审计论文、教材、标准及引擎。提供结构化字段如状态、优先级和裁决,确保引用有据可查并符合项目规范。
Trigger Scenarios
Install
npx skills add dartsim/dart --skill dart-references -g -y
SKILL.md
Frontmatter
{
"name": "dart-references",
"description": "DART References: manage the experimental simulation research catalog (papers, textbooks, engines) with status, priority, and verdict"
}
DART Research References
Load this skill when adding, updating, auditing, or citing research references (papers, textbooks, model-format standards, or comparative engines) for the DART experimental simulation world — its public API and its algorithms.
Catalog Location
docs/readthedocs/papers.md is the single source of truth and the published
website page. It is a companion to the experimental API design docs:
docs/design/simulation_cpp_api.mddocs/design/simulation_python_api.md
Entry Schema
Each entry has an id, a full citation, and these properties:
| Property | Values |
|---|---|
| Type | textbook, paper, standard, engine |
| Topic | e.g. dynamics, kinematics, contact, integration, collision, terminology, model-format, api |
| Status | referenced, planned, in-progress, implemented, deferred, rejected |
| Priority | high, medium, low, — |
| Verdict | adopt, baseline, reference, evaluate, reject |
| Where used | link to the design doc, code, or test that uses (or will use) it |
Status is written from the experimental world's perspective. A method shipping
in classic DART but not yet in the experimental world is planned, with the
classic location noted in Notes.
Workflow: add or update an entry
- Ground the entry in real evidence — a design doc, code path, test, or an explicit project decision. Do not add aspirational references with no link.
- Write an accurate citation (authors, title, year, venue/publisher). Prefer an official URL; do not fabricate DOIs.
- Add a row to the matching summary table and a detail subsection with the full properties and a one-line rationale.
- Set
Statusfrom the experimental world's perspective; note classic-DART status separately inNotes. - Set
Verdict(adoptto build on,baselineto compare against,referenceto cite,evaluatewhile undecided,rejectwith a reason). - Fill
Where usedwith the design-doc/code/test link. - When the relationship changes (e.g. a
plannedalgorithm becomesimplemented, or anevaluateis decided), updateStatus/Verdictand theWhere usedlink in the same change.
Rules
- Prefer robotics/dynamics literature (textbooks, papers) over engine-specific names when a reference informs a terminology decision; record the grounding in the catalog's "Terminology Grounding" section.
- Keep the catalog scoped to the experimental world for now; the schema is general and can extend to the rest of DART later.
- Keep
engineentries as baselines/comparisons, never as dependencies. - Use
docs/ai/verification.mdto select the docs-only or AI docs/adapters gate set, then runpixi run lintafter edits.
Full Documentation
For the catalog and its rationale: docs/readthedocs/papers.md
For the API it supports: docs/design/simulation_cpp_api.md,
docs/design/simulation_python_api.md
For DART's research focus: docs/ai/north-star.md
Version History
- e0d13fd Current 2026-07-05 10:36


