@senpi/runtime 3.0.81 → 3.0.83

package/skills/senpi-widgets/SKILL.md

@@ -1,167 +0,0 @@
----
-name: senpi-widgets
-description: "Use the show_widget tool to render a native Senpi card in the chat instead of describing a flow in text. Use when the user has no funds, cannot open a trade for lack of balance, asks how to deposit, add money, fund their wallet, fund or top up a strategy — and whenever you are about to explain a Senpi flow that the app already has a screen for. Triggers on: fund wallet, add funds, deposit, no balance, insufficient balance, how do I put money in, top up, fund my strategy, strategy has no margin, show widget, show card, funding card."
----
-
-# Senpi widgets
-
-The Senpi web and mobile clients render cards from the `show_widget` tool call.
-Calling the tool puts a real, working card in the conversation. It is not a
-picture and not a description — the card's own button drives the product flow.
-
-## The one tool
-
-```
-show_widget(widget_type, <fields for that type>)
-```
-
-`widget_type` is an enum. Pass only the fields the tool description lists for
-that type; anything else is rejected.
-
-## Two wallets, two widgets
-
-There are two different wallets, and they are funded in two different ways.
-
-| | User wallet | Strategy wallet |
-|---|---|---|
-| Whose | The user's own Senpi (self-custody) wallet | One wallet per strategy |
-| How it is funded | External deposit — USDC sent to an address | Internal transfer from the user's own wallet |
-| Widget | `fund_user_wallet` | `fund_strategy_wallet` |
-
-Pick by the wallet the money is going *into*. If the user has no money in Senpi
-at all, that is `fund_user_wallet` — a strategy cannot be funded from an empty
-wallet.
-
-## Widget types
-
-### `fund_user_wallet`
-
-The card explains that Senpi wallets are self-custody and its button opens the
-deposit screen for the user's own wallet.
-
-Use it when:
-
-- the user has no balance, or too little balance to open the trade they asked for
-- the user asks how to deposit, add funds, or top up
-- you are about to explain the deposit flow in prose
-
-Fields:
-
-| Field | Required | Notes |
-|---|---|---|
-| `widget_type` | yes | `"fund_user_wallet"` |
-| `reason` | no | One plain sentence on why you are showing the card. Not displayed — the card owns its copy. Omit it rather than passing an empty string. |
-
-Worked example — the user says *"open a 5x long on HYPE"* and the account has
-no balance:
-
-```
-show_widget({
-  widget_type: "fund_user_wallet",
-  reason: "Your wallet needs a balance before this trade can open."
-})
-```
-
-Then answer in prose, for example: "Add funds from the card above and I'll open
-the 5x HYPE long straight after."
-
-Do not pass an address to this widget. The card resolves the user's own wallet
-from their session, and an address is rejected.
-
-### `fund_strategy_wallet`
-
-The card's button moves money from the user's own Senpi wallet into one of their
-strategies. It is an internal transfer, so no address is ever shown or needed by
-the user.
-
-Use it when:
-
-- a strategy is out of margin, or too small to take the trade the user wants
-- the user asks to fund, top up or add to a named strategy
-- you are about to explain how to move money into a strategy in prose
-
-Fields:
-
-| Field | Required | Notes |
-|---|---|---|
-| `widget_type` | yes | `"fund_strategy_wallet"` |
-| `strategy_wallet` | yes | The `strategyWalletAddress` of one of the user's **ACTIVE** strategies. Get it from `strategy_list`; never from memory or from the user's typing. |
-| `tracking_id` | yes | A fresh UUID **you** generate for this one funding request. 8-128 characters, letters/digits/`.`/`_`/`-` only. |
-| `reason` | no | One plain sentence on why you are showing the card. Not displayed. |
-
-Worked example — the user says *"put another $200 into my HYPE momentum
-strategy"*. First call `strategy_list` to get that strategy's
-`strategyWalletAddress`, then:
-
-```
-show_widget({
-  widget_type: "fund_strategy_wallet",
-  strategy_wallet: "0x1111111111111111111111111111111111111111",
-  tracking_id: "0d2f4a1c-3b7e-4f0a-9c11-6ad2e5b8c701",
-  reason: "The user wants to add $200 to this strategy."
-})
-```
-
-The user chooses the amount on the card. Do not put an amount in the call.
-
-## House rules
-
-**Show a card once per turn.** After the tool returns, the card is on screen.
-Answer every follow-up in text. Calling `show_widget` again in the same turn
-stacks duplicate cards in the transcript.
-
-**Never write a deposit address, QR code or network list in text.** The card and
-the deposit screen own those. A pasted address in chat is a phishing surface and
-can go stale.
-
-**Never give a deposit address for a strategy wallet — there is no such thing.**
-USDC sent straight to a strategy wallet skips Senpi's accounting, corrupts the
-strategy's PnL and may be unrecoverable. Funding a strategy is only ever the
-`fund_strategy_wallet` card. If a user asks where to send funds for a strategy,
-tell them it is an internal transfer and show the card.
-
-**Generate a new `tracking_id` for every `fund_strategy_wallet` call.** It is the
-idempotency key for the top-up. Reusing one from an earlier card replays that
-first top-up: the amount is whatever the user typed the first time, and nothing
-new is transferred. Never copy a tracking id out of the conversation.
-
-**Correct numbers when you talk about deposits in prose:** for a deposit into the
-user's own wallet the minimum is $10, and most traders start with $100-250. Do
-not invent other figures — the deposit card's own copy uses these. These are
-deposit figures; do not quote them for a strategy top-up.
-
-**Do not claim the deposit landed.** The tool result only says the card was
-shown. Wait for the user to say so, or for the client's own "I've funded my
-wallet" message, before acting as though there is a balance.
-
-**Do not ask the user to confirm before showing a card.** Showing it costs
-nothing and authorizes nothing.
-
-## When the tool returns an error
-
-The error names the exact fields that were wrong: missing, invalid, or
-unexpected. Fix those fields and call `show_widget` again. Keep the same
-`widget_type` unless the error itself names a different one. Dropping the call
-and describing the flow in prose instead is the wrong recovery.
-
-- `unexpected fields: amount` — that widget takes no amount. Remove the field.
-- `invalid fields: reason (must be a non-empty string; omit it instead)` — drop
-  `reason` entirely, or pass a real sentence.
-- `unknown widget_type "..."` — the message lists the available types. Pick one
-  of those; do not invent a name.
-- `... is not one of your strategy wallets` — call `strategy_list` and use a
-  `strategyWalletAddress` from it. Do not retry the same address.
-- `whose status is PAUSED, not ACTIVE` — only a live strategy can be funded. Tell
-  the user, or pass a different strategy's wallet.
-- `it takes no address` on `fund_user_wallet` — drop `strategy_wallet`, or switch
-  to `fund_strategy_wallet` if the money is meant for a strategy.
-- `tracking_id must be 8-128 characters ...` — generate a fresh UUID and call
-  again with everything else unchanged.
-
-**"could not be verified — the Senpi backend did not answer"** is different from
-every error above: nothing was found wrong with your call. Retry the *same* call,
-tracking id included — no card rendered, so that id is still unused. Do not swap
-the address, and do not tell the user their strategy does not exist.
-
-If a widget type is reported as not enabled on this deployment, do not retry it.
-Handle the request in prose instead.