What problem does it solve?
Navigating a large Rust monorepo with 19 workspace members, 3 excluded crates, and 11 distribution packages is error-prone; this Skill explains where code belongs and prevents the common mistakes that break Docker builds and fresh clones when adding a new crate.
Core Features & Use Cases
- Workspace Map: Details every crate under
crates/ (core library, CLI, FFI, JNI, Node, Python, PHP, WASM, PDF engines, OCR backends) plus the two members living under packages/.
- Distribution Package Guide: Explains how each language binding (PyPI, RubyGems, npm, Maven, NuGet, Hex, pub.dev, SwiftPM) connects to the Rust core via FFI, JNI, NAPI-RS, or PyO3.
- New Member Checklist: Covers the
.dockerignore and .gitignore allowlists, Dockerfile COPY lines, and task verify:docker-crates validation required when adding or removing a workspace member.
- Use Case: When adding a new crate to the workspace, follow the checklist to update both ignore files and every Dockerfile, then run the verification task to catch omissions in both directions.
Quick Start
Ask the assistant to explain where a new crate belongs in the Xberg workspace and which ignore files and Dockerfiles must be updated to register it.