movementkit-cli 1.0.1 → 1.0.3

package/kits/engineer/.claude/commands/plan.md

@@ -0,0 +1,103 @@
+# /plan - Architecture Planning for Movement dApps
+
+Plan the architecture for a Movement blockchain dApp based on the user's requirements.
+
+## Workflow
+
+### Step 1: Analyze Requirements
+Carefully analyze the user's request: $ARGUMENTS
+
+Identify:
+- **Core functionality** - What does the dApp need to do?
+- **Smart contract requirements** - What on-chain logic is needed?
+- **Frontend requirements** - What UI/UX is needed?
+- **Integration points** - Wallets, oracles, other contracts?
+
+### Step 2: Research Phase
+Read the Move language reference for correct syntax:
+```bash
+cat docs/MOVE_LANGUAGE_REFERENCE.md
+```
+
+### Step 3: Create Planning Artifacts
+Create a timestamped plan directory: `plans/YYYYMMDD-HHmm-{plan-name}/`
+
+Generate the following files:
+1. `00-overview.md` - Executive summary and high-level architecture
+2. `01-contracts.md` - Move smart contract design with modules, structs, functions
+3. `02-frontend.md` - React frontend design with components and state management
+4. `03-testing.md` - Test strategy with unit, integration, and e2e tests
+5. `04-deployment.md` - Deployment plan for testnet and mainnet
+
+### Step 4: Validate Plan
+Ensure the plan addresses:
+- [ ] All user requirements are covered
+- [ ] Move contract security best practices
+- [ ] Proper resource management
+- [ ] Event emission for state changes
+- [ ] Error handling strategy
+- [ ] Gas optimization considerations
+
+### Step 5: Present Plan Summary
+Present a concise summary to the user with:
+- Architecture diagram (Mermaid)
+- Key components and their responsibilities
+- Estimated implementation time
+- Potential risks and mitigations
+- Next steps (suggest `/cook` to start implementation)
+
+## Complexity Modes
+
+### /plan:fast
+For simple dApps (single contract, basic CRUD):
+- Skip detailed research phase
+- Use standard patterns
+- Minimal documentation
+
+### /plan:hard
+For complex dApps (multiple contracts, complex logic):
+- Deep dive into security considerations
+- Comprehensive documentation
+- Formal verification recommendations
+
+## Output Format
+
+```markdown
+# Plan: {Plan Name}
+Created: {timestamp}
+
+## Overview
+{Brief description of the dApp}
+
+## Architecture
+{Mermaid diagram}
+
+## Components
+### Smart Contracts
+- {Contract 1}: {Description}
+
+### Frontend
+- {Component 1}: {Description}
+- {State management approach}
+
+## Implementation Order
+1. {First task}
+2. {Second task}
+...
+
+## Estimated Time
+- Contracts: {X} hours
+- Frontend: {X} hours
+- Testing: {X} hours
+- Total: {X} hours
+
+## Next Steps
+Run `/cook` to start implementation
+```
+
+## Success Criteria
+- Plan created in <5 minutes
+- All requirements addressed
+- Clear implementation path
+- Security considerations documented
+

package/kits/engineer/.claude/commands/review.md

