Use when writing or reviewing shared-memory concurrent code: atomics, lock-free/wait-free data structures, or scalable synchronization. Triggers on prompts about memory ordering (relaxed/acquire/release/seq_cst), CAS/compare-exchange, the ABA problem, SPSC/MPSC/MPMC queues, lock-free stack, hazard pointers / epoch / RCU reclamation, false sharing, spinlocks/backoff, work-stealing, even when the user doesn't say 'lock-free'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xonovex-skill-lock-free:lock-free-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- C11 atomics (`<stdatomic.h>`); audience is a C99/C11 game engine with atomic/thread/job modules.
SOURCES.mdeval-queries.jsonevals.jsonreferences/aba-problem.mdreferences/atomics-and-cas.mdreferences/false-sharing.mdreferences/lock-free-stack.mdreferences/locks-and-backoff.mdreferences/memory-model.mdreferences/memory-ordering.mdreferences/mpmc-bounded-queue.mdreferences/mpsc-queue.mdreferences/progress-guarantees.mdreferences/safe-memory-reclamation.mdreferences/scalable-architecture.mdreferences/spsc-ring-buffer.mdreferences/testing-and-verification.md<stdatomic.h>); audience is a C99/C11 game engine with atomic/thread/job modules.compare_exchange_weak in a loop; reload the expected value on failure, see references/atomics-and-cas.mdvolatile is not atomic and gives no ordering — it never makes concurrent C correct; use _Atomic/atomic_*.compare_exchange_weak may fail spuriously even when the value matches — only ever use it inside a retry loop.seq_cst is the safe default for a first draft but the slowest; relaxing it later requires a proof, not a guess.memory_order_* argument or a fenceGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub xonovex/platform --plugin xonovex-skill-lock-free