backend-distributed-locking
Installation
SKILL.md
Backend Distributed Locking
Purpose
Coordinate access to shared resources across multiple service instances using distributed locks with guaranteed safety properties.
Agent Protocol
Trigger
Exact user phrases: "distributed lock", "Redis lock", "Redlock", "ZooKeeper lock", "advisory lock", "PostgreSQL lock", "pg_advisory_lock", "lease", "distributed mutex", "fencing token", "lock timeout".
Input Context
- Resource being protected.
- Available infrastructure (Redis, PostgreSQL, ZooKeeper, etcd).
- Number of competing instances.
- Duration of the critical section.
Output Artifact
Lock configuration or implementation code. No file unless requested.