by Matt Corbett
Digital-twin engineering team — agents (digital-twin-architect, twin-integration-engineer) for the layer answering 'what should this twin MODEL, at what FIDELITY, and does it MATCH the real asset?': twin taxonomy (asset vs process vs system-of-systems; descriptive/predictive/prescriptive; digital-shadow vs true bidirectional), only-as-much-fidelity-as-the-decision-needs, modeling approach (physics vs data-driven/surrogate/reduced-order vs hybrid), telemetry ingestion (MQTT/OPC-UA/Kafka, edge vs cloud), state sync/drift/calibration, simulation & what-if, and fidelity validation. Fluent in DTDL + Azure Digital Twins, ISO 23247, AAS, Eclipse Ditto, NVIDIA Omniverse, Unity/Unreal, Bentley/Siemens. skills, a knowledge bank (decision tree + 2026 patterns), and templates. Distinct from embedded-iot-engineering (device firmware), robotics-autonomous-systems-engineering (robot control/autonomy), and data-platform (BI/warehouse). Requires ravenclaude-core@>=0.7.0.
Claude Code3 Skills