What problem does it solve? Writing ESP RainMaker firmware requires strict initialization ordering, correct claiming configuration per chip, and exact API signatures; mistakes cause cloud desync, failed claiming, or dropped MQTT messages. This Skill grounds every generated line in the real esp-rainmaker repository headers, Kconfig, and official examples so no API is invented. ## Core Features & Use Cases - Scenario Recipes: 14 step-by-step recipes covering node creation, claiming/provisioning, custom and standard devices, OTA, scheduling, scenes, local control, MQTT budgeting, Ethernet, controller nodes, Zigbee gateway, and Thread Border Router. - Verified References: Real function signatures from esp_rmaker headers, a full CONFIG_ESP_RMAKER_* Kconfig table, 20+ pitfalls with wrong/correct code pairs, and an index of all official examples. - Use Case: Ask for a RainMaker light with brightness and hue plus OTA and scheduling, and receive a complete app_main.c with correct init order, write callback with parameter write-back, and matching sdkconfig.defaults. ## Quick Start Ask the agent to create an ESP RainMaker switch firmware project for ESP32-S3 with OTA and scheduling enabled.