For a token

Describe the token name, symbol, total supply, decimals, initial recipient, and whether supply is fixed or mintable. Specify any administrator powers, transfer restrictions, or ownership requirements. Ask for artwork separately if you need an icon.

Example: “Create a fixed-supply Grape token called Orbit, symbol ORBT, with one million units and 18 decimals. Send the initial supply to my selected wallet. Explain any administrator permissions before deployment.”

For an NFT collection or application

For NFTs, provide the collection name, item count, artwork direction, metadata requirements, and whether all items should be preminted to a wallet or left mintable. For a mintable collection, ask for the mint flow, price, limits, permissions, and instructions.

For an application or game, describe the user journey, wallet actions, assets, pages, access rules, and what should happen on chain. Include what success looks like so testing can check outcomes rather than only whether files exist.

Review the actual deliverable

  1. Resolve missing information and inspect the working plan.
  2. Follow real task updates and check any reported blockers.
  3. Try the preview and inspect the generated project.
  4. Complete the required contract checks and signing approval.
  5. Verify deployment receipts, balances, NFT ownership, and the published URL.

Do not paste private keys into the chat. If the result is only source code, on-chain creation has not yet been demonstrated.