What problem does it solve?
It prevents build failures and CI breakage when adding, wiring, or debugging Cargo features in crates/xberg, where ORT-dependent features are incompatible with WASM and Android x86_64 targets and aggregate feature sets must stay in parity.
Core Features & Use Cases
- ORT Compatibility Rules: Maps which features (paddle-ocr, layout-detection, embeddings, auto-rotate, formula-recognition) fail on WASM and Android x86_64, and which pure-Rust type-only or tract-based variants replace them.
- Aggregate Feature Sets: Documents the membership of formats, analysis, services, full, no-ort-target, wasm-target, android-target, windows-target, and other curated bundles.
- CI Parity Guard: Explains the check-feature-parity.py script that fails CI when a feature is added to full but not to windows-target.
- Use Case: When adding a new ML feature, consult this Skill to decide whether it needs a tract variant, which aggregate sets must include it, and whether the parity guard will reject the change.
Quick Start
Ask the AI to check whether a new Cargo feature compiles on WASM and Android targets and which aggregate feature sets need updating.