movementkit-cli 1.0.1 → 1.0.4

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

@@ -0,0 +1,118 @@
+# /cook - Full dApp Code Generation
+
+Generate complete production-ready code for a Movement blockchain dApp.
+
+## Prerequisites
+
+### Install Movement CLI
+
+Before generating code, ensure the Movement CLI is installed. See [Movement CLI docs](https://docs.movementnetwork.xyz/devs/movementcli) for details.
+
+#### Quick Install (Testnet - with Move 2 support)
+
+**macOS (Apple Silicon/M-series):**
+```bash
+curl -LO https://github.com/movementlabsxyz/homebrew-movement-cli/releases/download/bypass-homebrew/movement-move2-testnet-macos-arm64.tar.gz && mkdir -p temp_extract && tar -xzf movement-move2-testnet-macos-arm64.tar.gz -C temp_extract && chmod +x temp_extract/movement && sudo mv temp_extract/movement /usr/local/bin/movement && rm -rf temp_extract movement-move2-testnet-macos-arm64.tar.gz
+```
+
+**macOS (Intel):**
+```bash
+curl -LO https://github.com/movementlabsxyz/homebrew-movement-cli/releases/download/bypass-homebrew/movement-move2-testnet-macos-x86_64.tar.gz && mkdir -p temp_extract && tar -xzf movement-move2-testnet-macos-x86_64.tar.gz -C temp_extract && chmod +x temp_extract/movement && sudo mv temp_extract/movement /usr/local/bin/movement && rm -rf temp_extract movement-move2-testnet-macos-x86_64.tar.gz
+```
+
+**Linux (x86_64):**
+```bash
+curl -LO https://github.com/movementlabsxyz/homebrew-movement-cli/releases/download/bypass-homebrew/movement-move2-testnet-linux-x86_64.tar.gz && mkdir -p temp_extract && tar -xzf movement-move2-testnet-linux-x86_64.tar.gz -C temp_extract && chmod +x temp_extract/movement && sudo mv temp_extract/movement /usr/local/bin/movement && rm -rf temp_extract movement-move2-testnet-linux-x86_64.tar.gz
+```
+
+**Verify installation:**
+```bash
+movement --version
+```
+
+### Initialize Account (if not done)
+```bash
+movement init --network testnet
+```
+
+This creates a `.movement/config.yaml` with your account credentials.
+
+### Get Testnet Tokens
+Visit https://faucet.movementnetwork.xyz/ to get testnet MOVE tokens.
+
+## Workflow
+
+This command orchestrates the generation of a complete dApp:
+
+### Phase 1: Research & Planning (if no plan exists)
+Check for existing plans and read Move language reference:
+```bash
+cat docs/MOVE_LANGUAGE_REFERENCE.md
+ls plans/
+```
+
+### Phase 2: Smart Contract Implementation
+Generate in `contracts/`:
+- `Move.toml` - Package manifest with dependencies
+- `sources/*.move` - Move module source files
+- `tests/*.move` - Move unit tests
+
+### Phase 3: Frontend Implementation
+Generate in `frontend/`:
+- `package.json` - React dependencies
+- `src/App.tsx` - Main application component
+- `src/components/*.tsx` - UI components
+- `src/hooks/*.ts` - Custom React hooks
+- `src/contexts/*.tsx` - React contexts (wallet, etc.)
+- `tests/*.test.tsx` - Frontend tests
+
+### Phase 4: Testing
+Ensure:
+- Move unit tests pass
+- Frontend tests pass
+- Coverage >90%
+
+### Phase 5: Code Review
+Check:
+- Move security best practices
+- No vulnerabilities
+- Code quality standards
+- Documentation completeness
+
+## Sub-Commands
+
+### /cook:contracts
+Generate only Move smart contracts
+
+### /cook:frontend
+Generate only React frontend
+
+## Output Summary
+
+After completion, display:
+```markdown
+# 🍳 Cook Complete!
+
+## Generated Files
+- Contracts: {count} files
+- Frontend: {count} files
+- Tests: {count} files
+
+## Test Results
+- Move tests: ✅ {passed}/{total}
+- Frontend tests: ✅ {passed}/{total}
+- Coverage: {percentage}%
+
+## Next Steps
+1. Review generated code
+2. Run `/test` for comprehensive testing
+3. Run `/review` for security audit
+4. Run `/deploy-full` to deploy to testnet
+```
+
+## Success Criteria
+- Contracts generated in <3 minutes
+- Frontend generated in <3 minutes
+- All tests passing
+- Coverage >90%
+

package/kits/engineer/.claude/commands/deploy-full.md

@@ -0,0 +1,158 @@
+# /deploy-full - Full Deployment to Movement Network
+
+Deploy the complete dApp to Movement testnet or mainnet.
+
+## Prerequisites
+
+1. **Movement CLI installed** - See [Movement CLI docs](https://docs.movementnetwork.xyz/devs/movementcli)
+2. **Wallet configured** in `.movement/config.yaml`
+3. **Sufficient tokens** from [faucet](https://faucet.movementnetwork.xyz/) (for testnet)
+
+## Workflow
+
+### Step 1: Pre-Deployment Checks
+
+1. **Verify all tests pass**
+   ```bash
+   cd contracts && movement move test
+   cd ../frontend && npm test
+   ```
+
+2. **Run security review**
+   Execute `/review` command and ensure no critical issues
+
+3. **Verify Movement CLI configuration**
+   Check `.movement/config.yaml` is configured for the target network:
+   ```yaml
+   ---
+   profiles:
+     default:
+       network: Custom
+       private_key: "0xYOUR_PRIVATE_KEY"
+       public_key: "0xYOUR_PUBLIC_KEY"
+       account: "YOUR_ACCOUNT_ADDRESS"
+       rest_url: "https://full.testnet.movementinfra.xyz/v1"  # or mainnet
+       faucet_url: "https://faucet.testnet.movementnetwork.xyz/"
+   ```
+
+4. **Configure Move.toml addresses**
+   Add your deployment address to `contracts/Move.toml`:
+   ```toml
+   [addresses]
+   module_addr = "YOUR_ACCOUNT_ADDRESS"
+   ```
+
+### Step 2: Deploy Smart Contracts
+
+Use `/deploy-smart-contract` command or run manually:
+
+#### Testnet Deployment
+```bash
+cd contracts
+movement move publish --named-addresses module_addr=default
+```
+
+#### Mainnet Deployment
+```bash
+cd contracts
+movement move publish \
+  --url https://full.mainnet.movementinfra.xyz/v1 \
+  --named-addresses module_addr=default
+```
+
+When prompted:
+```
+Do you want to submit this transaction? [Y/n]
+```
+Type `Y` and press **Enter** to confirm.
+
+> **Important:** Ensure you have sufficient tokens from the faucet before proceeding.
+
+### Step 3: Verify Contract Deployment
+
+1. Get deployed address and transaction hash from output
+2. Verify on Movement Explorer:
+   - Testnet: `https://explorer.movementnetwork.xyz/?network=testnet`
+   - Mainnet: `https://explorer.movementnetwork.xyz/?network=mainnet`
+
+### Step 4: Update Frontend Configuration
+
+Update contract address in `frontend/.env` so the frontend can interact with the deployed contract:
+
+```bash
+# frontend/.env
+VITE_MODULE_ADDRESS=<YOUR_DEPLOYED_CONTRACT_ADDRESS>
+VITE_NETWORK=testnet  # or mainnet
+VITE_NODE_URL=https://full.testnet.movementinfra.xyz/v1  # or mainnet URL
+```
+
+### Step 5: Deploy Frontend
+
+```bash
+cd frontend
+npm run build
+# Deploy to hosting service (Vercel, Netlify, etc.)
+```
+
+### Step 6: Post-Deployment Verification
+
+1. Test contract interactions via Explorer
+2. Test frontend wallet connection
+3. Execute sample transactions
+
+## Sub-Commands
+
+### /deploy-full:testnet
+Deploy complete dApp to testnet
+
+### /deploy-full:mainnet
+Deploy complete dApp to mainnet (requires additional confirmation)
+
+### /deploy-full:contracts
+Deploy only smart contracts (see `/deploy-smart-contract`)
+
+## Deployment Report
+
+```markdown
+# 🚀 Deployment Complete!
+
+## Network: {Testnet/Mainnet}
+## Timestamp: {ISO timestamp}
+
+## Smart Contracts
+| Module | Address | Tx Hash |
+|--------|---------|---------|
+| module_name | 0x... | 0x... |
+
+## Verification Links
+- Explorer: {link}
+- Contract: {link}
+
+## Configuration Updates
+- Frontend config updated: ✅
+
+## Post-Deployment Tests
+- Contract interaction: ✅
+- Frontend connection: ✅
+
+## Next Steps
+1. Monitor contract activity on Explorer
+2. Set up alerts for critical events
+3. Document deployment for team
+```
+
+## Safety Checks
+
+### Mainnet Deployment Requires:
+- [ ] All tests passing
+- [ ] Security review completed with no critical issues
+- [ ] Testnet deployment successful
+- [ ] Manual confirmation from user
+- [ ] Backup of deployment keys
+
+## Success Criteria
+- Deployment completed in <5 minutes
+- All contracts verified on Explorer
+- Configuration files updated
+- Post-deployment tests passing
+

package/kits/engineer/.claude/commands/deploy-smart-contract.md

@@ -0,0 +1,177 @@
+# /deploy-smart-contract - Deploy Move Smart Contracts
+
+Deploy Move smart contracts to the Movement Network (testnet or mainnet).
+
+## Prerequisites
+
+1. **Movement CLI installed** - See [Movement CLI docs](https://docs.movementnetwork.xyz/devs/movementcli)
+2. **Wallet configured** with private key
+3. **Sufficient tokens** from [faucet](https://faucet.movementnetwork.xyz/) (for testnet)
+
+## Workflow
+
+### Step 1: Verify Configuration
+
+Check your `.movement/config.yaml` is configured for the target network:
+
+#### Testnet Configuration
+```yaml
+---
+profiles:
+  default:
+    network: Custom
+    private_key: "0xYOUR_PRIVATE_KEY"
+    public_key: "0xYOUR_PUBLIC_KEY"
+    account: "YOUR_ACCOUNT_ADDRESS"
+    rest_url: "https://full.testnet.movementinfra.xyz/v1"
+    faucet_url: "https://faucet.testnet.movementnetwork.xyz/"
+```
+
+#### Mainnet Configuration
+```yaml
+---
+profiles:
+  default:
+    network: Custom
+    private_key: "0xYOUR_PRIVATE_KEY"
+    public_key: "0xYOUR_PUBLIC_KEY"
+    account: "YOUR_ACCOUNT_ADDRESS"
+    rest_url: "https://full.mainnet.movementinfra.xyz/v1"
+```
+
+### Step 2: Configure Move.toml
+
+Add your deployment address to `contracts/Move.toml`:
+
+```toml
+[addresses]
+module_addr = "YOUR_ACCOUNT_ADDRESS"
+```
+
+Or use `_` for dynamic address assignment during deployment:
+```toml
+[addresses]
+module_addr = "_"
+```
+
+### Step 3: Compile Contracts
+
+```bash
+cd contracts
+movement move compile
+```
+
+Verify compilation succeeds without errors.
+
+### Step 4: Run Tests
+
+```bash
+movement move test
+```
+
+Ensure all tests pass before deployment.
+
+### Step 5: Deploy to Network
+
+#### Testnet Deployment
+```bash
+cd contracts
+movement move publish --named-addresses module_addr=default
+```
+
+#### Mainnet Deployment
+```bash
+cd contracts
+movement move publish \
+  --url https://full.mainnet.movementinfra.xyz/v1 \
+  --named-addresses module_addr=default
+```
+
+### Step 6: Confirm Transaction
+
+You'll be prompted:
+```
+Do you want to submit this transaction? [Y/n]
+```
+
+Type `Y` and press **Enter** to confirm.
+
+> **Note:** Ensure you have sufficient tokens from the faucet before proceeding.
+
+### Step 7: Verify Deployment
+
+1. Note the transaction hash from the output
+2. Verify on Movement Explorer:
+   - Testnet: `https://explorer.movementnetwork.xyz/?network=testnet`
+   - Mainnet: `https://explorer.movementnetwork.xyz/?network=mainnet`
+
+### Step 8: Update Frontend Configuration
+
+Update the contract address in `frontend/.env` so the frontend can interact with the deployed contract:
+
+```bash
+# frontend/.env
+VITE_MODULE_ADDRESS=<YOUR_DEPLOYED_CONTRACT_ADDRESS>
+VITE_NETWORK=testnet  # or mainnet
+VITE_NODE_URL=https://full.testnet.movementinfra.xyz/v1  # or mainnet URL
+```
+
+Example:
+```bash
+VITE_MODULE_ADDRESS=0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
+VITE_NETWORK=testnet
+VITE_NODE_URL=https://full.testnet.movementinfra.xyz/v1
+```
+
+> **Note:** After updating `.env`, restart the frontend dev server for changes to take effect.
+
+## Sub-Commands
+
+### /deploy-smart-contract:testnet
+Deploy to testnet only.
+
+### /deploy-smart-contract:mainnet
+Deploy to mainnet (requires additional confirmation).
+
+### /deploy-smart-contract:verify
+Verify an existing deployment on the Explorer.
+
+## Deployment Report
+
+```markdown
+# 📜 Smart Contract Deployment Complete!
+
+## Network: {Testnet/Mainnet}
+## Timestamp: {ISO timestamp}
+
+## Deployed Modules
+| Module | Address | Tx Hash |
+|--------|---------|---------|
+| {name} | 0x...   | 0x...   |
+
+## Verification
+- Explorer: {link}
+- Status: ✅ Verified
+
+## Next Steps
+1. Test contract interactions from frontend
+```
+
+## Troubleshooting
+
+### Insufficient Gas
+Ensure you have enough MOVE tokens. Get testnet tokens from:
+- Faucet: https://faucet.movementnetwork.xyz/
+
+### Compilation Errors
+Run `movement move compile` first and fix any errors.
+
+### Account Not Found
+Initialize your account:
+```bash
+movement init --network testnet
+```
+
+### Named Address Errors
+Ensure `Move.toml` has the correct address mapping and use `--named-addresses` flag.
+

package/kits/engineer/.claude/commands/docs/generate.md

@@ -0,0 +1,121 @@
+# /docs:generate - Auto-Generate Documentation
+
+Automatically generate documentation from code for the Movement dApp.
+
+## Workflow
+
+### Step 1: Analyze Codebase
+Scan the project to identify:
+- Move modules and their public interfaces
+- Frontend components and hooks
+
+### Step 2: Generate Contract Documentation
+
+For each Move module in `contracts/sources/`:
+
+1. Extract module name and address
+2. Parse resource definitions
+3. Parse entry functions with parameters
+4. Parse view functions with return types
+5. Parse events
+6. Extract error codes
+
+Generate `docs/contracts/{module_name}.md`:
+```markdown
+# {Module Name}
+
+**Address:** `{module_address}::{module_name}`
+
+## Overview
+{Auto-generated description based on module structure}
+
+## Resources
+
+### {ResourceName}
+\`\`\`move
+struct ResourceName has key, store {
+    field1: u64,
+    field2: String,
+}
+\`\`\`
+
+## Entry Functions
+
+### `function_name`
+\`\`\`move
+public entry fun function_name(account: &signer, param1: u64)
+\`\`\`
+**Parameters:**
+- `account`: Signer account
+- `param1`: {Description}
+
+**Effects:**
+- {State changes}
+- Emits `EventName`
+
+## View Functions
+
+### `get_value`
+\`\`\`move
+#[view]
+public fun get_value(addr: address): u64
+\`\`\`
+**Parameters:**
+- `addr`: Account address to query
+
+**Returns:** `u64` - The current value
+
+## Events
+
+### `EventName`
+\`\`\`move
+#[event]
+struct EventName has drop, store {
+    field1: u64,
+    timestamp: u64,
+}
+\`\`\`
+Emitted when: {condition}
+
+## Error Codes
+| Code | Constant | Description |
+|------|----------|-------------|
+| 1 | E_NOT_AUTHORIZED | Caller is not authorized |
+| 2 | E_ALREADY_EXISTS | Resource already exists |
+```
+
+### Step 3: Generate Component Documentation
+
+For each component in `frontend/src/components/`:
+
+Generate `docs/frontend/components.md`:
+```markdown
+# Frontend Components
+
+## WalletConnect
+Handles wallet connection and disconnection.
+
+**Props:** None
+
+**Usage:**
+\`\`\`tsx
+<WalletConnect />
+\`\`\`
+```
+
+## Output Summary
+```markdown
+# 📖 Documentation Generated
+
+## Contract Docs
+- {n} module documentation files
+
+## Frontend Docs
+- {n} component documentation files
+
+## Next Steps
+- Review generated documentation
+- Add custom descriptions where needed
+- Keep docs updated as code changes
+```
+

package/kits/engineer/.claude/commands/docs/init.md

@@ -0,0 +1,132 @@
+# /docs:init - Initialize Documentation Structure
+
+Initialize the documentation structure for the Movement dApp project.
+
+## Workflow
+
+### Step 1: Create Documentation Directories
+```bash
+mkdir -p docs/api docs/contracts docs/guides docs/architecture
+```
+
+### Step 2: Generate Documentation Templates
+
+#### docs/README.md
+```markdown
+# {Project Name} Documentation
+
+## Overview
+{Brief project description}
+
+## Quick Links
+- [API Reference](./api/README.md)
+- [Contract Documentation](./contracts/README.md)
+- [Architecture Guide](./architecture/README.md)
+- [Development Guide](./guides/development.md)
+
+## Getting Started
+1. Clone the repository
+2. Install dependencies
+3. Configure environment
+4. Run development server
+
+## Project Structure
+{Link to architecture docs}
+```
+
+#### docs/api/README.md
+```markdown
+# API Reference
+
+## Endpoints
+
+### GET /api/{module}/value/:address
+Get the current value for an address.
+
+**Parameters:**
+- `address` (string): The account address
+
+**Response:**
+\`\`\`json
+{
+  "success": true,
+  "data": [value]
+}
+\`\`\`
+```
+
+#### docs/contracts/README.md
+```markdown
+# Smart Contract Documentation
+
+## Modules
+
+### {module_name}
+{Module description}
+
+#### Resources
+- `ResourceName`: {Description}
+
+#### Entry Functions
+- `function_name(param1: Type)`: {Description}
+
+#### View Functions
+- `get_value(addr: address): u64`: {Description}
+
+#### Events
+- `EventName`: Emitted when {condition}
+
+#### Error Codes
+| Code | Name | Description |
+|------|------|-------------|
+| 1 | E_NOT_AUTHORIZED | Caller is not authorized |
+```
+
+#### docs/guides/development.md
+```markdown
+# Development Guide
+
+## Prerequisites
+- Node.js 18+
+- Movement CLI
+- Rust (for Move development)
+
+## Setup
+1. Install dependencies
+2. Configure environment variables
+3. Start development servers
+
+## Testing
+- Run Move tests: `cd contracts && movement move test`
+- Run frontend tests: `cd frontend && npm test`
+
+## Deployment
+See [Deployment Guide](./deployment.md)
+```
+
+### Step 3: Create .env.example Files
+
+#### frontend/.env.example
+```
+VITE_NETWORK=testnet
+VITE_MODULE_ADDRESS=0x1
+VITE_NODE_URL=https://full.testnet.movementinfra.xyz/v1
+```
+
+## Output Summary
+```markdown
+# 📚 Documentation Initialized
+
+## Created Files
+- docs/README.md
+- docs/api/README.md
+- docs/contracts/README.md
+- docs/guides/development.md
+- docs/architecture/README.md
+- frontend/.env.example
+
+## Next Steps
+- Run `/docs:generate` to auto-generate API docs from code
+- Update documentation as you develop
+```
+