What problem does it solve? Embedded projects often fail because code is written before the hardware configuration, chip constraints, and architecture are validated. This Skill enforces a structured brainstorming phase that confirms the target chip, interface, and controller, checks hard constraints like DMA limits, and produces an approved design spec before any driver code is generated. ## Core Features & Use Cases - Hardware Confirmation Workflow: Asks targeted questions one at a time about chip family (ESP32-S3, STM32F4, RP2040, nRF52), interface type (SPI/I2C/UART), and controller model. - Constraint Identification: Checks chip-specific hard limits such as ESP32-S3 SPI DMA 4092-byte chunks, RP2040 PIO instruction limits, and nRF52 SoftDevice memory. - Design Proposal & Approval Gate: Presents 2-3 architecture approaches with trade-offs and blocks all code generation until the user approves the design. - Spec Persistence: Saves the validated design to docs/embedded/specs/YYYY-MM-DD-<feature>-spec.md and hands off to the embedded-driver-design skill. - Use Case: Before writing an ST7789 display driver for an ESP32-S3, use this Skill to confirm SPI mode, resolution, and DMA constraints, then get an approved architecture plan. ## Quick Start Ask the assistant to brainstorm the hardware design for your embedded project before writing any driver code.
