Menu
Scaffold a new Sui project with the right stack and write build-context.md. Use when the user wants to start, init, bootstrap, set up, or create a new Sui project, workspace, or template, in any phrasing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.
Build an AI agent that signs Sui transactions or runs onchain actions. Use when the user wants an AI agent on Sui.
Build a Sui data indexer or analytics pipeline. Use when the user wants to index Sui events, build a pipeline, or query Sui RPC data.
Build a mobile Sui app with React Native or the Sui Mobile SDK. Use when the user wants iOS, Android, or mobile Sui flows.
Pair with a coding agent to build a Sui MVP step by step. Use when the user wants to build the MVP iteratively with an agent.
Author Sui Move modules and packages with a senior Move dev as your pair. Use when the user wants to write, build, author, add, or scaffold Move code, smart contracts, or Sui programs at the module or function level, in any phrasing.
| name | scaffold-project |
| description | Scaffold a new Sui project with the right stack and write build-context.md. Use when the user wants to start, init, bootstrap, set up, or create a new Sui project, workspace, or template, in any phrasing. |
# Suiperpower telemetry. Routes through the CLI so projects.json + Convex stay in sync.
# Silent on failure so the skill never blocks. Opt out: SUIPERPOWER_TELEMETRY=off.
#
# AGENT NOTE: when this skill finishes, run the matching completion command:
# suiperpower track scaffold-project build completed
# Or use "failed" / "aborted" if it ended that way.
command -v suiperpower >/dev/null 2>&1 && suiperpower track scaffold-project build started >/dev/null 2>&1 &
true
If TEL_PROMPTED is no, before doing real work, ask the user:
Help suiperpower get better. We track which skills get used and how long they take. No code, no file paths, no PII. Change anytime in
~/.suiperpower/config.json.A) Sure, anonymous B) No thanks
Write the answer to ~/.suiperpower/config.json telemetryTier field and create ~/.suiperpower/.telemetry-prompted. Then continue.
Bootstraps a fresh Sui project on disk. Picks a template based on the project intent (Move-only package, frontend dapp, full-stack with backend), wires the standard Sui dependencies, generates Move.toml and package.json, and writes the canonical .suiperpower/build-context.md so subsequent skills know where the project lives and what stack it uses.
find-next-sui-idea first.build-with-move or the relevant build skill.deploy-to-testnet.If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.
.suiperpower/idea-context.md from find-next-sui-idea. Read it if present to derive project shape.If unclear, interview the user for:
A directory with: move/<package>/Move.toml, move/<package>/sources/, move/<package>/tests/, optional web/, optional cli/, .suiperpower/build-context.md, .gitignore, README.md.
Initial .suiperpower/build-context.md containing:
## scaffold-project session, <timestamp>
- project name: <name>
- stack: <move-only | frontend | full-stack>
- frontend: <none | next | vite>
- default sponsor integrations: <walrus | deepbook | scallop | none>
- Move package name: <name>
- target network: testnet
- open issues: <list>
A working sui move build and (if frontend) pnpm install + pnpm build.
The skill never deletes files outside the scaffolded directory without explicit user confirmation.
Context gathering
.suiperpower/idea-context.md if present.Pick the template
Generate the directory tree
Move.toml with pinned framework rev.sui move build succeeds.Frontend setup (if applicable)
@mysten/sui, @mysten/dapp-kit-core, and @mysten/dapp-kit-react. The legacy @mysten/dapp-kit package is deprecated and does not support gRPC or GraphQL.Sponsor defaults (if applicable)
@mysten/walrus (or HTTP path) for Walrus.@mysten/deepbook-v3 for DeepBook.@scallop-io/sui-scallop-sdk for Scallop.Quality verification
sui move build. Confirm zero errors.pnpm install and a build for frontend, if applicable.Write build-context.md
Hand off
object-model-design next if the project has non-trivial state.build-with-move for direct Move authoring.Closing handoff
.suiperpower/intent.md exists and the scaffold was non-trivial (new sponsor integration wired in, multi-package layout, custom upgrade authority), recommend verify-against-intent as the next step so the generated tree is checked against recorded intent before code lands on top.intent.md exists and the scaffold was non-trivial, surface that gap once: offer clarify-intent to backfill, do not force it.Before reporting done, the skill asks itself the following and refuses to declare success if any answer is no:
sui move build succeed in the scaffolded directory with zero errors?pnpm build without errors?Move.toml pinned to a specific framework rev or tag, not main?.suiperpower/build-context.md written with the stack decisions?If any answer is no, the skill reports the gap and works through it before declaring the project scaffolded.
On-demand references (load when relevant to the user's question):
references/template-shapes.md: Move-only, frontend, full-stack template shapes with file trees.references/move-toml-defaults.md: Pinned Sui framework rev, package name conventions, edition.Knowledge docs (load when scope expands beyond what is in references):
skills/data/sui-knowledge/04-protocols-and-sdks.md: SDK ecosystem context, which template fits which intent.claude "/suiper:scaffold-project <your message>"codex "/scaffold-project <your message>"grok, then /scaffold-project <your message> in the session~/.cursor/rules/scaffold-project.mdc and reference it.If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.