Domain Iot

This is a Layer 3 domain constraints guide that maps IoT realities (unreliable networks, power limits, physical security risks) directly to Rust design decisions. You get constraint tables showing why offline-first matters, when to use no_std versus tokio, and how to think about MQTT QoS levels in terms of battery life. The trace-down approach is helpful: it connects "network can fail" to actual crate choices like rumqttc with exponential backoff. Covers both Linux gateways and MCU devices, which is the right scope since IoT spans that range. The common mistakes table is honest about what kills devices in production (always-on radios, no local buffering). Use this when you need to justify architectural choices for connected devices, not just implement MQTT.

Install to Claude Code

npx -y skills add actionbook/rust-skills --skill domain-iot --agent claude-code