sui-dev
01Skill Claude CodeCodex
Full-stack Sui blockchain development — Move smart contracts, TypeScript SDK, and frontend dApp Kit. Routes to the appropriate sub-skill based on what the user is building.
Skill Claude CodeCodex
Full-stack Sui blockchain development — Move smart contracts, TypeScript SDK, and frontend dApp Kit. Routes to the appropriate sub-skill based on what the user is building.
Skill Claude CodeCodex
Move smart contract development on Sui. Use when writing, reviewing, or debugging Move code, Move.toml configuration, or Sui object model patterns.
Skill Claude CodeCodex
Sui object model — struct declarations, abilities (key/store/copy/drop), object ownership, naming conventions, and dynamic fields.
Skill Claude CodeCodex
Move design patterns — events, error handling, one-time witness (OTW), capability pattern, and pure functions/composability.
Skill Claude CodeCodex
Move package setup (Move.toml, edition, dependencies), building, testing, and common pitfalls from other Move dialects.
Skill Claude CodeCodex
Common Sui Move standard library patterns — strings, Coin/Balance, Option, addresses, UID, TxContext, vectors, and struct unpacking.
Skill Claude CodeCodex
Move language syntax — module layout, imports, mutability, visibility, method syntax, enums, macros, and comments.
Skill Claude CodeCodex
Sui frontend dApp development with @mysten/dapp-kit-react (React) and @mysten/dapp-kit-core (Vue, vanilla JS, other frameworks). Use when building browser apps that connect to Sui wallets, query on-chain data, or execute transactions. Use alongside the sui-ts-sdk skill for PTB construction patterns.
Skill Claude CodeCodex
Sui TypeScript SDK — PTB construction, client setup, transaction execution, and on-chain queries. Use when writing code that interacts with the Sui blockchain via @mysten/sui. These patterns apply in both backend scripts and frontend apps. For frontend-specific setup (dApp Kit, wallet adapters, React hooks), use the…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: