embedded-timing-libslisted

# Embedded Timing Libs ## Overview Use this skill for lightweight software timer libraries such as MultiTimer. The agent should confirm tick source, callback context, time units, wraparound behavior, and scheduler frequency before relying on timer callbacks. ## When To Use Use this skill when: - The user wants to add or debug MultiTimer, software timers, timeout lists, periodic callbacks, or one-shot timers. - Timers drift, fire too early/late, stop firing, fire repeatedly, or break across tick overflow. Do not use this skill for hardware PWM/timer peripheral bring-up. Use `embedded-peripheral-bringup` for register-level timer issues. ## First Questions Ask for: - Timer library and target runtime. - Tick source and frequency. - Callback context: main loop, RTOS task, ISR, or scheduler hook. - Time units used by the library and application. - Number of timers and longest expected uptime. - Whether callbacks may start/stop other timers. ## Integration Checklist 1. Confirm tick monotonicity. Timer logic needs a stable increasing timebase or explicit wraparound handling. 1. Match units. Milliseconds, ticks, microseconds, and RTOS ticks must not be mixed silently. 1. Define callback context. Timer callbacks must not block if they run in ISR or scheduler critical context. 1. Test one-shot and periodic behavior. Verify start, stop, restart, and callback ordering. 1. Test wraparound. Use simulated ticks or shortened counters to prove overflow behavior.