一键导入
sui-move
Move smart contract development on Sui. Use when writing, reviewing, or debugging Move code, Move.toml configuration, or Sui object model patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Move smart contract development on Sui. Use when writing, reviewing, or debugging Move code, Move.toml configuration, or Sui object model patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sui-move |
| description | Move smart contract development on Sui. Use when writing, reviewing, or debugging Move code, Move.toml configuration, or Sui object model patterns. |
Write Move smart contracts on Sui. Follow these rules precisely. Move on Sui is not Aptos Move and is not Rust — do not apply patterns from those languages.
This skill routes to focused sub-skills. Load only the ones relevant to the current task.
Skill: sui-dev-tools:sui-move-setup
Load when: creating a new Move package, configuring Move.toml, running sui move build or sui move test, writing tests, or unsure what patterns to avoid from other Move dialects.
Covers: §1 Package Setup, §2 Building and Testing, §3 What Move on Sui is NOT.
Skill: sui-dev-tools:sui-move-syntax
Load when: writing module declarations, imports, functions, enums, macros, or need guidance on visibility, mutability, method syntax, or comments.
Covers: §1 Module Layout, §2 Mutability, §3 Visibility, §4 Method Syntax, §5 Enums, §6 Macros, §7 Comments.
Skill: sui-dev-tools:sui-move-object
Load when: defining structs, choosing abilities (key/store/copy/drop), working with object ownership (transfer/share/freeze), naming conventions, or using dynamic fields.
Covers: §1 Structs, §2 Object Abilities Cheat Sheet, §3 Dynamic Fields.
Skill: sui-dev-tools:sui-move-patterns
Load when: emitting events, handling errors, implementing OTW or capability patterns, or designing composable/pure functions.
Covers: §1 Events, §2 Error Handling, §3 One-Time Witness, §4 Capability Pattern, §5 Pure Functions.
Skill: sui-dev-tools:sui-move-stdlib
Load when: working with strings, Coin/Balance, Option, addresses/IDs, vectors, or TxContext — the everyday Sui Move APIs.
Covers: §1 Common Standard Library Patterns.
| Task | Load |
|---|---|
| Creating a new Move project | sui-move-setup |
| Writing module code / functions | sui-move-syntax |
| Defining structs or objects | sui-move-object + sui-move-syntax |
| Using Coin, Balance, vectors, etc. | sui-move-stdlib |
| Emitting events or error handling | sui-move-patterns |
| Implementing access control (caps) | sui-move-patterns + sui-move-object |
| Writing or fixing tests | sui-move-setup |
| Full contract from scratch | all sub-skills |
| Code review | all sub-skills |
This skill should be used when the user says "run the sprint", "autonomous sprint", "run all stories", "execute sprint plan", "complete all epics", or asks to autonomously execute all stories in the current sprint. Drives Claude Code through create-story, dev-story, quality gates, and code-review in a continuous loop without human intervention until all stories are done or blocked.
This skill should be used when the user asks to "upgrade a Solana program through Squads", "set up squads multisig deployment", "create a Squads upgrade proposal", "configure squads-program-action", "deploy via Squads multisig", "set up Squads CI/CD pipeline", "squads GitHub Actions workflow", or mentions Solana program upgrades involving Squads v4 multisig governance.
This skill should be used when the user asks to "create a diagram", "make an architecture diagram", "design a system diagram", "draw an architecture", "create a technical diagram", "make a deployment diagram", "visualize infrastructure", "create a data flow diagram", "draw system components", "make a network diagram", "diagram a cloud architecture", "draw an AWS diagram", "create a Kubernetes diagram", or mentions architecture, system design, infrastructure diagrams, component relationships, or data flow. Do NOT trigger for cover images, step-by-step process flows, or infographics.
This skill should be used when the user asks to "write something satirical about work", "roast a corporate event", "write a vignette about a bad meeting", "satirise startup culture", "write a LinkedIn post parody", "make fun of OKRs", "write a scene about a reorg", "satirise remote work rituals", "mock team-building activities", "write a satirical all-hands recap", or wants any comedic or ironic depiction of organisational life, management behaviour, or workplace absurdity across offices, startups, remote teams, or any setting where hierarchy produces comedy.
Write technical documentation, blog articles, code reviews, and product writeups in a storytelling style that's direct, humble, and problem-first. Use this skill whenever the user wants to publish articles, write technical reviews, document processes, or explain systems in a way that's concrete and human. This includes API docs, how-to guides, product comparisons, incident postmortems, feature writeups, and code reviews. The skill applies whether you're writing for public blogs, internal teams, or personal knowledge vaults. Provide both public-facing (slightly more scaffolding) and internal (tighter) versions when requested.
This skill should be used when the user asks to "create a cover image", "generate a blog cover", "make an OG image", "design a social preview", "create a thumbnail for a post", "add a cover to my article", "make a featured image", "create a header image for a post", "generate an open graph image", or mentions cover images, OG images, social preview images, or blog post thumbnails. Do NOT trigger for diagrams, architecture diagrams, or process flows.