modern-move-syntax

Rewrite Move code to enforce Sui 2024 edition syntax.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill modern-move-syntax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modern-move-syntax
Source: https://github.com/MystenLabs/skills/tree/main/modern-move-syntax
Command: npx skills add https://github.com/MystenLabs/skills --skill modern-move-syntax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents AI-generated Move code from using legacy, pre-2024 patterns that fail to compile on Sui or reduce code quality.

Core Features & Use Cases

  • Method-call syntax enforcement for coins, balances, object/UID operations, and common patterns where module-style calls are outdated.
  • Sui Move 2024 edition idioms for tx context access, string literals, vector creation and method usage, option handling, and loop macros.
  • Modern destructuring and API naming using .. for unused struct fields and updated standard-library function names.

Quick Start

Use the modern-move-syntax skill whenever you need the agent to rewrite or generate Move code so it uses 2024 edition syntax and avoids legacy function-call patterns.

Frequently Asked Questions about modern-move-syntax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Move code to use 2024 edition syntax on Sui?

You update Move code to 2024 edition syntax by enforcing chained method calls, macro-based patterns for vectors and options, and modern struct destructuring using `..` to prevent pre-2024 legacy patterns from breaking Sui builds.

Why does my Sui Move build fail with legacy function-call patterns?

Sui Move builds fail because the 2024 edition deprecates module-style calls for coins, balances, and object operations, requiring updated standard-library APIs and chained method syntax to maintain code quality.

What is the 2024 edition method syntax for Move vector and option handling?

The 2024 edition method syntax for Move vector and option handling replaces legacy module-style calls with macro-based patterns and chained method calls to ensure correct field visibility and tx context usage.

Can I use `..` for unused struct fields when refactoring Move code?

Yes, you can use `..` for unused struct fields when refactoring Move code, as the 2024 edition enforces modern destructuring conventions and correct field visibility to prevent outdated API naming.

Does AI-generated Move code need syntax enforcement for Sui?

AI-generated Move code needs syntax enforcement for Sui because models often output pre-2024 patterns that fail to compile or lower code quality without consistent replacement rules matching 2024 idioms.

What are the limitations of using legacy module-style calls in Sui Move?

Limitations of using legacy module-style calls in Sui Move include failing builds and lowered code quality, as the 2024 edition requires consistent replacement rules for tx context access, string literals, and standard-library APIs.