GUIDE 02 / PREPARATION EDITION
Build with your agent
Reuse the infrastructure. Put your effort into the game only your community could make.
Choose a direction
- Arcade & skill: a runner, precision platformer, drift course or survival arena.
- Social worlds: a community clubhouse, cooperative challenge or exploration game.
- Puzzle & strategy: a compact repeatable challenge with a fair difficulty curve.
- Invent your own: another browser game is welcome if the core requirements are met. These are inspiration paths, not separate prize categories.
Keep the first build small
Agree on a one-page design: player action, objective, failure state, session length, unlocked benefit and replay hook. Ask the agent to implement one complete loop, then review it before adding features. A polished five-minute experience beats a large unfinished world.
The recommended stack
- Three.js: a readable 3D scene, realistic PBR materials, intentional lighting and optimized textures. React Three Fiber is optional.
- Phantom: desktop wallet extension and the mobile wallet browser; recover from cancellation, account changes and returning from the background.
- DevFridge Game Builder skill: discovery, integration references, an exact-amount gate helper and delivery checks.
- DevFridge SDK/API: discover eligible timelocks; verify authoritative access on your server when protecting sessions, content or rewards.
- Optional Scan badges, ecosystem discovery and health checks only when they help the game. TopShelf is an advanced, separate Robinhood integration, not a required Solana feature.
A useful agent workflow
- Plan: write acceptance criteria and known limitations.
- Build: ship small changes and keep secrets out of prompts, commits and client bundles.
- Review: inspect generated code, dependency changes and asset licences.
- Test: desktop + physical phone, wallet failures, gate boundaries and the complete gameplay loop.
- Record: commit the result, update the AI build log and keep a reproducible setup guide.
Build before a token launch
Use clearly labelled fixtures or a supported test environment while exploring. Never present mock locks, prices, players or scores as live on-chain data. Do not call a planned token a verified mainnet integration. Before live rollout, verify the exact mint, token program, decimals, extensions and redemption route.