Think of it like this:

This guide consolidates best practices from across the Babysitter ecosystem into a single reference. Whether you are designing workflows, developing processes, optimizing performance, or collaborating with your team, these patterns will help you get the most out of Babysitter.

Breakpoints provide human-in-the-loop approval gates within Babysitter workflows. Use ctx.breakpoint() to pause automated execution at critical decision points, present context to the user, and make informed approvals before proceeding. The call returns a BreakpointResult object containing the reviewer's decision and any feedback provided.

Like setting up an automatic notification: "When the workflow finishes, send me a Slack message." That's a hook.

Every time the AI does something - writes code, runs tests, asks for approval - it gets recorded in the journal. This means:

Think of it like cooking: instead of waiting for the water to boil, THEN chopping vegetables, THEN preheating the oven - you do all three at once. Much faster!

Just like a cooking recipe says "chop vegetables, then cook them, then serve" - a process says "research the codebase, then write tests, then implement, then verify."

<!-- process-library:lead:start -->

Instead of:

Close your laptop, end your session, or even have your computer crash - when you come back, just say "resume" and Babysitter picks up exactly where it left off.