thinking-in-boc Skill

Source

• Creator: microsoft
• Repository: microsoft/bocpy
• Skill file: .github/skills/thinking-in-boc/SKILL.md

What it does

Think in Behavior-Oriented Concurrency, not threads-and-locks. Use when: writing or reviewing any bocpy code (library, examples, tests), about to reach for time.sleep / threading.Event / atomic counters / polling loops / waitfor helpers, designing how a downstream behavior observes an upstream one, scheduling work to r

Skill instructions

Thinking in Behavior-Oriented Concurrency This skill is a corrective. The default reflex when synchronizing concurrent work is to reach for threads-and-locks primitives: shared state, a mutex, a condition variable, a busy-wait loop, an atomic counter, an event flag, a Future. In BOC, those answers are almost always wrong — not because they break, but because they bypass the very mechanism that makes BOC safe and fast. The BOC question is not "what synchronization primitive do I need here?" It is: "what cown is this work ordered against, and what behavior should run when that cown is free?" Read this skill any time you catch yourself writing one of the smells below. The smells If you find yourself typing any of these inside, or in code that interacts with, a BOC program — stop and re-derive the design. | Smell | What you almost certainly meant | |-------|---------------------------------| | time.sleep(...) in a polling loop | Schedule a behavior on the cown the predicate depends on. | |