If you're still using setTimeout in tests and wondering why they're flaky in CI, this is the fix. Instead of guessing how long something takes with arbitrary delays, you wait for the actual condition you need: an element appears, an API responds, state updates. The skill includes a decision tree for when to use condition-based waiting versus hardcoded delays (spoiler: almost always use conditions unless you're literally testing timing behavior). It's basic stuff but the kind of basic that stops tests from failing randomly when your build server is under load. Part of bobmatnyc's MPM skills collection, which has a decent following at 49 GitHub stars.
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill condition-based-waiting