Injective (wallet-sdk-core granular skill)

Granular skill for InjectiveWalletProvider — the low-level Injective wallet for backend / Node / non-React flows. Source-of-truth reference lives in the parent broad skill's knowledge tree; this file is the focused workflow only.

Step 1 — Clarify with user before coding

1. New code or v1 → v2 port? New → § Integration. Port v1 → § Migration (almost always a no-op here).
2. Secret (key/mnemonic) or browser-extension config? Injective discriminates by field presence, but the credential variant is SecretInjectiveWalletConfig: { secret: { privateKey } | { mnemonics }, chainId, network }; browser-extension = { msgBroadcaster }. The credential is nested under secret — there is no top-level privateKey.
3. Account state correct? Override defaults.sequence / defaults.accountNumber when the on-chain account differs from the zero defaults (else broadcasting fails with "incorrect account sequence").

Integration workflow (new v2 code)

1. ../integration/knowledge/ai-rules.md — DO / DON'T (read first).
2. ../integration/knowledge/architecture.md — BaseWalletProvider, dual-config discriminants, shallow defaults merge, library-exports.
3. ../integration/knowledge/features/injective.md — full config union, InjectiveWalletDefaults, methods (getRawTransaction / execute), gotchas.
4. Setup recipe → ../integration/knowledge/recipes/setup-private-key.md or ../integration/knowledge/recipes/setup-browser-extension.md; then ../integration/knowledge/recipes/sign-and-broadcast.md, ../integration/knowledge/recipes/defaults-and-overrides.md.
5. Lookups → ../integration/knowledge/reference/provider-classes.md, interfaces.md, chain-support.md.

Injective-specific anti-patterns