Use this skill as a map to the owning surface and service contract. Derive product behavior from current code, server data, and the real runtime.
Quick Start
- Reproduce the real entry and affected platform.
- Trace
entry -> data/position -> action -> transaction -> status -> refresh. - Find the first owner whose identity, capability, or transition is wrong.
- Reuse a nearby pattern only when its protocol and operation semantics match; then verify the changed path and a relevant sibling.
Find The Owner
| Task | Start here | Read next |
|---|---|---|
| Earn home, list, recommendation, or detail | Earn view/state and its service request | Architecture, Code map |
| Borrow, staking, claim, withdraw, repay, or status | Operation owner and current service contract | Operation flow |
| Portfolio position or action | Position data, supported action, transaction builder | Portfolio actions |
| Native route, modal, event, or account switch | Discovery host and runtime owner | Architecture |
| External protocol website | Discovery/browser until an App-owned RPC begins | Architecture |
| Funding handoff to Swap | DeFi prefill before quote; Swap execution afterward | $1k-trade-swap-market |
Load Detail As Needed
- Architecture explains surfaces, hosts, runtimes, and cross-module boundaries.
- Code map gives stable directories and search anchors.
- Operation flow covers operation identity, setup, transaction, status, and refresh.
- Portfolio actions covers how visible positions, supported actions, and transaction building join.
- Validation helps choose focused tests and runtime evidence for the changed layer.
Finish
State the owning surface/service and the identities that matter. Run nearby tests and repository-required checks, then prove the affected route reaches the intended terminal and refresh state. Report unavailable runtime or server proof.
Related skills: $1k-trade-swap-market, $1k-state-management,
$1k-cross-platform, $1k-coding-patterns.