sui-sdks

What problem does it solve?

This Skill prevents incorrect or outdated guidance when users ask which Sui SDK to use, how to migrate between SDK generations, or how to interpret Sui SDK APIs safely without mixing patterns.

Core Features & Use Cases

• Correct SDK selection across languages: Recommends the two official Mysten Labs SDK surfaces (TypeScript @mysten/sui and Rust sui-rust-sdk) while clearly flagging that Python/Go/Dart/Kotlin/Swift/Vue are community-maintained.
• Migration accuracy (v1 to v2): Avoids cross-wiring @mysten/sui.js (v1) and @mysten/sui (v2) by enforcing generation-specific client, transaction, and result-status patterns.
• Version-matched API referencing: Instructs the agent to consult bundled, installed-package LLM docs (e.g., node_modules/@mysten/sui/docs/llms-index.md) instead of guessing or relying on potentially mismatched web docs.
• Cross-SDK portability: Provides side-by-side operation mapping so porting core PTB concepts between TypeScript and Rust is done with the correct API semantics.

Quick Start

Use the sui-sdks skill to determine whether to use the official TypeScript or Rust SDK (or a specific community SDK) and to get a precise migration path if the user is currently on @mysten/sui.js or older TS patterns.