Skip to main content
skill CX Codex

sui-for-ethereum — Claude Code skill: migration to Sui Move

The sui-for-ethereum Claude Code skill explains how Sui Move differs from Ethereum and Solidity. It activates for pattern comparisons, token mappings, and contract migration questions.

Apache-2.0 159 installs ★ 25 updated 2026-11-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add MystenLabs/skills --skill sui-for-ethereum -a claude-code
Open on GitHub

What sui-for-ethereum does

The skill maps familiar Ethereum concepts to Sui Move. It explains the shift from accounts to objects, how data is stored, and how access control works. Move keeps data in objects separate from the package that holds the logic.

For specific comparisons, patterns.md covers ERC-20, ERC-721, and ERC-1155 mappings, along with ownership, upgrades, and composability. It also explains programmable transaction blocks (PTBs), which bundle contract calls into one atomic transaction, with up to 1,024 calls. Move has no inheritance or dynamic dispatch, unlike Solidity.

What it helps with

  • compare Ethereum accounts with Sui objects
  • map ERC-20 and ERC-721 to Sui standards
  • understand capability-based access in Sui
  • compare contract upgrade patterns in Solidity and Move
  • bundle contract calls into an atomic PTB

Example prompts for the agent

  • Compare how Solidity and Sui Move store data.
  • Which Sui standards map to ERC-20 and ERC-721?
  • Explain capability-based access versus Ownable in Sui.

How to install sui-for-ethereum

1Skills CLI (Vercel)

npx skills add MystenLabs/skills --skill sui-for-ethereum -a claude-code

2Manually: put the files in place

~/.claude/skills/sui-for-ethereum/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/sui-for-ethereum/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about sui-for-ethereum

How do I install sui-for-ethereum in Claude Code?

Run npx skills add MystenLabs/skills --skill sui-for-ethereum -a claude-code. The skill file is at ~/.claude/skills/sui-for-ethereum/SKILL.md.

What does sui-for-ethereum do?

It explains differences between Ethereum/EVM/Solidity and Sui Move, including their data models, access patterns, token standards, and contract upgrades.

How does the skill explain atomic calls in Sui?

It covers PTBs, which combine contract calls into a single atomic transaction. A PTB can contain up to 1,024 calls.

Source text

SKILL.md · Apache-2.0
---
name: sui-for-ethereum
description: >
  Migrating from Ethereum/EVM/Solidity to Sui Move. Use when the user is an
  Ethereum developer learning Sui, comparing Solidity patterns to Move equivalents,
  asking about differences between EVM and MoveVM, mapping Ethereum token standards
  to Sui standards, or translating access control, state storage, contract upgrade,
  or composability patterns from Ethereum to Sui.
---

# Sui for Ethereum Developers