@@ -0,0 +1,98 @@
+# /review - Code Quality and Security Auditing
+
+Perform comprehensive code review and security audit for the Movement dApp.
+
+## Workflow
+
+### Step 1: Move Contract Security Audit
+
+Check for common vulnerabilities:
+
+#### Resource Safety
+- [ ] No resource leaks (resources properly moved/destroyed)
+- [ ] Proper use of `move_to`, `move_from`, `borrow_global`
+- [ ] No dangling references
+
+#### Access Control
+- [ ] Signer validation on privileged functions
+- [ ] Proper capability checks
+- [ ] Admin functions protected
+
+#### Arithmetic Safety
+- [ ] No integer overflow/underflow
+- [ ] Safe division (no divide by zero)
+- [ ] Proper use of checked arithmetic
+
+#### Reentrancy Protection
+- [ ] State changes before external calls
+- [ ] No recursive vulnerabilities
+
+#### Event Emission
+- [ ] All state changes emit events
+- [ ] Events contain sufficient information
+
+#### Gas Optimization
+- [ ] No unbounded loops
+- [ ] Efficient data structures
+- [ ] Minimal storage operations
+
+### Step 2: Frontend Security Audit
+
+Check for:
+- [ ] No hardcoded secrets
+- [ ] Proper wallet connection handling
+- [ ] Transaction signing validation
+- [ ] XSS prevention
+- [ ] Secure storage of user data
+
+### Step 3: Generate Review Report
+
+```markdown
+# 🔍 Code Review Report
+
+## Security Audit
+
+### Critical Issues (Must Fix)
+| ID | Location | Issue | Recommendation |
+|----|----------|-------|----------------|
+| C1 | contracts/sources/main.move:42 | Issue desc | Fix recommendation |
+
+### High Priority Issues
+| ID | Location | Issue | Recommendation |
+|----|----------|-------|----------------|
+
+### Medium Priority Issues
+| ID | Location | Issue | Recommendation |
+|----|----------|-------|----------------|
+
+### Low Priority Issues
+| ID | Location | Issue | Recommendation |
+|----|----------|-------|----------------|
+
+## Code Quality
+### Contracts
+- Style compliance: ✅/❌
+- Documentation: ✅/❌
+- Test coverage: {percentage}%
+
+## Approval Status
+- [ ] Ready for testnet deployment
+- [ ] Ready for mainnet deployment
+```
+
+## Sub-Commands
+
+### /review:security
+Focus only on security audit
+
+### /review:quality
+Focus only on code quality
+
+### /review:contracts
+Review only Move contracts
+
+## Success Criteria
+- Review completed in <2 minutes
+- All critical issues identified
+- Clear remediation steps provided
+

package/kits/engineer/.claude/commands/test.md

@@ -0,0 +1,92 @@
+# /test - Comprehensive Test Generation and Execution
+
+Generate and run comprehensive tests for the Movement dApp.
+
+## Workflow
+
+### Step 1: Analyze Codebase
+Scan the project to identify:
+- Move contracts in `contracts/sources/`
+- Frontend code in `frontend/src/`
+- Existing tests
+
+### Step 2: Generate Move Tests
+For each Move module, generate tests in `contracts/tests/`:
+
+```move
+#[test_only]
+module test_module_name {
+    use std::signer;
+    use aptos_framework::account;
+
+    #[test(account = @0x1)]
+    fun test_function_name(account: &signer) {
+        // Setup
+        // Action
+        // Assert
+    }
+
+    #[test]
+    #[expected_failure(abort_code = ERROR_CODE)]
+    fun test_failure_case() {
+        // Test error conditions
+    }
+}
+```
+
+### Step 3: Run All Tests
+
+1. **Move Tests**
+   ```bash
+   cd contracts && movement move test
+   ```
+
+2. **Frontend Tests**
+   ```bash
+   cd frontend && npm test
+   ```
+
+### Step 4: Generate Coverage Report
+Analyze test coverage and identify gaps:
+- Line coverage
+- Branch coverage
+- Function coverage
+
+### Step 5: Report Results
+```markdown
+# 🧪 Test Results
+
+## Move Contract Tests
+| Module | Tests | Passed | Failed | Coverage |
+|--------|-------|--------|--------|----------|
+| module_name | 10 | 10 | 0 | 95% |
+
+## Frontend Tests
+| Component | Tests | Passed | Failed | Coverage |
+|-----------|-------|--------|--------|----------|
+| ComponentName | 8 | 8 | 0 | 88% |
+
+## Overall Coverage: 91%
+
+## Recommendations
+- Add tests for {uncovered areas}
+- Consider edge cases for {specific functions}
+```
+
+## Sub-Commands
+
+### /test:contracts
+Run only Move contract tests
+
+### /test:frontend
+Run only frontend tests
+
+### /test:coverage
+Generate detailed coverage report
+
+## Success Criteria
+- All tests generated in <3 minutes
+- All tests passing
+- Coverage >90%
+- No security vulnerabilities in test code
+

package/kits/engineer/.claude/commands/watzup.md

