embedded-framework-libs

# Embedded Framework Libs ## Overview Use this skill for framework-style embedded libraries that shape project architecture rather than one feature. Cover PLOOC, Avem, PowerManagement, and similar libraries by focusing on ownership, lifecycle, configuration, coupling, and migration risk. ## When To Use Use this skill when: - The user wants to add or evaluate PLOOC, Avem, PowerManagement, or a similar embedded framework. - The task involves object-oriented C patterns, module architecture, power-management framework integration, lifecycle hooks, or broad project restructuring. - The user is unsure whether a framework is appropriate for a small MCU project. Do not use this skill for small single-purpose utility libraries that can be integrated locally without architecture impact. ## First Questions Ask for: - Library/framework name and source. - Existing project architecture and target MCU/RTOS. - Problem the framework is meant to solve. - Code size, RAM, timing, safety, and team familiarity constraints. - Whether this is greenfield, migration, or partial adoption. ## Integration Checklist 1. Validate need. Confirm the framework solves a real recurring problem and is not added for style alone. 1. Define boundary. Decide which modules use the framework and which remain plain C. 1. Check lifecycle. Init, start, stop, suspend, resume, and deinit order must be explicit. 1. Keep platform hooks isolated. Hardware, RTOS, allocator, timebase, and logging hooks ...