Use this skill as a map to the owning code and contract. Let current code, payloads, and runtime behavior decide implementation details.
Quick Start
- Reproduce the real entry and affected platform.
- Trace
entry -> selection -> quote -> review -> execution -> history/status. - Identify the first owner whose state or contract is wrong; inspect adjacent consumers before editing.
- Preserve the trade identity across async boundaries, make the smallest owner-correct change, and verify the same user path.
Find The Owner
| Task | Start here | Read next |
|---|---|---|
| Swap selection, quote, review, or send | Swap state/actions, view hooks, background service | Architecture, Code map |
| Wallet, Send, Earn, Buy, or Market handoff | Source params, then settled Swap state | Architecture |
| Bridge, Limit, Stock, privacy, or provider work | Capability, payload, and lifecycle adapter | Provider contracts |
| Cold start, default asset, tab, or first-frame issue | Route seed, persisted display state, readiness | Architecture |
| Pending, history, status, restart, or repair | Persistent owner and status source | Provider contracts |
| Receive-only filtering | Receive and AssetSelector before any Swap handoff | Code map |
Load Detail As Needed
- Architecture explains the execution spine, handoff ownership, runtime boundaries, and cold-start model.
- Code map gives stable directories and useful search anchors.
- Provider contracts covers channels whose quote, settlement, or persistence semantics differ from an ordinary swap.
- Validation helps choose focused tests and runtime evidence for the changed layer.
Finish
State the entry, first wrong owner, and identities that matter. Run nearby tests and the repository-required checks, then prove the affected route and payload on the owning platform. Report any runtime or provider evidence you could not get.
Related skills: $1k-perps-module, $1k-tradingview-communication,
$1k-state-management, $1k-cross-platform, $1k-defi-module-integration.