elodin-syselodin-sys/elodin/.cursor/skills/elodin-dev/SKILL.md

elodin-dev

Skill553 starsChanged 5 months agoApache-2.0View on GitHub

Develop and contribute to the Elodin codebase. Use when building Elodin from source, running tests, modifying core libraries, working on the Rust workspace, or onboarding as a contributor.

Installs packages

In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bevySkill
- branch-regressionSkill
- elodin-alephSkill
- elodin-craneliftSkill
- elodin-dbSkill
- elodin-editor-devSkill
- elodin-headless-captureSkill
- elodin-monte-carloSkill
- elodin-nixSkill
- elodin-simulationSkill
- elodin-tracySkill
- gltf-asset-optimizationSkill
- kdl-to-python-schematicSkill
- nox-py-devSkill
- qa-test-planSkill
- rustSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
All changes must pass these before merge.
line 69
Distinctive:
Always run commands from the repo root.
line 96

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Elodin Development

Elodin is a monorepo for aerospace simulation and flight software. The stack:

nox-py — Python SDK (JAX + PyO3 bindings; includes ECS in src/)
nox — Tensor compiler (→ Cranelift-MLIR / JAX)
Impeller — High-performance pub-sub telemetry protocol
Elodin-DB — Time-series telemetry database
Elodin Editor — 3D viewer and graphing tool (Bevy + Egui)
Roci — Reactive flight software framework
Aleph — NixOS configuration for Jetson Orin flight computers

Architecture

Python Simulations (nox-py)
        │
   ┌────┴────┬──────────────┐
   │         │              │
 NOX      Impeller     Elodin-DB
Compiler  (Telemetry)   (Storage)
   │         │              │
Cranelift/ Stellarator    Elodin
  JAX      (Async RT)     Editor
                │
         ┌──────┴──────┐
       Roci          Aleph
    (Flight SW)   (Hardware)

Key integration points:

nox-py → nox → Cranelift-MLIR (default) or JAX (simulation compilation)
nox-py → impeller → elodin-db (telemetry)
elodin-editor → impeller → elodin-db (visualization)
roci → impeller → elodin-db (flight software telemetry)

Prerequisites

Determinate Systems Nix
Just (brew install just / apt install just)
git-lfs (git lfs install globally)
Arm macOS strongly preferred for build speed

Development Environment

Always work inside the Nix shell. It provides Rust, Python, C/C++ toolchains, cloud tools, and git-lfs.

nix develop                              # Enter unified dev shell
nix develop --command "cargo build"      # One-off command

Build Commands

just install

# Run an example
elodin editor examples/three-body/main.py

CI Checks

All changes must pass these before merge. See ci-checks.md for details.

cargo fmt                                 # Rust formatting
cargo test                                # Rust tests
cargo clippy -- -Dwarnings                # Rust lints (warnings = errors)
ruff format --check && ruff check --fix   # Python formatting + lints
alejandra                                 # Nix formatting

Workspace Structure

The Cargo workspace has 57 members. Key crates by area:

Area	Crates
Simulation	`nox`, `elodin-macros`, `nox-py`, `nox-frames`, `cranelift-mlir`
Database	`db`, `db/cli`, `db/eql`, `db/tests`
Telemetry	`impeller`, `impeller/{bevy,stellar,bbq,frame,kdl,wkt}`
Editor	`elodin-editor`, `apps/elodin`
Runtime	`stellarator`, `stellarator/{buf,macros,maitake}`
Flight SW	`roci`, `roci/{macros,adcs}`
FSW Apps	`serial-bridge`, `mekf`, `msp-osd`, `lqr`, `blackbox`, `gstreamer`, `video-streamer`
Utilities	`wmm`, `s10`, `video-toolbox`

Working from Repository Root

Always run commands from the repo root. This prevents path confusion across the many workspace members and aligns with how CI runs.

Component-Specific Skills

For deeper work on specific areas, see:

Editor: .cursor/skills/elodin-editor-dev/
Python SDK: .cursor/skills/nox-py-dev/
Database: .cursor/skills/elodin-db/
Aleph/NixOS: .cursor/skills/elodin-aleph/
Nix environment: .cursor/skills/elodin-nix/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free