@@ -0,0 +1,100 @@
+# /watzup - Project Status Check
+
+Quick status check for the Movement dApp project.
+
+## Workflow
+
+### Step 1: Scan Project Structure
+
+Check for existence and status of:
+- `contracts/` - Move smart contracts
+- `frontend/` - React frontend
+- `plans/` - Architecture plans
+- `docs/` - Documentation
+
+### Step 2: Analyze Each Component
+
+#### Contracts Status
+```bash
+ls -la contracts/sources/*.move 2>/dev/null | wc -l
+ls -la contracts/tests/*.move 2>/dev/null | wc -l
+```
+
+Check:
+- Number of Move modules
+- Number of test files
+- Last modified dates
+- Compilation status
+
+#### Frontend Status
+```bash
+ls -la frontend/src/**/*.tsx 2>/dev/null | wc -l
+```
+
+Check:
+- Number of React components
+- Dependencies installed
+- Build status
+
+### Step 3: Check Test Status
+
+Run quick test check:
+```bash
+cd contracts && movement move test --coverage 2>&1 | tail -5
+cd ../frontend && npm test 2>&1 | tail -5
+```
+
+### Step 4: Check Deployment Status
+
+Look for deployment records:
+- Deployed contract addresses
+- Network (testnet/mainnet)
+- Last deployment date
+
+### Step 5: Generate Status Report
+
+```markdown
+# 📊 Project Status: {Project Name}
+
+## Overview
+| Component | Status | Files | Coverage | Last Updated |
+|-----------|--------|-------|----------|--------------|
+| Contracts | ✅/⚠️/❌ | {n} | {%} | {date} |
+| Frontend | ✅/⚠️/❌ | {n} | {%} | {date} |
+| Tests | ✅/⚠️/❌ | {n} | {%} | {date} |
+| Docs | ✅/⚠️/❌ | {n} | - | {date} |
+
+## Deployment Status
+| Network | Status | Address | Last Deployed |
+|---------|--------|---------|---------------|
+| Testnet | ✅/❌ | 0x... | {date} |
+| Mainnet | ✅/❌ | 0x... | {date} |
+
+## Recent Activity
+- {Recent change 1}
+- {Recent change 2}
+- {Recent change 3}
+
+## Recommendations
+1. {Recommendation based on status}
+2. {Next logical step}
+
+## Quick Actions
+- `/cook` - Generate missing components
+- `/test` - Run all tests
+- `/review` - Security audit
+- `/deploy-full` - Deploy to network
+```
+
+## Status Indicators
+
+- ✅ **Complete** - Component is fully implemented and tested
+- ⚠️ **In Progress** - Component exists but incomplete
+- ❌ **Missing** - Component does not exist
+- 🔄 **Needs Update** - Component is outdated
+
+## Success Criteria
+- Status check completed in <30 seconds
+- Accurate representation of project state
+- Clear next steps provided
+

package/kits/engineer/.claude/workflows/development-rules.md

