platformio-mcp

Run the common ESP32 workflow in PlatformIO: build, flash, monitor, diagnose, patch, and retry. Use for ESP32/ESP8266/ESP32-S3/ESP32-C3 projects using Arduino or ESP-IDF.

Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.

Validate firmware behavior on real hardware rather than compilation-only checks. Use when running physical acceptance tests, confirming boot markers, validating sensor output, or checking runtime timing/telemetry.

Diagnose and fix PlatformIO build, upload, and configuration failures. Use when resolving compiler errors, missing libraries, platformio.ini issues, memory overflows, port conflicts, permission errors, or failed uploads.

Deploy and validate services on single-board computers such as Raspberry Pi, Jetson, Orange Pi, BeagleBone, and Coral. Use when checking SSH connectivity, runtime dependencies, logs, service health, Docker workloads, or systemd deployment.

Diagnose embedded runtime behavior through serial logs after build/upload. Use when investigating boot loops, crashes, watchdog resets, panic output, missing boot markers, peripheral initialization issues, or silent serial sessions.

Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption. Invoke for STM32, ESP32, FreeRTOS, bare-metal, power optimization, real-time systems.

The absolute Single Source of Truth for executing PlatformIO operations via the MCP Server (compiling, flashing, log-reading, uploading filesystems, managing libraries, testing, and queue locking). Agents MUST route all hardware executions through this skill. Use this to actively solve 'Resource busy' errors, macOS ESP32 port drift/anomalies, invoke esptool.py to clear corrupted flash memory, or configure hardware-less target simulators. Do NOT trigger this skill for general code editing, simply writing text into a platformio.ini file, or querying general macOS/Docker host analytics.

Consistently and thoroughly document TypeScript/Node code following the project's "house style". Use this skill whenever documenting, refactoring, or creating new TypeScript modules to ensure they meet the specific JSDoc, method, and naming standards. Also use this skill whenever drafting or reviewing an implementation plan to ensure it adheres to the project structure.