zeus-research-methodology

Guides hypothesis-driven bug investigation and feature lifecycle decisions in the Zeus Lightning wallet.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-research-methodology-aswin-dev-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeus-research-methodology
Source: https://github.com/aswin-dev-debug/Ai-Finance-analyzer/tree/main/lib/zeus-contrib/zeus/.claude/skills/zeus-research-methodology
Command: npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-research-methodology-aswin-dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers working on the Zeus React Native Bitcoin/Lightning wallet often jump from a hunch to a fix without proving the root cause, leading to regressions across 7 node backends and 2 mobile platforms. This Skill enforces a disciplined evidence bar, experiment design, and retirement process so changes are accepted or abandoned with a documented trail. ## Core Features & Use Cases - Evidence Bar Enforcement: Requires one mechanism explaining all observations (including negatives), pre-registered predictions with numeric thresholds, and adversarial refutation by an assigned reviewer before any fix is accepted. - Feature Lifecycle Guidance: Documents the observed idea → default-off flag → default-on → MOD_KEY migration → deprecated-but-retired lifecycle, with worked examples like bimodalPathfinding and lsps1ShowPurchaseButton. - Templates & Checklists: Provides a copy-paste hypothesis/experiment/refutation template, a promotion checklist, and a dead-end archaeology format for documenting abandoned investigations. - Use Case: You suspect the in-flight request dedup cache causes a bug. The Skill walks you through writing predictions before testing, refuting across backends and upgrade paths, and recording the refutation attempts in your PR. ## Quick Start Ask the assistant to apply the Zeus research methodology to structure a hypothesis and experiment plan for the bug you are investigating before writing any fix.

Frequently Asked Questions about zeus-research-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prove a root cause before fixing a bug in a React Native app?

Write down one mechanism that explains all observations including where the bug does not occur, then state concrete predictions with numeric thresholds before running any experiment. Finally, have someone other than the author attempt adversarial refutation across backends, platforms, and upgrade paths.

How to promote an experimental feature flag to a default setting?

Flip the inline default for fresh installs and ship a MOD_KEY migration for existing users, passing a real object to setSettings rather than a JSON string. The change must pass the storage gate with maintainer sign-off and remain revertible as a single unit.

When should I deprecate a feature flag instead of deleting it?

Deprecated flags are retained in users' settings blobs forever and only marked with a deprecated comment, because removing keys is a storage-format change requiring maintainer sign-off. Dead UI is fenced in place with a TODO or tracker reference rather than deleted.

What should I do when a bug investigation hits a dead end?

Stop after two failed hypothesis cycles, when the fix would break a maintainer non-negotiable, or when the bug is tracked upstream. File a dead-end archaeology entry recording observations, refuted hypotheses, evidence, and what new observation would reopen the case.

Does this methodology apply outside the Zeus wallet codebase?

The evidence bar, prediction-first experiment design, and adversarial refutation patterns generalize to any codebase, but the specific lifecycle stages, MOD_KEY migrations, and commit examples are grounded in the Zeus repository's own history.