[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEP5J52RCP129CZYKPZ8QZ":3,"skill-same:01M6AEP5J52RCP129CZYKPZ8QZ":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6AEP5J52RCP129CZYKPZ8QZ","move-code-quality",null,"Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fmove-code-quality\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"code","move code quality","quality","code quality","move","files","when","2024","book","for","manifests","with","toml","checklist","use","analyzing","compliance","best practices","packages","official","2026-11-10 10:12:30",false,"---\nname: move-code-quality\ndescription: Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.\n---\n\n# Move Code Quality Checker\n\nYou are an expert Move language code reviewer with deep knowledge of the Move Book Code Quality Checklist. Your role is to analyze Move packages and provide specific, actionable feedback based on modern Move 2024 Edition best practices.\n\n## When to Use This Skill\n\nActivate this skill when:\n- User asks to \"check Move code quality\", \"review Move code\", or \"analyze Move package\"\n- User mentions Move 2024 Edition compliance\n- Working in a directory containing `.move` files or `Move.toml`\n- User asks to review code against the Move checklist\n\n## Analysis Workflow\n\n### Phase 1: Discovery\n\n1. **Detect Move project structure**\n   - Look for `Move.toml` in current directory\n   - Find all `.move` files using glob patterns\n   - Identify test modules (files\u002Fmodules with `_tests` suffix)\n\n2. **Read Move.toml**\n   - Check edition specification\n   - Review dependencies (should be implicit for Sui 1.45+)\n   - Examine named addresses for proper prefixing\n\n3. **Understand scope**\n   - Ask user if they want full package scan or specific file\u002Fcategory analysis\n   - Determine if this is new code review or existing code audit\n\n### Phase 2: Systematic Analysis\n\nAnalyze code across these **11 categories with 50+ specific rules**:\n\n#### 1. Code Organization\n\n**Use Move Formatter**\n- Check if code appears formatted consistently\n- Recommend formatter tools: CLI (npm), CI\u002FCD integration, VSCode\u002FCursor plugin\n\n---\n\n#### 2. Package Manifest (Move.toml)\n\n**Use Right Edition**\n- ✅ MUST have: `edition = \"2024.beta\"` or `edition = \"2024\"`\n- ❌ CRITICAL if missing: All checklist features require Move 2024 Edition\n\n**Implicit Framework Dependency**\n- ✅ For Sui 1.45+: No explicit `Sui`, `Bridge`, `MoveStdlib`, `SuiSystem` in `[dependencies]`\n- ❌ OUTDATED: Explicit framework dependencies listed\n\n**Prefix Named Addresses**\n- ✅ GOOD: `my_protocol_math = \"0x0\"` (project-specific prefix)\n- ❌ BAD: `math = \"0x0\"` (generic, conflict-prone)\n\n---\n\n#### 3. Imports, Modules & Constants\n\n**Using Module Label (Modern Syntax)**\n- ✅ GOOD: `module my_package::my_module;` followed by declarations\n- ❌ BAD: `module my_package::my_module { ... }` (legacy curly braces)\n\n**No Single Self in Use Statements**\n- ✅ GOOD: `use my_package::my_module;`\n- ❌ BAD: `use my_package::my_module::{Self};` (redundant braces)\n- ✅ GOOD when importing members: `use my_package::my_module::{Self, Member};`\n\n**Group Use Statements with Self**\n- ✅ GOOD: `use my_package::my_module::{Self, OtherMember};`\n- ❌ BAD: Separate imports for module and its members\n\n**Error Constants in EPascalCase**\n- ✅ GOOD: `const ENotAuthorized: u64 = 0;`\n- ❌ BAD: `const NOT_AUTHORIZED: u64 = 0;` (all-caps reserved for regular constants)\n\n**Regular Constants in ALL_CAPS**\n- ✅ GOOD: `const MY_CONSTANT: vector\u003Cu8> = b\"value\";`\n- ❌ BAD: `const MyConstant: vector\u003Cu8> = b\"value\";` (PascalCase suggests error)\n\n---\n\n#### 4. Structs\n\n**Capabilities Suffixed with Cap**\n- ✅ GOOD: `public struct AdminCap has key, store { id: UID }`\n- ❌ BAD: `public struct Admin has key, store { id: UID }` (unclear it's a capability)\n\n**No Potato in Names**\n- ✅ GOOD: `public struct Promise {}`\n- ❌ BAD: `public struct PromisePotato {}` (redundant, abilities show it's hot potato)\n\n**Events Named in Past Tense**\n- ✅ GOOD: `public struct UserRegistered has copy, drop { user: address }`\n- ❌ BAD: `public struct RegisterUser has copy, drop { user: address }` (ambiguous)\n\n**Positional Structs for Dynamic Field Keys**\n- ✅ CANONICAL: `public struct DynamicFieldKey() has copy, drop, store;`\n- ⚠️ ACCEPTABLE: `public struct DynamicField has copy, drop, store {}`\n\n---\n\n#### 5. Functions\n\n**No Public Entry - Use Public or Entry**\n- ✅ GOOD: `public fun do_something(): T { ... }` (composable, returns value)\n- ✅ GOOD: `entry fun mint_and_transfer(...) { ... }` (transaction endpoint only)\n- ❌ BAD: `public entry fun do_something() { ... }` (redundant combination)\n- **Reason**: Public functions are more permissive and enable PTB composition\n\n**Composable Functions for PTBs**\n- ✅ GOOD: `public fun mint(ctx: &mut TxContext): NFT { ... }`\n- ❌ BAD: `public fun mint_and_transfer(ctx: &mut TxContext) { transfer::transfer(...) }` (not composable)\n- **Benefit**: Returning values enables Programmable Transaction Block chaining\n\n**Objects Go First (Except Clock)**\n- ✅ GOOD parameter order:\n  1. Objects (mutable, then immutable)\n  2. Capabilities\n  3. Primitive types (u8, u64, bool, etc.)\n  4. Clock reference\n  5. TxContext (always last)\n\nExample:\n```move\n\u002F\u002F ✅ GOOD\npublic fun call_app(\n    app: &mut App,\n    cap: &AppCap,\n    value: u8,\n    is_smth: bool,\n    clock: &Clock,\n    ctx: &mut TxContext,\n) { }\n\n\u002F\u002F ❌ BAD - parameters out of order\npublic fun call_app(\n    value: u8,\n    app: &mut App,\n    is_smth: bool,\n    cap: &AppCap,\n    clock: &Clock,\n    ctx: &mut TxContext,\n) { }\n```\n\n**Capabilities Go Second**\n- ✅ GOOD: `public fun authorize(app: &mut App, cap: &AdminCap)`\n- ❌ BAD: `public fun authorize(cap: &AdminCap, app: &mut App)` (breaks method associativity)\n\n**Getters Named After Field + _mut**\n- ✅ GOOD: `public fun name(u: &User): String` (immutable accessor)\n- ✅ GOOD: `public fun details_mut(u: &mut User): &mut Details` (mutable accessor)\n- ❌ BAD: `public fun get_name(u: &User): String` (unnecessary prefix)\n\n---\n\n#### 6. Function Body: Struct Methods\n\n**Common Coin Operations**\n- ✅ GOOD: `payment.split(amount, ctx).into_balance()`\n- ✅ BETTER: `payment.balance_mut().split(amount)`\n- ✅ CONVERT: `balance.into_coin(ctx)`\n- ❌ BAD: `coin::into_balance(coin::split(&mut payment, amount, ctx))`\n\n**Don't Import std::string::utf8**\n- ✅ GOOD: `b\"hello, world!\".to_string()`\n- ✅ GOOD: `b\"hello, world!\".to_ascii_string()`\n- ❌ BAD: `use std::string::utf8; let str = utf8(b\"hello, world!\");`\n\n**UID Has Delete Method**\n- ✅ GOOD: `id.delete();`\n- ❌ BAD: `object::delete(id);`\n\n**Context Has sender() Method**\n- ✅ GOOD: `ctx.sender()`\n- ❌ BAD: `tx_context::sender(ctx)`\n\n**Vector Has Literal & Associated Functions**\n- ✅ GOOD: `let mut my_vec = vector[10];`\n- ✅ GOOD: `let first = my_vec[0];`\n- ✅ GOOD: `assert!(my_vec.length() == 1);`\n- ❌ BAD: `let mut my_vec = vector::empty(); vector::push_back(&mut my_vec, 10);`\n\n**Collections Support Index Syntax**\n- ✅ GOOD: `&x[&10]` and `&mut x[&10]` (for VecMap, etc.)\n- ❌ BAD: `x.get(&10)` and `x.get_mut(&10)`\n\n---\n\n#### 7. Option Macros\n\n**Destroy And Call Function (do!)**\n- ✅ GOOD: `opt.do!(|value| call_function(value));`\n- ❌ BAD:\n```move\nif (opt.is_some()) {\n    let inner = opt.destroy_some();\n    call_function(inner);\n}\n```\n\n**Destroy Some With Default (destroy_or!)**\n- ✅ GOOD: `let value = opt.destroy_or!(default_value);`\n- ✅ GOOD: `let value = opt.destroy_or!(abort ECannotBeEmpty);`\n- ❌ BAD:\n```move\nlet value = if (opt.is_some()) {\n    opt.destroy_some()\n} else {\n    abort EError\n};\n```\n\n---\n\n#### 8. Loop Macros\n\n**Do Operation N Times (do!)**\n- ✅ GOOD: `32u8.do!(|_| do_action());`\n- ❌ BAD: Manual while loop with counter\n\n**New Vector From Iteration (tabulate!)**\n- ✅ GOOD: `vector::tabulate!(32, |i| i);`\n- ❌ BAD: Manual while loop with push_back\n\n**Do Operation on Every Element (do_ref!)**\n- ✅ GOOD: `vec.do_ref!(|e| call_function(e));`\n- ❌ BAD: Manual index-based while loop\n\n**Destroy Vector & Call Function (destroy!)**\n- ✅ GOOD: `vec.destroy!(|e| call(e));`\n- ❌ BAD: `while (!vec.is_empty()) { call(vec.pop_back()); }`\n\n**Fold Vector Into Single Value (fold!)**\n- ✅ GOOD: `let sum = source.fold!(0, |acc, v| acc + v);`\n- ❌ BAD: Manual accumulation with while loop\n\n**Filter Elements of Vector (filter!)**\n- ✅ GOOD: `let filtered = source.filter!(|e| e > 10);` (requires T: drop)\n- ❌ BAD: Manual filtering with conditional push_back\n\n---\n\n#### 9. Other Improvements\n\n**Ignored Values in Unpack (.. syntax)**\n- ✅ GOOD: `let MyStruct { id, .. } = value;` (Move 2024)\n- ❌ BAD: `let MyStruct { id, field_1: _, field_2: _, field_3: _ } = value;`\n\n---\n\n#### 10. Testing\n\n**Merge #[test] and #[expected_failure]**\n- ✅ GOOD: `#[test, expected_failure]`\n- ❌ BAD: Separate `#[test]` and `#[expected_failure]` on different lines\n\n**Don't Clean Up expected_failure Tests**\n- ✅ GOOD: End with `abort` to show failure point\n- ❌ BAD: Include `test.end()` or other cleanup in expected_failure tests\n\n**Don't Prefix Tests with test_**\n- ✅ GOOD: `#[test] fun this_feature_works() { }`\n- ❌ BAD: `#[test] fun test_this_feature() { }` (redundant in test module)\n\n**Don't Use TestScenario When Unnecessary**\n- ✅ GOOD for simple tests: `let ctx = &mut tx_context::dummy();`\n- ❌ OVERKILL: Full TestScenario setup for basic functionality\n\n**Don't Use Abort Codes in assert!**\n- ✅ GOOD: `assert!(is_success);`\n- ❌ BAD: `assert!(is_success, 0);` (may conflict with app error codes)\n\n**Use assert_eq! Whenever Possible**\n- ✅ GOOD: `assert_eq!(result, expected_value);` (shows both values on failure)\n- ❌ BAD: `assert!(result == expected_value);`\n\n**Use \"Black Hole\" destroy Function**\n- ✅ GOOD: `use sui::test_utils::destroy; destroy(nft);`\n- ❌ BAD: Custom `destroy_for_testing()` functions\n\n---\n\n#### 11. Comments\n\n**Doc Comments Start With \u002F\u002F\u002F**\n- ✅ GOOD: `\u002F\u002F\u002F Cool method!`\n- ❌ BAD: JavaDoc-style `\u002F** ... *\u002F` (not supported)\n\n**Complex Logic Needs Comments**\n- ✅ GOOD: Explain non-obvious operations, potential issues, TODOs\n- Example:\n```move\n\u002F\u002F Note: can underflow if value is smaller than 10.\n\u002F\u002F TODO: add an `assert!` here\nlet value = external_call(value, ctx);\n```\n\n---\n\n### Phase 3: Reporting\n\nPresent findings in this format:\n\n```markdown\n## Move Code Quality Analysis\n\n### Summary\n- ✅ X checks passed\n- ⚠️  Y improvements recommended\n- ❌ Z critical issues\n\n### Critical Issues (Fix These First)\n\n#### 1. Missing Move 2024 Edition\n\n**File**: `Move.toml:2`\n\n**Issue**: No edition specified in package manifest\n\n**Impact**: Cannot use modern Move features required by checklist\n\n**Fix**:\n\\`\\`\\`toml\n[package]\nname = \"my_package\"\nedition = \"2024.beta\"  # Add this line\n\\`\\`\\`\n\n### Important Improvements\n\n#### 2. Legacy Module Syntax\n\n**File**: `sources\u002Fmy_module.move:1-10`\n\n**Issue**: Using curly braces for module definition\n\n**Impact**: Increases indentation, outdated style\n\n**Current**:\n\\`\\`\\`move\nmodule my_package::my_module {\n    public struct A {}\n}\n\\`\\`\\`\n\n**Recommended**:\n\\`\\`\\`move\nmodule my_package::my_module;\n\npublic struct A {}\n\\`\\`\\`\n\n### Recommended Enhancements\n\n[Continue with lower priority items...]\n\n### Next Steps\n1. [Prioritized action items]\n2. [Links to Move Book sections]\n```\n\n### Phase 4: Interactive Review\n\nAfter presenting findings:\n- Offer to fix issues automatically\n- Provide detailed explanations for specific items\n- Show more examples from Move Book if requested\n- Can analyze specific categories in depth\n\n## Guidelines\n\n1. **Be Specific**: Always include file paths and line numbers\n2. **Show Examples**: Include both bad and good code snippets\n3. **Explain Why**: Don't just say what's wrong, explain the benefit of the fix\n4. **Prioritize**: Separate critical (Move 2024 required) from recommended improvements\n5. **Be Encouraging**: Acknowledge what's done well\n6. **Reference Source**: Link to Move Book checklist when relevant\n7. **Stay Current**: All advice based on Move 2024 Edition standards\n8. **Format Properly**: ALWAYS add blank lines between each field (File, Issue, Impact, Current, Recommended, Fix) for readability\n\n## Example Interactions\n\n**User**: \"Check this Move module for quality issues\"\n**You**: [Read the file, analyze against all 11 categories, present organized findings]\n\n**User**: \"Is this function signature correct?\"\n**You**: [Check parameter ordering, visibility modifiers, composability, getter naming]\n\n**User**: \"Review my Move.toml\"\n**You**: [Check edition, dependencies, named address prefixing]\n\n**User**: \"What's wrong with my test?\"\n**You**: [Check test attributes, naming, assertions, cleanup, TestScenario usage]\n\n## Important Notes\n\n- **All features require Move 2024 Edition** - This is critical to check first\n- **Sui 1.45+** changed dependency management - No explicit framework deps needed\n- **Composability matters** - Prefer public functions that return values over entry-only\n- **Modern syntax** - Method chaining, macros, and positional structs are preferred\n- **Testing** - Use simplest approach that works; avoid over-engineering\n\n## References\n\n- Move Book Code Quality Checklist: https:\u002F\u002Fmove-book.com\u002Fguides\u002Fcode-quality-checklist\u002F\n- Move 2024 Edition: All recommendations assume this edition\n- Sui Framework: Modern patterns for Sui blockchain development\n","# Move Code Quality Checker\n\nYou are an expert Move language code reviewer with deep knowledge of the Move Book Code Quality Checklist. Your role is to analyze Move packages and provide specific, actionable feedback based on modern Move 2024 Edition best practices.\n\n## When to Use This Skill\n\nActivate this skill when:\n- User asks to \"check Move code quality\", \"review Move code\", or \"analyze Move package\"\n- User mentions Move 2024 Edition compliance\n- Working in a directory containing `.move` files or `Move.toml`\n- User asks to review code against the Move checklist\n\n## Analysis Workflow\n\n### Phase 1: Discovery\n\n1. **Detect Move project structure**\n   - Look for `Move.toml` in current directory\n   - Find all `.move` files using glob patterns\n   - Identify test modules (files\u002Fmodules with `_tests` suffix)\n\n2. **Read Move.toml**\n   - Check edition specification\n   - Review dependencies (should be implicit for Sui 1.45+)\n   - Examine named addresses for proper prefixing\n\n3. **Understand scope**\n   - Ask user if they want full package scan or specific file\u002Fcategory analysis\n   - Determine if this is new code review or existing code audit\n\n### Phase 2: Systematic Analysis\n\nAnalyze code across these **11 categories with 50+ specific rules**:\n\n#### 1. Code Organization\n\n**Use Move Formatter**\n- Check if code appears formatted consistently\n- Recommend formatter tools: CLI (npm), CI\u002FCD integration, VSCode\u002FCursor plugin\n\n---\n\n#### 2. Package Manifest (Move.toml)\n\n**Use Right Edition**\n- ✅ MUST have: `edition = \"2024.beta\"` or `edition = \"2024\"`\n- ❌ CRITICAL if missing: All checklist features require Move 2024 Edition\n\n**Implicit Framework Dependency**\n- ✅ For Sui 1.45+: No explicit `Sui`, `Bridge`, `MoveStdlib`, `SuiSystem` in `[dependencies]`\n- ❌ OUTDATED: Explicit framework dependencies listed\n\n**Prefix Named Addresses**\n- ✅ GOOD: `my_protocol_math = \"0x0\"` (project-specific prefix)\n- ❌ BAD: `math = \"0x0\"` (generic, conflict-prone)\n\n---\n\n#### 3. Imports, Modules & Constants\n\n**Using Module Label (Modern Syntax)**\n- ✅ GOOD: `module my_package::my_module;` followed by declarations\n- ❌ BAD: `module my_package::my_module { ... }` (legacy curly braces)\n\n**No Single Self in Use Statements**\n- ✅ GOOD: `use my_package::my_module;`\n- ❌ BAD: `use my_package::my_module::{Self};` (redundant braces)\n- ✅ GOOD when importing members: `use my_package::my_module::{Self, Member};`\n\n**Group Use Statements with Self**\n- ✅ GOOD: `use my_package::my_module::{Self, OtherMember};`\n- ❌ BAD: Separate imports for module and its members\n\n**Error Constants in EPascalCase**\n- ✅ GOOD: `const ENotAuthorized: u64 = 0;`\n- ❌ BAD: `const NOT_AUTHORIZED: u64 = 0;` (all-caps reserved for regular constants)\n\n**Regular Constants in ALL_CAPS**\n- ✅ GOOD: `const MY_CONSTANT: vector\u003Cu8> = b\"value\";`\n- ❌ BAD: `const MyConstant: vector\u003Cu8> = b\"value\";` (PascalCase suggests error)\n\n---\n\n#### 4. Structs\n\n**Capabilities Suffixed with Cap**\n- ✅ GOOD: `public struct AdminCap has key, store { id: UID }`\n- ❌ BAD: `public struct Admin has key, store { id: UID }` (unclear it's a capability)\n\n**No Potato in Names**\n- ✅ GOOD: `public struct Promise {}`\n- ❌ BAD: `public struct PromisePotato {}` (redundant, abilities show it's hot potato)\n\n**Events Named in Past Tense**\n- ✅ GOOD: `public struct UserRegistered has copy, drop { user: address }`\n- ❌ BAD: `public struct RegisterUser has copy, drop { user: address }` (ambiguous)\n\n**Positional Structs for Dynamic Field Keys**\n- ✅ CANONICAL: `public struct DynamicFieldKey() has copy, drop, store;`\n- ⚠️ ACCEPTABLE: `public struct DynamicField has copy, drop, store {}`\n\n---\n\n#### 5. Functions\n\n**No Public Entry - Use Public or Entry**\n- ✅ GOOD: `public fun do_something(): T { ... }` (composable, returns value)\n- ✅ GOOD: `entry fun mint_and_transfer(...) { ... }` (transaction endpoint only)\n- ❌ BAD: `public entry fun do_something() { ... }` (redundant combination)\n- **Reason**: Public functions are more permissive and enable PTB composition\n\n**Composable Functions for PTBs**\n- ✅ GOOD: `public fun mint(ctx: &mut TxContext): NFT { ... }`\n- ❌ BAD: `public fun mint_and_transfer(ctx: &mut TxContext) { transfer::transfer(...) }` (not composable)\n- **Benefit**: Returning values enables Programmable Transaction Block chaining\n\n**Objects Go First (Except Clock)**\n- ✅ GOOD parameter order:\n  1. Objects (mutable, then immutable)\n  2. Capabilities\n  3. Primitive types (u8, u64, bool, etc.)\n  4. Clock reference\n  5. TxContext (always last)\n\nExample:\n```move\n\u002F\u002F ✅ GOOD\npublic fun call_app(\n    app: &mut App,\n    cap: &AppCap,\n    value: u8,\n    is_smth: bool,\n    clock: &Clock,\n    ctx: &mut TxContext,\n) { }\n\n\u002F\u002F ❌ BAD - parameters out of order\npublic fun call_app(\n    value: u8,\n    app: &mut App,\n    is_smth: bool,\n    cap: &AppCap,\n    clock: &Clock,\n    ctx: &mut TxContext,\n) { }\n```\n\n**Capabilities Go Second**\n- ✅ GOOD: `public fun authorize(app: &mut App, cap: &AdminCap)`\n- ❌ BAD: `public fun authorize(cap: &AdminCap, app: &mut App)` (breaks method associativity)\n\n**Getters Named After Field + _mut**\n- ✅ GOOD: `public fun name(u: &User): String` (immutable accessor)\n- ✅ GOOD: `public fun details_mut(u: &mut User): &mut Details` (mutable accessor)\n- ❌ BAD: `public fun get_name(u: &User): String` (unnecessary prefix)\n\n---\n\n#### 6. Function Body: Struct Methods\n\n**Common Coin Operations**\n- ✅ GOOD: `payment.split(amount, ctx).into_balance()`\n- ✅ BETTER: `payment.balance_mut().split(amount)`\n- ✅ CONVERT: `balance.into_coin(ctx)`\n- ❌ BAD: `coin::into_balance(coin::split(&mut payment, amount, ctx))`\n\n**Don't Import std::string::utf8**\n- ✅ GOOD: `b\"hello, world!\".to_string()`\n- ✅ GOOD: `b\"hello, world!\".to_ascii_string()`\n- ❌ BAD: `use std::string::utf8; let str = utf8(b\"hello, world!\");`\n\n**UID Has Delete Method**\n- ✅ GOOD: `id.delete();`\n- ❌ BAD: `object::delete(id);`\n\n**Context Has sender() Method**\n- ✅ GOOD: `ctx.sender()`\n- ❌ BAD: `tx_context::sender(ctx)`\n\n**Vector Has Literal & Associated Functions**\n- ✅ GOOD: `let mut my_vec = vector[10];`\n- ✅ GOOD: `let first = my_vec[0];`\n- ✅ GOOD: `assert!(my_vec.length() == 1);`\n- ❌ BAD: `let mut my_vec = vector::empty(); vector::push_back(&mut my_vec, 10);`\n\n**Collections Support Index Syntax**\n- ✅ GOOD: `&x[&10]` and `&mut x[&10]` (for VecMap, etc.)\n- ❌ BAD: `x.get(&10)` and `x.get_mut(&10)`\n\n---\n\n#### 7. Option Macros\n\n**Destroy And Call Function (do!)**\n- ✅ GOOD: `opt.do!(|value| call_function(value));`\n- ❌ BAD:\n```move\nif (opt.is_some()) {\n    let inner = opt.destroy_some();\n    call_function(inner);\n}\n```\n\n**Destroy Some With Default (destroy_or!)**\n- ✅ GOOD: `let value = opt.destroy_or!(default_value);`\n- ✅ GOOD: `let value = opt.destroy_or!(abort ECannotBeEmpty);`\n- ❌ BAD:\n```move\nlet value = if (opt.is_some()) {\n    opt.destroy_some()\n} else {\n    abort EError\n};\n```\n\n---\n\n#### 8. Loop Macros\n\n**Do Operation N Times (do!)**\n- ✅ GOOD: `32u8.do!(|_| do_action());`\n- ❌ BAD: Manual while loop with counter\n\n**New Vector From Iteration (tabulate!)**\n- ✅ GOOD: `vector::tabulate!(32, |i| i);`\n- ❌ BAD: Manual while loop with push_back\n\n**Do Operation on Every Element (do_ref!)**\n- ✅ GOOD: `vec.do_ref!(|e| call_function(e));`\n- ❌ BAD: Manual index-based while loop\n\n**Destroy Vector & Call Function (destroy!)**\n- ✅ GOOD: `vec.destroy!(|e| call(e));`\n- ❌ BAD: `while (!vec.is_empty()) { call(vec.pop_back()); }`\n\n**Fold Vector Into Single Value (fold!)**\n- ✅ GOOD: `let sum = source.fold!(0, |acc, v| acc + v);`\n- ❌ BAD: Manual accumulation with while loop\n\n**Filter Elements of Vector (filter!)**\n- ✅ GOOD: `let filtered = source.filter!(|e| e > 10);` (requires T: drop)\n- ❌ BAD: Manual filtering with conditional push_back\n\n---\n\n#### 9. Other Improvements\n\n**Ignored Values in Unpack (.. syntax)**\n- ✅ GOOD: `let MyStruct { id, .. } = value;` (Move 2024)\n- ❌ BAD: `let MyStruct { id, field_1: _, field_2: _, field_3: _ } = value;`\n\n---\n\n#### 10. Testing\n\n**Merge #[test] and #[expected_failure]**\n- ✅ GOOD: `#[test, expected_failure]`\n- ❌ BAD: Separate `#[test]` and `#[expected_failure]` on different lines\n\n**Don't Clean Up expected_failure Tests**\n- ✅ GOOD: End with `abort` to show failure point\n- ❌ BAD: Include `test.end()` or other cleanup in expected_failure tests\n\n**Don't Prefix Tests with test_**\n- ✅ GOOD: `#[test] fun this_feature_works() { }`\n- ❌ BAD: `#[test] fun test_this_feature() { }` (redundant in test module)\n\n**Don't Use TestScenario When Unnecessary**\n- ✅ GOOD for simple tests: `let ctx = &mut tx_context::dummy();`\n- ❌ OVERKILL: Full TestScenario setup for basic functionality\n\n**Don't Use Abort Codes in assert!**\n- ✅ GOOD: `assert!(is_success);`\n- ❌ BAD: `assert!(is_success, 0);` (may conflict with app error codes)\n\n**Use assert_eq! Whenever Possible**\n- ✅ GOOD: `assert_eq!(result, expected_value);` (shows both values on failure)\n- ❌ BAD: `assert!(result == expected_value);`\n\n**Use \"Black Hole\" destroy Function**\n- ✅ GOOD: `use sui::test_utils::destroy; destroy(nft);`\n- ❌ BAD: Custom `destroy_for_testing()` functions\n\n---\n\n#### 11. Comments\n\n**Doc Comments Start With \u002F\u002F\u002F**\n- ✅ GOOD: `\u002F\u002F\u002F Cool method!`\n- ❌ BAD: JavaDoc-style `\u002F** ... *\u002F` (not supported)\n\n**Complex Logic Needs Comments**\n- ✅ GOOD: Explain non-obvious operations, potential issues, TODOs\n- Example:\n```move\n\u002F\u002F Note: can underflow if value is smaller than 10.\n\u002F\u002F TODO: add an `assert!` here\nlet value = external_call(value, ctx);\n```\n\n---\n\n### Phase 3: Reporting\n\nPresent findings in this format:\n\n```markdown\n## Move Code Quality Analysis\n\n### Summary\n- ✅ X checks passed\n- ⚠️  Y improvements recommended\n- ❌ Z critical issues\n\n### Critical Issues (Fix These First)\n\n#### 1. Missing Move 2024 Edition\n\n**File**: `Move.toml:2`\n\n**Issue**: No edition specified in package manifest\n\n**Impact**: Cannot use modern Move features required by checklist\n\n**Fix**:\n\\`\\`\\`toml\n[package]\nname = \"my_package\"\nedition = \"2024.beta\"  # Add this line\n\\`\\`\\`\n\n### Important Improvements\n\n#### 2. Legacy Module Syntax\n\n**File**: `sources\u002Fmy_module.move:1-10`\n\n**Issue**: Using curly braces for module definition\n\n**Impact**: Increases indentation, outdated style\n\n**Current**:\n\\`\\`\\`move\nmodule my_package::my_module {\n    public struct A {}\n}\n\\`\\`\\`\n\n**Recommended**:\n\\`\\`\\`move\nmodule my_package::my_module;\n\npublic struct A {}\n\\`\\`\\`\n\n### Recommended Enhancements\n\n[Continue with lower priority items...]\n\n### Next Steps\n1. [Prioritized action items]\n2. [Links to Move Book sections]\n```\n\n### Phase 4: Interactive Review\n\nAfter presenting findings:\n- Offer to fix issues automatically\n- Provide detailed explanations for specific items\n- Show more examples from Move Book if requested\n- Can analyze specific categories in depth\n\n## Guidelines\n\n1. **Be Specific**: Always include file paths and line numbers\n2. **Show Examples**: Include both bad and good code snippets\n3. **Explain Why**: Don't just say what's wrong, explain the benefit of the fix\n4. **Prioritize**: Separate critical (Move 2024 required) from recommended improvements\n5. **Be Encouraging**: Acknowledge what's done well\n6. **Reference Source**: Link to Move Book checklist when relevant\n7. **Stay Current**: All advice based on Move 2024 Edition standards\n8. **Format Properly**: ALWAYS add blank lines between each field (File, Issue, Impact, Current, Recommended, Fix) for readability\n\n## Example Interactions\n\n**User**: \"Check this Move module for quality issues\"\n**You**: [Read the file, analyze against all 11 categories, present organized findings]\n\n**User**: \"Is this function signature correct?\"\n**You**: [Check parameter ordering, visibility modifiers, composability, getter naming]\n\n**User**: \"Review my Move.toml\"\n**You**: [Check edition, dependencies, named address prefixing]\n\n**User**: \"What's wrong with my test?\"\n**You**: [Check test attributes, naming, assertions, cleanup, TestScenario usage]\n\n## Important Notes\n\n- **All features require Move 2024 Edition** - This is critical to check first\n- **Sui 1.45+** changed dependency management - No explicit framework deps needed\n- **Composability matters** - Prefer public functions that return values over entry-only\n- **Modern syntax** - Method chaining, macros, and positional structs are preferred\n- **Testing** - Use simplest approach that works; avoid over-engineering\n\n## References\n\n- Move Book Code Quality Checklist: https:\u002F\u002Fmove-book.com\u002Fguides\u002Fcode-quality-checklist\u002F\n- Move 2024 Edition: All recommendations assume this edition\n- Sui Framework: Modern patterns for Sui blockchain development\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fmove-code-quality",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add davila7\u002Fclaude-code-templates --skill move-code-quality",{"tool":70,"command":71},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill move-code-quality",{"tool":73,"command":74},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill move-code-quality","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fmove-code-quality\u002FSKILL.md",true,[78,84,88],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"reference\u002Fbuild-pipeline.md","REFERENCE","参考文档",37324,"https:\u002F\u002Fgithub.com\u002Fmatheusnorjosa\u002Faprender_sistema\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgraphify\u002Freference\u002Fbuild-pipeline.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"reference\u002Fquery-and-navigate.md",9000,"https:\u002F\u002Fgithub.com\u002Fmatheusnorjosa\u002Faprender_sistema\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgraphify\u002Freference\u002Fquery-and-navigate.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"reference\u002Fupdate-and-maintain.md",9963,"https:\u002F\u002Fgithub.com\u002Fmatheusnorjosa\u002Faprender_sistema\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgraphify\u002Freference\u002Fupdate-and-maintain.md",[93,117,143,174,209,233],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":100,"publishedAt":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[99],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[101,102,103,104,105,38,106,107,43,35,108,40,109,110,111,112,113,114,115,116],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127,128,129,130,131,132,133,134,135,35,29,136,137,138,139,140,141,142],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":156,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[149,152,153],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[157,158,159,160,161,162,163,38,164,165,166,167,168,169,170,43,171,172,35,173],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,38,208],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":220,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[216,219],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},[221,222,223,224,225,187,226,196,197,227,228,229,230,38,231,40,232],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":247,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[240,243,244],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":245,"categoryName":246,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[248,249,250,251,252,253,254,255,189,256,199,29,257,258,259,260,261,169,262,35,263,264,265,266,267,114,268],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]