What problem does it solve? Debugging the Zeus Lightning wallet involves recurring, non-obvious failure modes: features that silently no-op on certain backends, settings that vanish after updates, CI checks that fail despite passing locally, and native crashes in embedded LND. This Skill maps each known symptom directly to its first check, likely cause, and fix pattern, eliminating hours of blind investigation. ## Core Features & Use Cases - Symptom-to-Triage Table: Sixteen documented failure modes (silent no-ops, .then is not a function errors, stuck connecting screens, Tor dedup-cache replay, Hermes regex stack overflows, Fabric layout crashes) each paired with discriminating experiments and fix patterns. - Discriminating Experiments: Concrete grep commands and runtime checks to distinguish root causes, such as telling a missing backend method apart from a missing supports*() capability gate. - Provenance & Re-verification: Every cited commit hash and code fact ships with a one-liner command to re-verify it against the current master branch. - Use Case: A developer sees TypeError: x.then is not a function on the LndHub backend. The playbook identifies that BackendUtils.call() returns false synchronously for missing methods, and provides the exact grep commands to confirm and gate the feature correctly. ## Quick Start Ask the assistant to triage your Zeus bug by describing the symptom, for example: my Zeus app is stuck on the connecting screen after the latest update, help me find the cause.
