esp-idf-integration

# ESP-IDF Integration ## Overview Use this skill to debug ESP-IDF by separating project configuration, components, partition table, bootloader, flash settings, FreeRTOS behavior, and subsystem logs. ESP-IDF failures are often visible in `sdkconfig` or boot logs. ## When To Use Use this skill when: - The user is working with ESP-IDF, `idf.py`, ESP32-family SoCs, components, or managed components. - The issue involves `sdkconfig`, partition tables, NVS, Wi-Fi, BLE, OTA, flash mode/size, bootloader logs, heap, tasks, or peripheral drivers. - The project differs between menuconfig, CMake components, and runtime logs. Do not use this skill for generic FreeRTOS kernel bugs with no ESP-IDF surface. Use `freertos-kernel-debug` instead. ## First Questions Ask for: - ESP-IDF version, target chip, module/board, toolchain, and `idf.py` command. - `sdkconfig`, partition table, component layout, and dependency manifest. - Boot log from reset through app start, including flash mode/size and reset reason. - Subsystem involved: Wi-Fi, BLE, NVS, OTA, filesystem, peripheral, or power. - Current error code, log tag, panic dump, heap info, or task snapshot. ## Debug Workflow 1. Reproduce the build and target. Confirm `IDF_TARGET`, `idf.py set-target`, clean build, flash, and monitor. 1. Inspect boot evidence. Read reset reason, bootloader version, flash parameters, partition table, and app image selection. 1. Verify configuration. Check `sdkconfig`, Kconfig options,...