sui-full-stack
Use when starting a new SUI project from scratch or need end-to-end workflow orchestration (architecture → contracts → frontend → testing → deployment). This is the PROJECT ORCHESTRATOR that routes to specialized skills per phase. Triggers on "new project", "start from scratch", "full workflow", "what's the next step", or any multi-phase SUI development task. Do NOT use for Move↔TypeScript integration tasks (type generation, event handling) — that's sui-fullstack-integration.
Best use case
sui-full-stack is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when starting a new SUI project from scratch or need end-to-end workflow orchestration (architecture → contracts → frontend → testing → deployment). This is the PROJECT ORCHESTRATOR that routes to specialized skills per phase. Triggers on "new project", "start from scratch", "full workflow", "what's the next step", or any multi-phase SUI development task. Do NOT use for Move↔TypeScript integration tasks (type generation, event handling) — that's sui-fullstack-integration.
Teams using sui-full-stack should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sui-full-stack/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sui-full-stack Compares
| Feature / Agent | sui-full-stack | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when starting a new SUI project from scratch or need end-to-end workflow orchestration (architecture → contracts → frontend → testing → deployment). This is the PROJECT ORCHESTRATOR that routes to specialized skills per phase. Triggers on "new project", "start from scratch", "full workflow", "what's the next step", or any multi-phase SUI development task. Do NOT use for Move↔TypeScript integration tasks (type generation, event handling) — that's sui-fullstack-integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# SUI Full-Stack Development **Complete end-to-end SUI Move project development workflow.** ## Overview This is the main orchestrator skill that guides you through the entire SUI development lifecycle: 1. **Phase 0**: Project Initialization & Git Setup 2. **Phase 1**: Architecture Planning (`sui-architect`) 3. **Phase 2**: Smart Contract Development (`sui-developer`) 4. **Phase 3**: Frontend Development (`sui-frontend`) - Optional 5. **Phase 4**: Integration (`sui-fullstack-integration`) 6. **Phase 5**: Testing (`sui-tester`) 7. **Phase 6**: Deployment (`sui-deployer`) 8. **Phase 7**: Documentation Generation - Optional ## Quick Start ```bash # Start new project sui-full-stack # Resume existing project sui-full-stack --resume # Skip to specific stage sui-full-stack --stage testing ``` ## Workflow Summary ### Phase 0: Project Initialization - Collect project name and description - Set up Git version control (optional GitHub sync) - Create `.gitignore`, pre-commit hooks via `sui-security-guard` ### Phase 1: Architecture Planning - Call `sui-architect` for guided Q&A - Generate specification document and architecture diagrams - Git checkpoint with architecture commit ### Phase 2: Smart Contract Development - Call `sui-developer` to generate Move code from spec - Real-time quality checks (fast/standard/strict modes) - Auto-generate TypeScript types - Git checkpoint with contracts commit ### Phase 3: Frontend Development (Optional) - Call `sui-frontend` to set up React/Next.js/Vue - Install `@mysten/dapp-kit-react @mysten/dapp-kit-core @mysten/sui @tanstack/react-query` (hooks/providers from `@mysten/dapp-kit-react`; UI components like `ConnectButton` from `@mysten/dapp-kit-react/ui`). The legacy `@mysten/dapp-kit` package is deprecated. - Wallet integration and API wrappers - Git checkpoint with frontend commit ### Phase 4: Integration - Call `sui-fullstack-integration` - Generate TypeScript types from Move ABI - Set up event listeners and dev environment - If project needs historical data aggregation or custom analytics, call `sui-indexer` to set up a data pipeline (PostgreSQL + checkpoint processor) ### Phase 5: Testing - Call `sui-tester` for comprehensive testing - Move unit/integration tests, frontend tests, E2E tests - Gas benchmarks - Auto-fix failing tests (max 5 retries) ### Phase 6: Deployment - Call `sui-deployer` with network selection - Devnet (automated), Testnet (confirmation), Mainnet (strict checks) - Record Package ID, update frontend `.env` - Git tag for mainnet releases ### Phase 7: Documentation (Optional) - Generate technical docs, architecture docs, developer guide - Query latest APIs via `sui-docs-query` ## Git Checkpoints Each phase includes a Git checkpoint: 1. Run `sui-security-guard` scan 2. Create commit with conventional message 3. Optionally push to GitHub ## References - **[Phase Details](references/phases.md)** - Complete workflow for each phase - **[Configuration](references/config.md)** - `.sui-full-stack.json` options and CLI usage - **[Examples](references/examples.md)** - Complete project walkthroughs ## Integrated Skills This skill orchestrates: | Skill | Phase | Purpose | |-------|-------|---------| | `sui-security-guard` | All | Security at every checkpoint | | `sui-docs-query` | All | Latest documentation | | `sui-architect` | 1 | Architecture planning | | `sui-developer` | 2 | Move development | | `sui-frontend` | 3 | Frontend setup | | `sui-fullstack-integration` | 4 | Type generation | | `sui-tester` | 5 | Comprehensive testing | | `sui-deployer` | 6 | Multi-network deployment | | `sui-tools-guide` | All | Tool selection | | `sui-indexer` | 4 | Custom data pipelines (optional) | ## Common Mistakes ❌ **Skipping phases** - **Problem:** Missing architecture docs, untested contracts, poor integration - **Fix:** Follow phases sequentially, each builds on the previous ❌ **Not using Git checkpoints** - **Problem:** Cannot rollback to working state, lost progress - **Fix:** Commit after each phase with descriptive messages ❌ **Deploying without comprehensive testing** - **Problem:** Bugs discovered in production, user funds at risk - **Fix:** Complete Phase 5 (all test types) before Phase 6 deployment ❌ **Ignoring security-guard warnings** - **Problem:** Secrets committed to Git, API keys exposed - **Fix:** Fix all security warnings before committing ❌ **Manual frontend package ID updates** - **Problem:** Frontend calls wrong package after redeployment - **Fix:** Automate .env updates in deployment scripts ❌ **Skipping frontend phase for backend-only projects** - **Problem:** No way to interact with contracts for testing - **Fix:** Build minimal frontend or admin panel for contract interaction ❌ **Not documenting custom workflows** - **Problem:** Team members cannot reproduce setup - **Fix:** Generate docs in Phase 7, include setup instructions --- **From idea to production-ready SUI dApp - guided every step of the way!**
Related Skills
sui-fullstack-integration
Use when bridging Move contracts to TypeScript — generating TS types from Move ABI, creating contract API wrappers, subscribing to on-chain events, or building E2E integration tests. Triggers on "generate types from Move", "event listener", "contract ABI", "Move to TypeScript", "subscribe to events", "ABI wrapper", or any Move↔frontend bridging task. This is the CONTRACT-TO-CODE BRIDGE, not project setup (sui-full-stack) or UI/wallet (sui-frontend).
sui-zklogin
Use when implementing zkLogin on SUI — OAuth login (Google, Facebook, Apple, Twitch) with zero-knowledge proofs for privacy-preserving authentication. Triggers on "zkLogin", "social login on SUI", "Google login", "OAuth", "ephemeral keypair", "JWT proof", or any authentication flow that derives a SUI address from an OAuth provider. Also use when the user mentions "login without wallet extension".
sui-walrus
Use when storing or retrieving files using Walrus — SUI's decentralized blob storage. Triggers on "Walrus", "blob storage", "upload file to chain", "decentralized storage", "store NFT image", "IPFS alternative on SUI", "where to store NFT metadata", "host a site on-chain", or any off-chain data storage needs on SUI. Also use for Walrus Sites (decentralized web hosting), storing game assets, media files, or when the user asks "where do I put large files on SUI".
sui-wallet
Use when performing on-chain transactions (transfer, Move call, publish) through the agent's CLI wallet via MCP tools. Triggers on "transfer SUI", "call Move function", "publish package", "wallet status", "sign transaction", or any agent-driven on-chain operation. This is for headless/backend wallet operations — for browser wallet UI (React/Vue), use sui-frontend instead.
sui-tester
Use when writing Move tests, setting up test suites, running gas benchmarks, or planning test strategy for SUI contracts. Triggers on "write tests", "test this module", "#[test]", "test coverage", "gas benchmark", "property-based test", or any Move testing task. Use even for simple "how do I test this function" questions.
sui-suins
Use when integrating SuiNS (SUI Name Service) — resolving .sui names to addresses, reverse lookups, or registering names. Triggers on "SuiNS", ".sui name", "name resolution", "reverse lookup", "human-readable address", or any name service integration. Also use when the user wants to display user-friendly names instead of hex addresses.
sui-security-guard
Use when setting up security scanning, detecting leaked secrets/API keys, implementing pre-commit hooks, or auditing a Sui Move contract for security/architecture/quality issues. Triggers on "security scan", "detect secrets", "pre-commit hook", "security audit setup", "API key leaked", and on contract-level review requests like "audit this contract", "review access control", "is this Move safe", "check for vulnerabilities", "Move security review" — these load the SEC/DES/PAT/TST/QA/CFG finding registry in references/move-security-findings.md. For offensive/adversarial testing (attack vector discovery, writing exploits/PoCs), use sui-red-team instead. For Move style/idiom quality (non-security), use move-code-quality.
sui-seal
Use when implementing data encryption, access control, or secrets management on SUI using the Seal protocol. Triggers on threshold encryption, data privacy, token-gated content, encrypted storage, decryption policies, paywall, gated access, encrypted NFT metadata, private data sharing, or any scenario requiring on-chain access control for off-chain data. Also use when the user mentions Seal, pay-to-decrypt, "only NFT holders can see", or subscriber-only content on SUI.
sui-red-team
Use when performing adversarial security testing on SUI Move contracts — generating attack tests for access control bypass, integer overflow, object manipulation, economic exploits, reentrancy, and DoS vectors. Triggers on "red team", "attack test", "find vulnerabilities", "exploit", "pentest", "security test", or when the user wants to stress-test their contract's security. For defensive security setup (scanning, hooks, checklists), use sui-security-guard instead.
sui-passkey
Use when implementing WebAuthn passkeys or biometric authentication (Face ID, fingerprint, hardware keys) on SUI. Triggers on "passkey", "WebAuthn", "biometric login", "Face ID", "fingerprint auth", "FIDO2", or passwordless auth that uses device authenticators instead of seed phrases. Different from zkLogin (which uses OAuth providers).
sui-nautilus
Use when building verifiable off-chain computation, integrating external APIs with on-chain proof, or running trusted execution environments on SUI. Triggers on Nautilus, off-chain oracle, "verify API data on-chain", "connect external API to Move", "prove off-chain result", trusted compute, AWS Nitro Enclave, attestation, price feed, weather data on-chain, or any scenario requiring cryptographically verified external data. Also use when the user asks "how do I get real-world data into my SUI contract" or needs an oracle-like pattern.
sui-kiosk
Use when building NFT marketplaces, enforcing royalties, or managing transfer policies using SUI's Kiosk standard. Triggers on "Kiosk", "NFT marketplace", "transfer policy", "royalty enforcement", "list NFT for sale", "purchase rules", or any NFT commerce on SUI. Also use when the user asks about listing, delisting, or trading NFTs with enforced rules.