orion-error-engineering

What problem does it solve?

This Skill helps you migrate to and apply the orion-error Rust crate correctly so your services produce consistent, structured, and interoperable error boundaries instead of stale or legacy error-handling patterns.

Core Features & Use Cases

• Domain reason modeling and governance: choose stable identities for business variants and keep shared infrastructure categories transparent over UnifiedReason.
• Correct API selection for conversions and sources: decide between to_err(), source_err(), source_raw_err(), with_source(), conv_err(), and interop APIs based on the upstream error type and boundary semantics.
• Diagnostics-to-protocol workflow: use report(), exposure(), and JSON/protocol rendering paths to produce correct machine and human-facing error representations while keeping payloads out of reason values.
• Migration guidance and review heuristics: detect and replace removed/legacy APIs (owe_*, err_wrap, with, etc.) and update old 0.6/0.7-era examples to current 0.8.x practices.

Quick Start

Use this skill to review an existing Rust codebase that uses legacy orion-error error APIs and update it to structured 0.8.x patterns: migrate a failing service that still calls owe_* and map_err wrappers into source_err()/source_raw_err() with correct identities and protocol rendering.