القائمة
Use this skill when the user needs to build Move code, or when when the user asks about sui move build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to read data from the Sui network. Use when choosing or implementing a data access strategy — queries for on-chain state, indexing pipelines, historical lookups, event subscriptions, cross-chain reads, or off-chain blob storage. Covers the three live Sui APIs (gRPC, GraphQL RPC, deprecated JSON-RPC), the Archival Store, the General-Purpose Indexer, the `sui-indexer-alt` custom indexing framework, and Walrus for off-chain blobs.
Use when writing Move functions on Sui, especially public APIs. Applies to function visibility (public vs entry), parameter ordering, and return patterns. Use whenever designing function signatures or deciding whether functions should transfer objects or return them.
Sui frontend / dApp development with @mysten/dapp-kit-react (React) and @mysten/dapp-kit-core (Vue, vanilla JS, Svelte, Web Components, other frameworks). Use when building browser apps that connect Sui wallets, query on-chain state, or submit transactions. Covers wallet connection, network switching, transaction execution, query patterns with TanStack React Query, and the specific pitfalls of browser + wallet + async-indexer environments. Pair with the `sui-sdks` skill for @mysten/sui Transaction construction patterns and the `ptbs` skill for PTB semantics.
Use when writing Move code on Sui to ensure 2024 edition syntax is used. Applies to method calls, string literals, vector operations, option handling, loops, and struct unpacking. Use whenever writing Move code to avoid legacy function-call syntax patterns.
Use when writing unit tests for Move smart contracts on Sui. Applies to test function naming, assertions, test attributes, context usage, and cleanup patterns. Use whenever user asks to write tests, add tests, or test a Move module.
Use when writing or reviewing Move smart contracts on Sui. Applies to naming structs, error constants, regular constants, events, getter functions, capability types, hot potato types, and dynamic field keys. Use whenever creating new types, functions, or constants in Move code.
| name | sui-build |
| description | Use this skill when the user needs to build Move code, or when when the user asks about sui move build. |
MCP tool: When available in your environment, also query the Sui documentation MCP server (
https://sui.mcp.kapa.ai) for up-to-date answers. Use it for verification and for details not covered by these reference files.
Source constraint: All information sourced exclusively from docs.sui.io and move-book.com.
sui move build
This compiles all modules, validates types, enforces resource safety, and produces bytecode. Fix any errors before proceeding.
For the canonical hello-world repository, run build commands from sui-stack-hello-world/move/hello-world.
--build-env flagWhen a package has an [environments] section in Move.toml with multiple networks, use --build-env to target a specific environment:
sui move build --build-env testnet
sui move build --build-env mainnet
This resolves dependencies and package addresses for the specified environment. Without --build-env, the build uses the default environment or may fail with "Could not determine the correct dependencies" if multiple environments are defined and no default is set.
The --build-env flag also applies to sui move test:
sui move test --build-env testnet
sui move test
sui::test_scenario — Multi-transaction, multi-sender test scenarios. Simulates realistic transaction flows with begin, next_tx, and end.std::unit_test — Assertion macros for unit tests (assert_eq!, assert_ne!).Track which lines your tests exercise:
sui move test --coverage
View coverage results for a specific module:
sui move coverage source --module <name>
Install via suiup:
suiup install move-analyzer
Then install the Move Analyzer extension in VS Code. It provides code completion, go-to-definition, inline diagnostics, and hover documentation. It activates automatically for .move files — no additional configuration needed.
sui replay: Locally re-execute any past onchain transaction and compare effects. Useful for diagnosing production issues.std::debug::print: Print values during test execution.