> **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 in this skill is sourced exclusively from [docs.sui.io/getting-started/sui-for-ethereum](https://docs.sui.io/getting-started/sui-for-ethereum). When extending or updating this skill, only pull from this source. Do not use third-party blogs, tutorials, or unofficial documentation.

This skill helps Ethereum/EVM/Solidity developers understand how Sui Move differs from the patterns they already know. It covers conceptual model shifts, pattern mappings, and concrete comparisons between the two ecosystems.

---

## Reference files

### patterns — Pattern Mappings and Comparisons
**Path:** `patterns.md`
**Load when:** the user asks about specific Ethereum-to-Sui pattern mappings, token standard equivalents, technical comparisons (signatures, consensus, VM), access control differences, data storage differences, contract upgrade approaches, or composability differences.
**Covers:** account vs object model, data storage, inheritance and polymorphism, asset accessibility, access control patterns (with Move capability example), contract upgrades, development environment, state mutation, object model fundamentals, object ownership types, mutating objects, PTBs, standards mapping (ERC-20/ERC-721/ERC-1155 to Sui equivalents), and full technical comparison table.

---

## Routing guide

| Task | Load |
|------|------|
| High-level "what is different about Sui vs Ethereum" | SKILL.md only |
| Specific pattern mapping (access control, storage, tokens) | patterns |
| Token standard equivalents (ERC-20, ERC-721, ERC-1155) | patterns |
| Technical comparisons (signatures, consensus, VM, execution) | patterns |
| How PTBs replace multi-transaction workflows | patterns |
| Contract upgrade differences | patterns |
| Capability-based vs role-based access control | patterns |

---

## Core conceptual shifts

### Programming language
Sui uses Move; the EVM uses Solidity. Move enforces resource safety at both compile time and through bytecode verification. Objects cannot be duplicated or silently dropped. Solidity relies on the EVM for runtime safety.

### Account-centric vs object-centric
Ethereum uses an account-centric model. Solidity implements custom ownership logic within contracts using mappings. Only Ethereum's native currency (ETH) is a first-class citizen with global APIs. Sui uses an object-centric model. Object ownership is inherent to the protocol. Objects are first-class citizens encompassing everything owned on Sui. Any currency on Sui has the same properties as SUI.

### Data storage
In Solidity, data is stored in the smart contract. In Move, data is stored in Move objects. Logic is defined in the contract (package), but the data lives in objects separate from the contract itself. Object behavior (creation, modification, ownership, and deletion) is defined by a package.

### Object model fundamentals
Objects store data in Move and everything in Move is an object. This includes smart contracts (Move packages), onchain addresses, coins, and NFTs.

### Object ownership
- **Address-owned objects:** Single address ownership. Transferable without smart contract interaction.
- **Shared objects:** Publicly accessible objects anyone can use.

### Programmable transaction blocks (PTBs)
PTBs give builders the ability to chain contract calls together with atomicity guarantees during runtime. A Sui PTB can have up to 1,024 different contract calls. This replaces the pattern in Ethereum where each call is its own transaction and is not atomic.

---

## Rules

- Always frame migration advice around the shift from account-centric to object-centric thinking.
- When comparing access control, emphasize that Sui uses capability-based access control through owned objects, not identity/role-based access control through Ownable or AccessControl contracts.
- When discussing token standards, map ERC-20 and ERC-721 to the Sui Currency Standard and Closed-Loop Token. Do not invent Sui equivalents for standards not covered in the source material.
- When discussing contract upgrades, explain that Sui requires layout compatibility, not proxy contracts.
- When discussing composability, emphasize PTBs as the mechanism for atomic multi-call transactions.
- Do not describe Sui as "just another EVM chain." The programming model is fundamentally different.
- Do not invent information beyond what is provided in the source material from docs.sui.io/getting-started/sui-for-ethereum.

## Common mistakes

- **Assuming Solidity inheritance patterns work in Move.** Move has no interfaces, no polymorphism, and no dynamic dispatch. It uses composition through module imports and generics (`Type<T>`) instead.
- **Assuming only role-based access control works.** Sui can implement role-based access control, but the idiomatic pattern is capability-based access through owned objects (e.g., `AdminCap`). Capabilities cheaply objectify ownership transfer rules.
- **Thinking data is stored in the contract like Solidity.** In Sui, logic lives in the contract (package) but data lives in Move objects.
- **Expecting proxy-based contract upgrades.** Sui can have proxy-like patterns, but they must operate on the same object types across upgrades. Layout compatibility is required — new contracts must be layout-compatible with the old one. Upgrades are controlled through `UpgradeCap`.
- **Treating each Move function call as a separate transaction.** Use PTBs to chain up to 1,024 contract calls into a single atomic transaction.
- **Assuming tokens are bound to a smart contract like in Solidity.** On Sui, anyone can access shared objects, and owned objects are directly accessible by their owner without going through a contract.

© MystenLabs · Apache-2.0 · MystenLabs/skills

Similar skills

All skills for Programming languages →

From the same set30

The whole set →
deepbook-margin The deepbook-margin Claude Code skill explains margin trading on DeepBook on Sui. It covers borrowed positions, collateral, risk ratios, and liquidation. CX Codex +1 181installs deepbook-move The deepbook-move Claude Code skill guides Move contract work with DeepBook V3. It covers pools, orders, swaps, flash loans, and BalanceManager permissions. CX Codex +1 181installs deepbook-predict This Claude Code skill covers DeepBook Predict integration for prediction markets on Sui. It explains position creation, settlement, and the liquidity pool. CX Codex +1 181installs sui-ts-sdk-backend The sui-ts-sdk-backend Claude Code skill covers backend services and agents that interact with Sui through the TypeScript SDK. It is invoked for client setup, transaction signing, package publishing, and high-throughput execution. CX Codex +1 167installs zklogin Explains zkLogin and guides its integration into Sui apps. It activates for questions about OpenID providers, address derivation, session lifetime, or security. CX Codex +1 164installs kiosk This Claude Code skill supports writing, reviewing, and debugging Move code for Sui Kiosk. It covers asset trading, NFT listings, TransferPolicy, and Kiosk extensions. CX Codex +1 162installs onchain-randomness Guides onchain randomness implementation in Sui Move. Secures functions using the 0x8 Random object against composition and PTB attacks. CX Codex +1 162installs sui-bridge This Claude Code skill explains Sui Bridge and answers questions about transfers between Sui and Ethereum. It activates for queries about supported assets, limits, finality, or validator governance. CX Codex +1 160installs

Project sponsors

Companies that keep this analytics open