Lifecycle and context
Design goroutines and request flow around ownership, cancellation, and shutdown.
Every goroutine should have an owner, every timeout should be intentional, and shutdown should be predictable.
Build Go services that stay reliable under load with explicit lifecycle control, stronger concurrency discipline, better observability, and safer failure handling.
Build Go services that stay reliable under load with explicit lifecycle control, stronger concurrency discipline, better observability, and safer failure handling.
Design goroutines and request flow around ownership, cancellation, and shutdown.
Every goroutine should have an owner, every timeout should be intentional, and shutdown should be predictable.
Use errgroup, semaphores, and worker patterns without losing clarity.
Prefer simple coordination, preserve errors, and avoid invisible background work that becomes impossible to operate.
Skill execution is available for signed-in users. Run this skill and keep a history of your results.
No reviews yet. Run this skill and share your experience.