Run build checks, linting, formatting, and tests for the FrogDB project using the Justfile. Handles smart scoping (targeting specific crates based on what changed), sccache troubleshooting, nextest configuration, and all test types (unit, integration, proptest, Shuttle concurrency, Turmoil simulation). Use this skill whenever the user asks to check, lint, format, test, verify, or validate their code changes — even partial requests like "run tests" or "does this compile". Also use when builds fail with sccache errors or test timeouts.
Sync docs with code, update docs, doc drift, are docs up to date, audit documentation, spec is wrong, doc is stale, check documentation, verify specs, docs out of date, after code changes affecting documented behavior.
Manage the self-hosted GitHub Actions runner (rebuild image, restart container, check status/logs, troubleshoot). Use this skill whenever runner config files are modified (.github/runner/Dockerfile, docker-compose.yml), when the user asks about the CI runner, or when CI jobs fail with runner-related errors. Proactively suggest rebuilding when you notice changes to runner configuration during a session.
Manage the FrogDB development server lifecycle: start, restart, and stop. Start the server with continuous low-volume background traffic for testing metrics, debug pages, logs, and observability features. Automatically kills any existing dev server before starting a new one (one instance per worktree). Use when the user asks to start/stop/restart the dev server, run the server for development, test the debug UI, or when you've edited server code and need to restart to pick up changes. Also use after editing HTML/CSS/JS assets under frogdb-server/crates/debug/assets/ since rust-embed bakes them at compile time.
Benchmark FrogDB: standalone load testing (memtier_benchmark), comparative benchmarks against Redis/Valkey/Dragonfly, cluster-mode scaling, Criterion micro-benchmarks, durability mode comparison, and result interpretation with architectural context. Use when the user asks to benchmark, compare performance, run load tests, measure throughput/latency, compare against Redis/Valkey/Dragonfly, run Criterion benchmarks, test different durability modes, or understand why one database outperforms another.
Profile FrogDB performance: CPU sampling (samply), async flamegraphs (tracing-flame), causal profiling (tokio-coz), memory profiling (heaptrack), and always-on metrics (tokio-metrics). Use when the user asks to profile, investigate performance, generate flamegraphs, do causal/memory profiling, or analyze CPU/async hotspots. For benchmarking, load testing, or comparing against Redis/Valkey/Dragonfly, use the `/benchmark` skill instead.
Architectural design and implementation planning for FrogDB. Produces a design rationale and implementation plan written to the plan mode plan file. Invoke for any non-trivial change: new commands, new subsystems, cross-crate feature additions, concurrency changes, persistence changes, protocol changes, replication impacts, or any work touching more than one crate. Also use when the user asks about architecture, component design, request flows, dispatch mechanisms, or tradeoffs. Even for simpler changes like adding a single command, use this skill to ensure the right execution strategy, WAL strategy, and flags are chosen.
Correctness audit for distributed systems, concurrency bugs, replication correctness, failover safety, split-brain, WAL ordering, cross-shard atomicity, consistency violations, race conditions, deadlocks, lost wakeups, linearizability, epoch monotonicity, fencing, VLL lock ordering, channel backpressure, snapshot consistency. Trigger on: "audit", "is this safe", "could this lose data", "does this break linearizability", "correctness check", "race condition", "split-brain", "replication lag", "review for correctness", "distributed systems review", "concurrency review", "is this correct under failure", "what happens if this crashes".