sui-build
Skill20 starsChanged 15 days agoApache-2.0View on GitHub
Use this skill when the user needs to build Move code, or when when the user asks about sui move build.
In this repository30 other files it gives its agents.
- accessing-dataSkill
- composable-move-functionsSkill
- deepbook-marginSkill
- deepbook-moveSkill
- deepbook-overviewSkill
- deepbook-predictSkill
- deepbook-sdkSkill
- frontend-appsSkill
- generate-sui-agent-configSkill
- kioskSkill
- modern-move-syntaxSkill
- move-securitySkill
- move-unit-testingSkill
- naming-conventionsSkill
- sui-object-modelSkill
- onchain-randomnessSkill
- ptbsSkill
- sui-bridgeSkill
- sui-clientSkill
- sui-for-ethereumSkill
- sui-installSkill
- sui-move-projectSkill
- sui-moveSkill
- sui-networks-gasSkill
- sui-overviewSkill
- sui-publishSkill
- sui-sdksSkill
- sui-ts-sdk-backendSkill
- walrus-sitesSkill
- zkloginSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
When a package has an [environments] section in Move.toml with multiple networks, use --build-env to target a specific environment:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Building Packages
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.
Building
sui move buildThis 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 flag
When 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 mainnetThis 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 testnetTesting
sui move testKey testing modules
sui::test_scenario— Multi-transaction, multi-sender test scenarios. Simulates realistic transaction flows withbegin,next_tx, andend.std::unit_test— Assertion macros for unit tests (assert_eq!,assert_ne!).
Code coverage
Track which lines your tests exercise:
sui move test --coverageView coverage results for a specific module:
sui move coverage source --module <name>Move Analyzer
Install via suiup:
suiup install move-analyzerThen 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.
Debugging
- Move Trace Debugger: Step-through debugger for Move execution traces with variable inspection.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

