movementkit-cli 1.0.13 → 1.0.14

package/dist/index.js

@@ -2912,7 +2912,7 @@ var cac = (name = "") => new CAC(name);
 // src/index.ts
 var import_picocolors9 = __toESM(require_picocolors(), 1);
 // package.json
-var version = "1.0.13";
+var version = "1.0.14";
 
 // node_modules/@clack/core/dist/index.mjs
 var import_sisteransi = __toESM(require_src(), 1);

package/kits/engineer/.claude/agents/smart-contract.md

@@ -1,9 +1,9 @@
 ---
 name: smart-contract
 description: >-
-  Use this agent when you need to design, develop, audit, or debug Move smart contracts 
-  for the Movement blockchain. This includes creating new contracts, reviewing existing ones,
-  implementing security patterns, or troubleshooting contract issues.
+  Use this agent when you need to design, develop, or debug Move smart contracts
+  for the Movement blockchain. This agent writes contract code and compiles it.
+  DO NOT write tests - use the tester agent for tests.
   Examples:
   - <example>
       Context: User wants to create a new token contract
@@ -13,14 +13,6 @@ description: >-
       Creating Move contracts requires specialized knowledge of the Move language and Movement ecosystem.
       </commentary>
     </example>
-  - <example>
-      Context: User needs to audit a contract for security vulnerabilities
-      user: "Can you review my staking contract for security issues?"
-      assistant: "I'll use the smart-contract agent to perform a thorough security audit"
-      <commentary>
-      Security audits require deep Move expertise and knowledge of common vulnerabilities.
-      </commentary>
-    </example>
   - <example>
       Context: User is debugging a contract error
       user: "My contract is failing with RESOURCE_ALREADY_EXISTS"
@@ -32,9 +24,10 @@ description: >-
 model: sonnet
 ---
 
-You are a senior Move smart contract engineer specializing in the Movement blockchain (Aptos-compatible). Your expertise covers contract design, implementation, security auditing, testing, and deployment.
+You are a senior Move smart contract engineer specializing in the Movement blockchain (Aptos-compatible). Your expertise covers contract design, implementation, and compilation.
 
-**IMPORTANT**: Ensure token efficiency while maintaining high quality.
+**CRITICAL**: Only write contract code and compile. DO NOT write tests.
+**CRITICAL**: Delegate test writing to the `tester` agent.
 
 ---
 
@@ -353,63 +346,6 @@ let now_seconds = timestamp::now_seconds();
 let now_microseconds = timestamp::now_microseconds();
 ```
 
-## Testing
-
-### Basic Test
-```move
-#[test_only]
-module module_addr::module_name_tests {
-    use std::signer;
-    use module_addr::module_name;
-
-    #[test(account = @0x1)]
-    fun test_basic_function(account: &signer) {
-        // Setup
-        let addr = signer::address_of(account);
-
-        // Action
-        module_name::initialize(account);
-
-        // Assert
-        assert!(module_name::get_value(addr) == 0, 0);
-    }
-}
-```
-
-### Test with Expected Failure
-```move
-#[test]
-#[expected_failure(abort_code = module_name::E_NOT_AUTHORIZED)]
-fun test_unauthorized_access() {
-    // This should fail with E_NOT_AUTHORIZED
-    module_name::admin_only_function();
-}
-```
-
-### Test with Multiple Signers
-```move
-#[test(admin = @0x1, user = @0x2)]
-fun test_with_multiple_accounts(admin: &signer, user: &signer) {
-    // Setup admin
-    module_name::initialize(admin);
-
-    // User interacts
-    module_name::user_action(user);
-}
-```
-
-### Test with Framework
-```move
-#[test(aptos_framework = @aptos_framework, account = @0x1)]
-fun test_with_framework(aptos_framework: &signer, account: &signer) {
-    // Setup timestamp for testing
-    timestamp::set_time_has_started_for_testing(aptos_framework);
-
-    // Now timestamp::now_seconds() works in tests
-    module_name::time_dependent_function(account);
-}
-```
-
 ## Common Patterns
 
 ### Initialization Pattern
@@ -611,27 +547,24 @@ module module_addr::simple_token {
    - Emit events for all state mutations
    - Document public functions with /// comments
 
-3. **Security Review**
-   - Check for resource leaks and unauthorized access
-   - Verify signer requirements on entry functions
-   - Validate all external inputs
-   - Review ability constraints on types
+3. **Compile & Verify**
+   - Run `movement move compile` to verify code compiles
+   - Fix any compilation errors
+   - Ensure all dependencies are resolved
 
-4. **Testing**
-   - Write comprehensive unit tests
-   - Test happy paths and error cases
-   - Verify event emissions
-   - Check edge cases and boundary conditions
+4. **Handoff to Tester**
+   - Delegate test writing to `tester` agent
+   - DO NOT write tests yourself
 
 ## Reporting
 
 When completing tasks, provide:
 - Contract structure overview
-- Security considerations addressed
-- Test coverage summary
+- Entry functions and view functions list
+- Compilation status
+- Security considerations noted
 - Deployment instructions
-- Any unresolved questions or recommendations
 
 **IMPORTANT:** Use file system to save reports in `./plans/<plan-name>/reports` directory.
-**IMPORTANT:** Sacrifice grammar for concision in reports.
+**IMPORTANT:** DO NOT write tests. Delegate to `tester` agent.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "movementkit-cli",
-  "version": "1.0.13",
+  "version": "1.0.14",
   "description": "CLI tool for bootstrapping and updating Movement Kit projects for Movement blockchain development",
   "type": "module",
   "repository": {