@@ -0,0 +1,110 @@
+# Development Rules for Movement dApps
+
+Strict rules to follow when developing dApps on the Movement blockchain.
+
+## Move Smart Contract Rules
+
+### 1. Always Read the Reference First
+```
+BEFORE generating any Move code, ALWAYS read:
+docs/MOVE_LANGUAGE_REFERENCE.md
+```
+
+### 2. Resource Safety
+- Never leave resources dangling
+- Always use `move_to`, `move_from`, `borrow_global`, `borrow_global_mut` correctly
+- Resources with `key` ability must be stored in global storage
+
+### 3. Access Control
+- Always validate signers on privileged functions
+- Use `signer::address_of(account)` to get caller address
+- Check ownership before modifying resources
+
+### 4. Error Handling
+- Define error constants at module top
+- Use descriptive names: `E_NOT_AUTHORIZED`, `E_INSUFFICIENT_BALANCE`
+- Use `assert!` with error codes
+
+### 5. Events
+- Emit events for ALL state changes
+- Use `#[event]` attribute for event structs
+- Include relevant data in events
+
+### 6. Testing
+- Write tests for every public function
+- Test error conditions with `#[expected_failure]`
+- Aim for >90% coverage
+
+## TypeScript Backend Rules
+
+### 1. Type Safety
+- Use strict TypeScript (`strict: true`)
+- No `any` types
+- Define interfaces for all data structures
+
+### 2. Movement SDK Usage
+- Use `@aptos-labs/ts-sdk` for blockchain interaction
+- Configure for Movement network endpoints
+- Handle transaction errors properly
+
+### 3. Error Handling
+- Wrap all async operations in try-catch
+- Return consistent error responses
+- Log errors for debugging
+
+### 4. Configuration
+- Use environment variables for secrets
+- Never hardcode private keys
+- Use `.env` files with `.env.example` templates
+
+## React Frontend Rules
+
+### 1. Wallet Integration
+- Use `@aptos-labs/wallet-adapter-react`
+- Handle connection states properly
+- Show clear feedback for transactions
+
+### 2. State Management
+- Use React hooks for local state
+- Use context for global state (wallet, config)
+- Avoid prop drilling
+
+### 3. Error Handling
+- Show user-friendly error messages
+- Handle wallet disconnection gracefully
+- Provide transaction status feedback
+
+### 4. Security
+- Never store private keys in frontend
+- Validate all user inputs
+- Use HTTPS for API calls
+
+## Network Configuration
+
+### Testnet
+```typescript
+const TESTNET_CONFIG = {
+  fullnode: "https://full.testnet.movementinfra.xyz/v1",
+  chainId: 250,
+  faucet: "https://faucet.movementnetwork.xyz/",
+  explorer: "https://explorer.movementnetwork.xyz/?network=testnet"
+};
+```
+
+### Mainnet
+```typescript
+const MAINNET_CONFIG = {
+  fullnode: "https://full.mainnet.movementinfra.xyz/v1",
+  chainId: 126,
+  explorer: "https://explorer.movementnetwork.xyz/?network=mainnet"
+};
+```
+
+## Code Quality Standards
+
+1. **Formatting**: Use consistent formatting (Prettier for TS, Move formatter for Move)
+2. **Comments**: Document complex logic, public APIs, and non-obvious code
+3. **Naming**: Use descriptive names, follow language conventions
+4. **Testing**: Write tests before or alongside code
+5. **Review**: Always run `/review` before deployment
+

package/kits/engineer/.claude/workflows/primary-workflow.md

@@ -0,0 +1,95 @@
+# Primary Workflow for Movement dApp Development
+
+This document outlines the primary workflow for building dApps on the Movement blockchain.
+
+## Workflow Overview
+
+```
+/plan → /cook → /test → /review → /deploy-full
+```
+
+## Phase 1: Planning (/plan)
+
+1. **Analyze Requirements**
+   - Understand user's dApp requirements
+   - Identify on-chain vs off-chain logic
+   - Determine wallet integration needs
+
+2. **Research**
+   - Read `docs/MOVE_LANGUAGE_REFERENCE.md`
+   - Check existing patterns in codebase
+   - Review Movement network specifics
+
+3. **Create Plan**
+   - Generate architecture documents in `plans/`
+   - Create Mermaid diagrams for visualization
+   - Define implementation order
+
+## Phase 2: Implementation (/cook)
+
+1. **Smart Contracts** (`/cook:contracts`)
+   - Generate Move modules in `contracts/sources/`
+   - Create unit tests in `contracts/tests/`
+   - Compile and verify
+
+2. **Frontend** (`/cook:frontend`)
+   - Generate React components in `frontend/src/`
+   - Implement wallet integration
+   - Create custom hooks for contract interaction
+
+## Phase 3: Testing (/test)
+
+1. **Unit Tests**
+   - Move contract tests
+   - Frontend component tests
+
+2. **Integration Tests**
+   - Contract interaction tests
+   - E2E wallet flow tests
+
+3. **Coverage Analysis**
+   - Target >90% coverage
+   - Identify gaps
+   - Add missing tests
+
+## Phase 4: Review (/review)
+
+1. **Security Audit**
+   - Move contract vulnerabilities
+   - Frontend security concerns
+
+2. **Code Quality**
+   - Style compliance
+   - Documentation completeness
+   - Best practices adherence
+
+3. **Performance Review**
+   - Gas optimization
+   - Frontend bundle size
+
+## Phase 5: Deployment (/deploy-full)
+
+1. **Testnet Deployment**
+   - Deploy contracts to Movement testnet
+   - Verify on Explorer
+   - Test all functionality
+
+2. **Mainnet Deployment**
+   - Final security review
+   - Deploy to Movement mainnet
+   - Monitor and verify
+
+## Quick Reference
+
+| Phase | Command | Output |
+|-------|---------|--------|
+| Plan | `/plan` | Architecture docs in `plans/` |
+| Build | `/cook` | Code in `contracts/`, `frontend/` |
+| Test | `/test` | Test results and coverage |
+| Review | `/review` | Security and quality report |
+| Deploy | `/deploy-full` | Deployed contracts and apps |
+
+## Status Check
+
+Use `/watzup` at any time to check project status and get recommendations for next steps.
+

