Create Aptos Project Skill

Purpose

Scaffold new Aptos projects using npx create-aptos-dapp. This is the mandatory first step when a user wants to
build any new Aptos app, dApp, or project — regardless of how they phrase it.

ALWAYS

1. 1. Use npx create-aptos-dapp to scaffold — NEVER create projects from scratch manually
2. Ask the user about project type, framework, and network before scaffolding
3. Verify .env is in .gitignore before any git operations
4. Use the same network for both create-aptos-dapp and INLINECODE5
5. Follow the full Build a dApp workflow after scaffolding (contracts, tests, audit, deploy, frontend)

NEVER

1. 1. Skip scaffolding — even for "simple" projects, always start with INLINECODE6
2. Create project structure manually — the boilerplate template handles this
3. Display or read private keys — use "0x..." as placeholder
4. Run git add . or git add -A without first verifying .env is in INLINECODE11

Decision Tree

Before running the scaffold command, gather these inputs from the user:

1. Project Name

Derive from the user's description or ask directly. Use kebab-case (e.g., habit-tracker, nft-marketplace).

2. Project Type

3. Framework (fullstack only)

4. Network

5. API Key (optional)

Ask if the user has a Geomi API key. It's optional for devnet but recommended for testnet/mainnet to avoid rate limits.
Get one at https://geomi.dev (create project -> API Resource -> copy key).

Scaffolding Commands

CODEBLOCK0

Optional flags:

• - --api-key <key> — Pass a Geomi API key during scaffolding
• INLINECODE15 — Enable Surf for type-safe contract interactions

Post-Scaffold Checklist

After scaffolding, complete these steps in order:

1. 1. INLINECODE16
2. Verify .env is in .gitignore before any git operations
3. Run aptos init --network <network> --assume-yes (use the same network as above)
4. Verify: INLINECODE20
5. INLINECODE21

Build a dApp Workflow

ALWAYS follow this workflow when the user wants to build a new Aptos app, dApp, or project. This applies regardless
of how the user phrases it ("build me a ...", "create a ...", "make a ...", "I want to build ...").

1. 1. /create-aptos-project -> scaffold with npx create-aptos-dapp (this skill — NEVER skip)
2. INLINECODE24 -> write Move modules
3. INLINECODE25 -> create test suite, verify 100% coverage
4. INLINECODE26 -> audit before deployment
5. INLINECODE27 -> deploy contract to specified network
6. INLINECODE28 -> orchestrates frontend integration (routes to ts-sdk-client, ts-sdk-transactions,

What the Boilerplate Includes

Fullstack Template

• - contract/ — Move smart contract with Move.toml and starter module
• INLINECODE31 — React app with Aptos wallet adapter pre-configured
• INLINECODE32 — Scripts for move:compile, move:test, move:publish, dev, INLINECODE37
• INLINECODE38 — Environment variables for network, API key, and publisher account

Contract-Only Template

• - contract/ — Move smart contract with Move.toml and starter module
• INLINECODE41 — Scripts for move:compile, move:test, INLINECODE44
• INLINECODE45 — Environment variables for network and publisher account

Troubleshooting

npx create-aptos-dapp command not found

CODEBLOCK1

If that still fails, verify Node.js and npm are installed (node -v && npm -v).

Compile failures after scaffold

1. 1. Check contract/Move.toml has correct named addresses
2. Run aptos init --network <network> --assume-yes if not done
3. Verify my_addr is set to "_" in [addresses] section

Named address errors

The boilerplate uses my_addr = "_" which gets resolved from .env at compile time. Ensure
VITE_MODULE_PUBLISHER_ACCOUNT_ADDRESS is set in .env (populated by aptos init).