embedded-framework

name	embedded-framework
description	Universal Embedded Knowledge Framework for AI Coding Agents - recognizes embedded frameworks, maps domains, and applies native-first patterns
trigger	**/*.c, **/*.h, **/*.cpp, **/*.ino, **/*.py, **/*.md

Universal Embedded Knowledge Framework

Core Rules (loaded from ../../..)

When working on embedded projects, follow these rules:

1. Domain-First - Identify running domains before writing code
2. Native-First - Use framework's native APIs, not cross-framework abstractions
3. Clear Boundaries - Define communication protocols between domains

Environment Variables

EMBEDDED_SKILLPACK_DIR=../../..

Framework Recognition

Indicator	Framework
uORB/, msg/, px4_add_module	PX4
apps/, frameworks/, Kconfig	openvela / NuttX
xTaskCreate, FreeRTOSConfig.h	FreeRTOS
rt_device, SConscript	RT-Thread
dts/, west.yml, Kconfig	Zephyr
sdkconfig, main/	ESP-IDF

Example Commands

1. Analyze project structure:

   find . -name "*.c" -o -name "*.h" | head -20 && ls -la
   

2. Identify framework and domains:

   grep -r "xTaskCreate\|FreeRTOSConfig" . 2>/dev/null || \
   grep -r "uORB\|px4_add_module" . 2>/dev/null || \
   grep -r "rt_device\|rt_thread" . 2>/dev/null
   

3. Check for middleware/config files:

   ls *.cfg *.config Kconfig sdkconfig 2>/dev/null; \
   find . -name "Kconfig" -o -name "CMakeLists.txt" | head -10
   

Activation Context

Load this skill when:

• Working on MCU/embedded projects (*.c, *.h, *.cpp, *.ino)
• Analyzing project structure for framework identification
• Writing embedded firmware or drivers
• Debugging embedded systems issues