What problem does it solve? Developing ESP-WASMachine firmware requires precise knowledge of WAMR runtime initialization order, Kconfig dependency chains, partition tables, and WASM native API registrations, and mistakes in any of these cause build failures or runtime crashes that are hard to diagnose. ## Core Features & Use Cases - Scenario Recipes: Twelve recipes covering project creation, build/flash, board selection, iwasm execution, App Manager remote management, littleFS packaging, native extensions (libc/HTTP/MQTT/LVGL/RainMaker/Wi-Fi provisioning), Extended VFS, and data_seq serialization. - Grounded API & Kconfig Reference: Every WASM native import signature, host-side API, and WASMACHINE_* Kconfig option is extracted from real esp-wasmachine source, with explicit rules against inventing symbols. - Pitfall Prevention: Twelve WRONG/CORRECT pitfall pairs covering init order, storage flashing, MQTT/App Manager dependency, UART console conflicts, and partition sizing. - Use Case: A developer asks the AI to create an ESP32-S3-BOX project that runs a WASM app with MQTT and LVGL; the skill produces the correct sdkconfig.defaults, app_main init sequence, BSP ops registration, and build/flash commands. ## Quick Start Ask the AI to create a new ESP-WASMachine firmware project for ESP32-S3 that runs a WASM app with the shell and App Manager enabled.