package/kits/engineer/CLAUDE.md

@@ -0,0 +1,105 @@
+# CLAUDE.md - Movement Kit
+
+This file provides guidance to Claude Code (claude.ai/code) when building dApps on the Movement blockchain.
+
+## Role & Responsibilities
+
+Your role is to analyze user requirements for Movement blockchain dApps, generate production-ready code using Move smart contracts and React frontend with wallet integration.
+
+## Movement Network Context
+
+**Network Endpoints:**
+- Mainnet: `https://full.mainnet.movementinfra.xyz/v1` (Chain ID: 126)
+- Testnet: `https://full.testnet.movementinfra.xyz/v1` (Chain ID: 250)
+- Faucet: `https://faucet.movementnetwork.xyz/`
+- Explorer: `https://explorer.movementnetwork.xyz/`
+
+**Key Technologies:**
+- Smart Contracts: Move language (Aptos-compatible)
+- TypeScript SDK: `@aptos-labs/ts-sdk`
+- Wallet Integration: `@aptos-labs/wallet-adapter-react`
+- CLI: `movement` (Aptos-compatible commands)
+
+## Commands
+
+Slash commands for dApp development:
+
+| Command | Description |
+|---------|-------------|
+| `/plan` | Create architecture plan for a dApp |
+| `/cook` | Generate full dApp code (contracts + frontend) |
+| `/cook:contracts` | Generate Move smart contracts only |
+| `/cook:frontend` | Generate React frontend only |
+| `/test` | Generate and run comprehensive tests |
+| `/review` | Perform security audit and code review |
+| `/deploy-smart-contract` | Deploy Move smart contracts to Movement Network |
+| `/deploy-full` | Deploy complete dApp to testnet or mainnet |
+| `/watzup` | Check project status |
+| `/docs:init` | Initialize documentation structure |
+| `/docs:generate` | Auto-generate API and contract docs |
+
+## Workflows
+
+- Primary workflow: `./.claude/workflows/primary-workflow.md`
+- Development rules: `./.claude/workflows/development-rules.md`
+- Commands reference: `./.claude/commands/*.md`
+
+## Project Structure
+
+```
+movement-kit/
+├── CLAUDE.md                    # This file
+├── contracts/                   # Move smart contracts
+│   ├── Move.toml
+│   ├── sources/                 # .move source files
+│   └── tests/                   # Move unit tests
+├── frontend/                    # React frontend
+│   ├── package.json
+│   ├── src/
+│   │   ├── App.tsx
+│   │   ├── components/
+│   │   ├── hooks/
+│   │   └── contexts/
+│   └── tests/
+├── docs/                        # Documentation
+│   ├── MOVE_LANGUAGE_REFERENCE.md
+│   └── contracts/
+├── plans/                       # Architecture plans
+└── templates/                   # Code templates
+```
+
+## Development Principles
+
+1. **Security First**: All contracts must follow Move security best practices
+2. **Type Safety**: Use strict TypeScript with no `any` types
+3. **Test Coverage**: Target >90% code coverage
+4. **Event Emission**: Emit events for all state changes
+5. **Error Handling**: Use descriptive error codes in contracts
+
+## Critical Instructions
+
+**IMPORTANT:** Always read `docs/MOVE_LANGUAGE_REFERENCE.md` before generating Move contracts
+**IMPORTANT:** Use Movement-specific network configuration (not generic Aptos)
+**IMPORTANT:** Test on Movement testnet before mainnet deployment
+**IMPORTANT:** Follow the command workflows in `.claude/commands/`
+**IMPORTANT:** For dates, use `bash -c 'date +%y%m%d'` command
+
+## Quick Start
+
+```bash
+# Create a new dApp
+/plan Create a simple counter dApp
+
+# Generate the code
+/cook
+
+# Test everything
+/test
+
+# Review for security
+/review
+
+# Deploy to testnet
+/deploy-full:testnet
+```
+