embedded-library-entry

# Embedded Library Entry ## Overview Use this skill as the entry point for MCU library integration work. Classify the library type, target platform, runtime model, resource limits, and required porting layer before routing to a specific library skill. ## When To Use Use this skill when: - The user wants to add, port, configure, or debug an embedded C library. - The task involves MCU storage, logging, crash diagnosis, shell commands, filesystems, protocol stacks, UI, parsers, buttons, timers, queues, or state machines. - The target may be bare metal, RTOS-based, or resource-constrained. Do not use this skill when the problem is only board bring-up, flashing, serial logs, or architecture faults. Use the embedded debug skills first. ## First Questions Ask only what is needed to route: - Library name and version or source repository. - Target MCU/SoC, compiler, and build system. - Runtime model: bare metal, FreeRTOS, RT-Thread, Zephyr, Linux, or unknown. - Memory/storage resources: RAM, flash, block device, filesystem, heap, stack, and whether dynamic allocation is allowed. - Existing porting layer: file I/O, flash driver, UART, timebase, mutex, malloc, display, network, or shell transport. - Current task: first integration, compile error, link error, runtime failure, performance issue, or data corruption. ## Routing Guide **Storage & Filesystem** | Library or task | Prefer | | --- | --- | | littlefs filesystem or block device | `littlefs-integration` | | FatFs disk I...