Open a link. Play.
A Three.js game for desktop and mobile browsers, with Phantom, touch controls and Daily, Weekly or Monthly passes paid in SOL.
DEVFRIDGE GAME BUILDER · v1.12.0
Unbox your
next game.
Your meme. Your world. Your rules. An AI coding skill to build playable 3D games for the browser and Seeker, from the first idea to the release.
BrowserSeekerOr both.
OPEN AGENT SKILLS FORMAT · DIGITAL DOWNLOAD
Already have an idea? Make your prompt ↗INSIDE THE BOX
3D gameplay. Landscapes, architecture and nature. Studio roles and workflows. Seeker Connect. Daily, Weekly and Monthly passes in SOL. In-app token market.
Asset, sound and music pipelines. Signed APKs. Optional Free Play sponsors. Optional DevFridge intro before the game opens. Store release guidance.
THE BUILDER’S EDITION
A little box. A world of possibility.
v1.12.0
DEVFRIDGEWORLD / BUILD
Game
BuilderYOUR MEME.
A WORLD TO PLAY.
BuilderYOUR MEME.
A WORLD TO PLAY.
Preparing your 3D edition…
01 / BRING A MEME+02 / SHAPE THE GAME+03 / SEASON PASS→PLAY ANYWHERE
YOUR NEXT MOVE
Open the box.
Give your agent the skill.
Open your project in a coding agent and paste this prompt. It installs the skill, asks Browser, Seeker app or Both first, then helps you shape your game.
Prefer a manual install? See the steps ↓THEN, MAKE IT YOURS
One skill.
Entirely your world.
A runner, a drift club, an arena. Start with the game your community wants to play, then build it around your character and your rules.
Explore six starting points ↗ CONCEPT LABTHREE.JS / PBR
Preparing your little world…
3D endless runnerSmall world. Endless possibilities.
PBR material study · detailed models, textured surfaces and studio lighting. Your AI builds the actual game.
FIRST, CHOOSE WHERE TO PLAY
Browser. Seeker app.
Or both.
Your agent asks this before building and reuses your answer. An unanswered choice stays open until you decide.
A game on your phone.
Choose game content included in the APK or loaded from your website. Both options deliver a signed Android APK, with wallet integration, physical Seeker tests and Store preparation.
Shared game. Two homes.
Share gameplay source and assets across the browser and Android app, with separate wallet adapters and checks for each release.
For Seeker, choose APK content before the architecture: included locally or loaded from a hosted website. Both produce an installable APK; Browser alone is a website. Wallet integration follows that architecture. For web delivery, your agent also asks separately about OnlyFridge Club Game Room. Signing, device testing and Store review remain part of release.
PICK A PASS. PLAY TO BELONG.
A meme gets attention.
A good game earns the next visit.
A token in a wallet gives a community something to own. A playable character gives it something to do. DevFridge connects the two: players buy a Daily, Weekly or Monthly Pass in SOL. The SOL buys your token, which stays set aside for the pass length, and the pass opens your game.
That meme is me.
Turn your token’s character and lore into a playable identity. Give holders a way to show up as part of their community.
I’m in for this season.
Players choose a pass with a clear token amount, duration and end date. Their tokens remain held on-chain until that date.
- 1 Month
- 6 Months
- 1 Year
Illustrative labels. Your amounts and durations determine whether a Best value badge is justified.
One more run.
Master a level, beat a personal best or join a community challenge. Build a repeat-play loop that makes the pass worth using.
ONE SOLANA PROGRAM. YOUR GAME’S RULES.
Connect → Subscribe in SOL → Play → Return
One transaction buys your token with the player’s SOL and deposits it in the existing Fridge program on Solana ↗ until the pass ends. Any active deposit of your token opens the game, and the countdown reads its end time; amounts are never matched against prices. You choose your RPC, Token-2022 mint, domain, pass prices and free scope; your game does not need a new contract.
Players see a subscription, its SOL price and a countdown. The review shows the plan, price, end date and network costs, and one line saying the SOL buys your token. The full mechanics, including the 2% fee when tokens leave the program, go in your terms page.
TOKENIZED CHARACTERS · ONE EXISTING PUMP.FUN MARKET
The meme token becomes part of the game.
Here, a tokenized game means the community’s existing fungible token is tied to a playable identity or feature—not that buyers own the game. The skill maps an exact Solana mint to a character, its art, mood and music, then builds the game around that identity. An active subscription can open the character or features chosen for the game. Existing games can retain their independently configured access rules. The same mint remains the community token traded on its existing market, including Pump.fun where applicable.
Why Token-2022? It is the token program accepted by the current DevFridge Fridge program: create_lock rejects other token programs, transfers with transfer_checked and records the amount actually received in the vault. Token-2022 also has native metadata extensions that suit a portable token identity. MetadataPointer identifies where metadata is stored; TokenMetadata can hold the mint’s name, symbol, URI and custom key-value fields. The URI can point to JSON with the character image, description, game website and community/social links. These fields help wallets, explorers and game tooling identify the character; they do not contain the game itself or grant access by themselves. Solana metadata extension docs ↗
A mint can also use Metaplex metadata. Metadata conventions and client support vary, so the skill checks the actual mint and metadata rather than assuming every Pump.fun token uses the same layout. The Fridge program checks the Token-2022 lock; it does not read or write either metadata format. The identity and its image/site links are configured on the mint before the lock.
For a Pump.fun community, the game gives its meme a playable use: holders can appear as their character, share its world and return for new challenges. That can make the community token more relevant to people who want to play, and may create additional demand for the same mint. It is a possible market effect, not a promise of buyers, retention or price appreciation. Tokens in an active vault cannot be sold or withdrawn before the chosen unlock date. After expiry, the depositor redeems: 2% of the redeemed amount is used to buy and burn PASTA, or is burned directly when the locked mint is PASTA; the remainder returns subject to the redemption route and network costs. The holder can then sell on the market available at that time. Later players do not pay earlier players; market price and liquidity can rise or fall, and the lock sets no price floor, market cap or return.
The retention idea is identity + voluntary commitment + enjoyable progress. A subscription creates an access window; gameplay earns the return visit. Measure returning players separately from tokens held on-chain. Neither retention nor token price growth is guaranteed.
ONE ENGINE. MANY MISSIONS.
Build your game.
Reuse the engine.
Think of SpaceX’s reusable rockets: the next mission builds on an engine already built. Fridge brings that reuse idea to meme games. Your AI uses the skill to create Season Passes directly on the existing Solana timelock program, with the SDK available as an optional read path.
A reuse analogy, with no affiliation or endorsement by SpaceX or Elon Musk.
- 01 / THE ENGINEFridge on Solana
Token vaults, unlock dates and redemption rules.
- 02 / THE CONNECTIONOn-chain passes + AI skill
Create the pass. Check each deposit against your game’s rules.
- 03 / YOUR MISSIONYour meme. Your game.
Runner, racer or arena: bring the character and the fun.
SOLANA MAINNET / FRIDGE PROGRAM
9RY54dNPYTzDyh3TfFqDdt2b2KMM56KW1tw9erRTGQo6 ↗Evidence checked 22 September 2026 · Snapshot, not a live security monitor.
A contact card in the code.
The deployed program includes security metadata: project, source, disclosure policy and contacts. Researchers can find the developer directly from the program address. TRUE means those metadata are present; it is not a safety score or audit approval.
Read the on-chain metadata ↗Source and deployment match.
Solscan displays Verified Build. The verification service reports matching hashes for the executable built from source and the deployed program, linked to commit 292645a. This is reproducible-build evidence for that version, not a guarantee of bug-free code.
Inspect the work behind it.
The repository documents developer review, a Sealevel attack-pattern checklist, Rust tests, Clippy, dependency checks and Sec3 X-ray runs. These are different layers of evidence. Current security metadata say auditors: None; no independent audit is published.
What makes Fridge reusable?
Each Token-2022 lock records its depositor, exact mint, amount and unlock date in a distinct program account. Tokens sit in a PDA-controlled vault. A wallet can create multiple independent locks; under the current program, only the depositor can redeem after expiry. Redemption applies the documented 2% PASTA buy-and-burn fee.
Your game chooses supported tokens, Season Pass tiers, free scope and character access. The skill guides direct on-chain activation and per-deposit eligibility; the SDK can optionally read existing locks. You reuse the deployed timelock infrastructure while building your own gameplay, wallet flow and score verification. Token extensions and redemption routes still need compatibility checks.
The program remains upgradeable. Check the current authority and verification after upgrades. Reusing the live program is also distinct from copying or redeploying its source, which has its own licence.
What is actually recorded on-chain?
Program bytecode, lock accounts and transactions are on-chain. Security metadata are embedded in the program. Solana’s verified-build workflow can store repository, commit and build instructions in a verification PDA, then use a remote rebuild to compare hashes.
An audit report, a build record and a transaction receipt prove different things. The records checked here do not establish an independent audit stored on-chain. A future audit should link its author, scope, reviewed commit, report and any on-chain attestation explicitly.
How Solana verified builds work ↗Open the verification receipts
- Source linked by the verifier
- Commit 292645a ↗
- Matching executable / on-chain hash
0043d6dabd4d8d50e6623305a12f32404e281499920a7a6478f2d6a36f60237e- Verifier timestamp
- 25 August 2026 · status rechecked 22 September 2026
Tests cover zero amounts, invalid unlock dates, fee arithmetic and boost configuration. The public security workflow also runs Clippy, cargo audit and X-ray when program inputs change.
The 19 September run is marked successful, but its X-ray output includes LLVM diagnostics alongside “No issues detected.” Its cargo audit configuration excludes two documented advisories, RUSTSEC-2024-0344 and RUSTSEC-2022-0093. A green workflow badge alone does not establish complete analysis or an independent audit.
Inspect the actual check logs ↗The development effort you can reuse
Building this foundation involves program engineering, account constraints, tests, deployment, reproducible-build verification, SDK work and ongoing maintenance. The skill makes that existing work accessible to another game without requiring its developer to start a new timelock program from scratch.
No substantiated total for development or external audit expenditure is published in the sources reviewed here. Network fees and rent balances are not a development invoice. Reuse can avoid duplicated work; it does not remove your game’s integration, testing, hosting or security-review costs.
Open the fridge. Follow the evidence.
Use DevFridge’s visual interface to explore locks, amounts, unlock dates and transaction links. Open Solscan’s Program IDL, Accounts Data, Verification and Security tabs for the technical details. No terminal needed to inspect them.
A BUILDING PARTNER, WITH CONTEXT
It asks the right questions.
Then it helps you ship.
A practical skill for an AI coding agent. It supplies the DevFridge integration knowledge; your agent writes and tests the game in your project.
Choose platform and game
First choose Browser, Seeker app or Both. Then shape your runner, drifter, puzzle or something stranger around the way your community wants to play.
Set up your passes
Your RPC, Token-2022 CA, website domain, Daily/Weekly/Monthly prices in SOL and what stays free. Each pass shows its price, end date and a live countdown. Choose an optional in-app token market, and decide separately about the DevFridge intro, the pre-round Club promotion and the top sponsor card.
Build and prepare release
Test the game loop, wallet and mobile recovery. Browser gets a web build; Seeker gets the chosen APK content, wallet checks and Store preparation. Both shares the game source.
SINCE v1.8.0
A studio, inside the skill.
Claude Code Game Studios 1.2.0 is included: 49 roles and 74 workflows for design, code, art, audio and QA. Your agent uses the light path — one brief, then a playable game it has actually looked at. DevFridge still asks for the platform, the subscription and the release checks first.
The right specialist for the step.
Directors, department leads and specialists cover design, programming, art, audio, narrative and QA. The agent reads the one role the current task needs.
A brief, then the game.
The studio’s own playtest ranked a one-page brief ahead of a 30-document pass. Heavier design docs are used only when you ask for them.
Your rules are not replaced.
Browser, Seeker or both, subscription prices, ads and the 50 FPS release gate stay DevFridge decisions. The studio does not switch the engine or set token amounts.
Hooks, bash helpers and Claude Code settings from that project are not installed into your game. Read how the studio is used ↗
BUILD AND RELEASE
Plan, build and verify.
Guides and working tools for your agent, with checks tied to the game you actually build.
The domain the wallet judges.
Use a real HTTPS identity from the first submittable build, with favicon and assetlinks. A scam-site simulation, or a provider key in the APK, blocks submission.
Check wallet trust ↗Keep the key on your server.
Deploy a fixed-upstream RPC proxy with scoped methods, request limits and safe errors. The APK contains your proxy URL; provider keys stay in the server environment.
Set up the RPC proxy ↗Landing, privacy and terms.
Generate separate public pages from your actual publisher details and game practices. Drafts stay visibly incomplete until reviewed; use your real HTTPS identity domain.
Generate the support website ↗A measured 50 FPS release gate.
Run representative gameplay on the exact candidate. A complete measured second below 50 FPS blocks release. APKs also need physical Seeker evidence and the device checklist.
See performance requirements ↗A working game, step by step.
Build the small complete loop first. Save source, checksums, test results and the next action after every stage, then add improvements with a recoverable checkpoint.
Use incremental checkpoints ↗Wait for the action.
Capture real gameplay when configured scenes are ready. Keep the originals, add accurate captions and check screenshot count, dimensions and size before delivery.
Automate Store screenshots ↗Same key. Verified release.
Check versions, package, certificate and candidate evidence before the publishing CLI. Selected deliverables over 25 MB route to your configured private Drive folder with resumable uploads.
Prepare updates and delivery ↗Subscriptions + optional market
Sell Daily, Weekly and Monthly passes in SOL. One transaction buys your token and sets it aside; any active deposit opens the game. If selected, the in-app market uses fresh quotes, transaction validation and recovery for uncertain results.
Explore the subscription workflow ↗Give your game an identity.
18 curated gamedev skills guide models, materials, animation and game feel. Add licensed logo art, sound-effect variants and soundtrack briefs, with audio processing tools and separate music/SFX controls.
Explore the creative workflows ↗Icons, performance and checks.
Build adaptive launcher icons, caption real screenshots and use an adaptive quality governor. Copy and secret checks support the release checklist; Seeker testing and Store approval are verified separately.
Explore the release checklist ↗The package includes helpers, tests and implementation guides. Your agent creates the game, assets and platform integration in your project; a helper test does not certify an APK or a live wallet transaction.
PROMPT STUDIO
Start with your idea.
Fill in what you know. Leave the rest blank and the skill will ask.
Your agent must resolve this choice before implementing gameplay. Browser delivers a website; Seeker delivers an installable APK, with the content choice below. Both delivers the website and APK.
Name your provider, for example Alchemy or Helius. Never paste an API key here: your agent keeps it server-side.
Daily = 1 day, Weekly = 7 days, Monthly = 30 days. You set every price. The SOL buys your token, which stays set aside until the pass ends.
This is separate from the subscription and advertisements. Ask me keeps the market unresolved; no purchase is made by this form or used as a test.
Asked before building. Include plays the supplied DevFridge Games page once when the game opens. On an APK that page and its files are inside the package. Skip enters the game. It is separate from Free Play ads.
A mint is verified during development. This form does not connect a wallet, check eligibility or submit a transaction.
YOUR BUILD BRIEF.prompt
SIX STARTING POINTS. YOUR OWN LORE.
What will your meme become?
Example briefs, not ready-made games. Copy one and let the skill interview you.
013D endless runner
Meme on the run
One thumb. Three lanes. Your meme outrunning the chaos.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Build a Three.js endless runner for my Pump.fun token. Ask for the exact mint, subscription prices in SOL and what stays free. Include three-lane swipe controls, keyboard controls where supported, collectible combos, a complete loss/restart loop, the chosen platform wallet and in-app subscription activation. Keep the HUD clear of the track. Start with local personal bests and no paid entry. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
023D arcade drifting
Community drift club
A tiny track with a big personality. Chase your best lap.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Build a stylized Three.js drift game around my meme. Interview me about the token, character, handling, subscription prices in SOL and free scope. Support mobile steering buttons and keyboard steering where supported, lap timing and restart, the chosen platform wallet and in-app SOL subscription purchase. Use original or licensed assets. Label personal bests local; ask before adding authoritative competitive scores. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
033D arena survival
Last meme standing
Dodge the swarm. Collect upgrades. Survive another wave.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Build a single-player Three.js survival arena for my token community, with virtual joystick and keyboard movement where supported, auto-attack, escalating waves and win/loss screens. Ask for mint, assets, subscription prices in SOL and what stays free. Use the wallet integration for my chosen platform and in-app pass activation. Do not imply real multiplayer or rewards unless we design those separately. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
043D physics puzzle
Stack the lore
Merge, balance and discover the next form of your mascot.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Build an original Three.js physics stacking puzzle for my Pump.fun meme. Ask about merge rules, assets, mint, subscription prices in SOL and free scope. Implement touch drag/drop and pointer aim, fixed-step physics, sound, restart and score-image sharing. Use in-app SOL subscription purchase plus the chosen platform wallet without copying World characters or imposing its ten-token rules. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
053D exploration
Holder hideout
A community clubhouse with doors your token can open.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Build an explorable Three.js clubhouse with touch controls and keyboard controls where supported. Ask which rooms or characters a subscription opens, the exact mint, pass prices and what stays free. Include the chosen platform wallet, in-app subscription activation and accessible menus; ask before adding a technical live lock badge. A single-player prototype is fine; ask before adding real-time social networking. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
06Competitive game
Season challengers
A verified leaderboard, designed as a separate trusted system.
Read the prompt
Use $devfridge-game-builder. First resolve the delivery platform with me as the game owner, before other build decisions. Do not implement gameplay until I explicitly choose Browser, Seeker app, or Both. Reuse an explicit prior platform choice without asking again. Ask me supplies no new decision and must never default to Browser; only a choice missing from both this prompt and our prior conversation remains pending. Delivery platform: Ask me: no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask Browser, Seeker app, or Both and wait for my answer. After resolving the platform, for Seeker app or Both, resolve APK content before architecture implementation. There is no automatic default: reuse my explicit prior answer, otherwise ask and wait. Both content choices produce an installable signed APK; Browser alone does not require an APK. Bundled assets do not make wallet, RPC or server features work offline. Explain the three delivery options if needed, then use only the chosen platform workflow. Browser uses Phantom on desktop/mobile. Seeker app delivers an APK with the chosen content and wallet architecture, physical-device testing and Solana dApp Store preparation. Both shares gameplay source with separate platform adapters. After resolving the delivery choices, ask about Game Room only if web delivery is selected: Browser, Both, or a Seeker APK that loads a hosted website. Reuse an explicit prior answer for that web path; otherwise ask and wait before gameplay or integration work. For bundled-only Seeker, skip Game Room and ignore stale choices. Game Room is independent of both ad choices and Free Play. If included for a web path, prepare integration/submission using references/game-room.md without claiming publication. Before implementing gameplay, ask me as the game owner whether to include each of these two independent free-play ad integrations, unless I have already explicitly answered. Accept both, either one, or neither. Reuse each explicit choice without asking again. Keep each integration disabled unless I explicitly chose Include. Ask me supplies no new decision: reuse a prior explicit answer, otherwise leave it pending and ask before gameplay implementation. A missing answer is never consent. If I explicitly choose no Free Play, mark both not applicable without asking ad questions or adding a free mode. Read references/free-play-sponsors.md for integration details. OnlyFridge Club ad before every free run, including the first run and every retry/restart, but never on pause/resume: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. YOUR AD HERE / sponsored-token top card during free mode only: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The top card is the only ad during a free run; the independently selected Club promotion appears before each new free round. Neither integration may appear in subscription or paid sessions. These ad choices are separate from the other optional ecosystem modules. Before implementing gameplay, ask me whether to show the DevFridge Games intro before the game opens. This choice is independent of platform, Game Room, the market and both Free Play ads. Reuse my explicit prior choice. Ask me supplies no new decision and is never consent. Read references/devfridge-intro.md. DevFridge intro before the game opens: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep the intro out until I answer. If included, play that local page once on each cold open, before the menu, the pass and play. On an APK the HTML, logo, fonts and synth are files inside the package, including when the rest of the game is hosted. Do not load them from the network. Skip and the ending both enter the game. The door tap starts it. Do not replay it on pause, resume or wallet return. The skill link opens https://world.devfridge.cool/skill outside the WebView only when tapped. Do not put that branding on subscription, wallet or gameplay screens. Help me design and build a competitive Three.js game with Daily, Weekly and Monthly passes paid in SOL. Interview me about gameplay, subscription prices in SOL, free scope and any separately designed rewards. Separate wallet ownership, per-deposit pass eligibility and live score authority. Evaluate TopShelf as an optional Robinhood integration, confirm operator support, and never submit arbitrary client scores to its production service. Explain bot limitations and test mobile interruptions before enabling rewards. Right after the platform choice, resolve my blockchain setup together in one message. Read references/discovery.md and references/season-pass.md. Reuse my explicit prior answers; otherwise ask once and wait. Solana RPC: Ask me which RPC provider to use. If I give no answer, use the public Solana RPC https://api.mainnet-beta.solana.com. Token-2022 CA: Ask me for the exact token contract address or Pump.fun URL; do not choose one for me. Verify on-chain that it is an initialized Token-2022 mint without TransferFee, TransferHook or unknown extensions, and that it has a market route. Website domain: Ask me for my game website domain (wallet identity, privacy and terms pages, game origin). Missing blocks release, not development. Subscription passes and SOL prices: Ask me which of Daily Pass (1 day), Weekly Pass (7 days) and Monthly Pass (30 days) to sell and the price in SOL of each. Do not invent prices. What stays free: Ask me; reuse my explicit prior free scope, otherwise ask what, if anything, stays free. Optional in-app Buy <TOKEN> screen: Ask me; no new choice supplied in this prompt. Reuse my explicit prior choice; otherwise ask and keep disabled while pending. The market choice is independent of platform, Game Room and both free-play ad choices; never infer consent from them. Paid access is a Daily, Weekly or Monthly subscription paid in SOL: in one wallet-approved transaction the SOL buys my token on its live route and the bought amount (the swap's guaranteed minimum output) is deposited in the existing Fridge program until the pass ends. Grant access when the connected wallet has any active verified deposit of my mint; never compare the deposited amount with the price. Read the countdown from that deposit's end time. An unknown RPC result never grants access. Players see a subscription, its SOL price and a countdown; game screens never mention timelocks, vaults, deposits, the program or PASTA, and Details says only that the SOL buys my token, set aside until the subscription ends, and that its value can change. Put the full mechanics in the terms page. Do not deploy a new contract or add automatic renewal. If the game builds Fridge claim, follow the claim accounts in references/program-and-verification.md for this mint whether it is PASTA or another Token-2022: the PASTA mint, the burn-PDA fee ATA, the burn-PDA PASTA ATA and Jupiter v6 are always included, a Jupiter route is added only when the mint is not PASTA and the fee is above zero, and a shorter account list fails with Anchor 3005. Use detailed models, realistic PBR textures, natural material scale, environment reflections and soft contact shadows. Ask about art direction; optimize texture sizes and draw calls for mobile. Do not deliver placeholder cubes as finished art. Reuse my website domain as wallet identity. Ask for my permanent Android package if applicable, supported UI languages and logo/art/audio rights; reuse answers already provided. Follow references/gamedev-skills.md to route the selected game genre and platform, references/game-studio.md for the vendored Claude Code Game Studios roles and workflows, references/3d-assets-and-characters.md and references/visual-realism.md for realistic assets, references/logo-and-store-art.md for original brand and Store art, and references/sound-prompts.md and references/music-prompts.md for SFX and soundtrack pipelines. Use the studio's minimal path: one gameplay brief, then the playable loop, then look at the running game. DevFridge platform, subscription, wallet, advertisement and release rules win on every conflict. Do not install that studio's hooks or settings, do not switch the engine away from Three.js, and do not block implementation on its missing story files or bash helpers. Record actual licenses and distinguish generated or proposed assets from completed, inspected files. If I explicitly select the in-game market, resolve the token's route on-chain, show a fresh quote and all costs, simulate and validate the exact transaction, and recover unknown outcomes without an automatic second request. Follow references/in-game-market.md; do not execute a real purchase as a test. Build one complete working loop first, then small improvements with a verified source snapshot, actual check results and exact next action at every stage; follow references/incremental-build.md. Preserve newer work on resume and continue through the full requested scope. Use the RPC I chose; with no choice use the public Solana RPC directly. For a private provider use references/rpc-proxy.md: fixed server-only upstream, scoped methods and limits; never embed the paid RPC key in the game or APK. Before proposing a Seeker Store submission, follow references/wallet-trust.md and block submission when the identity domain, wallet simulation, RPC key scan or review content gate fails. Generate real landing/privacy/terms pages from actual app facts with references/public-site.md. A bundled-only support website does not make Game Room inclusion applicable. Before every game release, follow references/performance-and-capture.md: capture real input-driven gameplay and block release if any complete measured one-second window falls below 50 FPS after warmup. Require fresh exact-candidate evidence; for APKs require the physical Seeker checklist. When Store materials are requested, capture actual ready scenes, retain original screenshots, add truthful captions and validate dimensions/count/size; browser-only performance tests do not require Store artwork. Missing hardware evidence blocks release, not ongoing development. Follow references/release-updates.md for version advancement, original package/signing identity and verified publishing CLI submission within existing authorization. Automatically route explicitly selected deliverables over 25,000,000 bytes to the configured authorized private Drive folder with secret scanning, resumable uploads and checksum verification. Missing Drive setup means delivery pending; never upload keys, credentials or private checkpoints. These thresholds are workflow policies, not Store limits. Apply references/release-pitfalls.md, the adaptive icon builder, player-copy and secret checks, and the quality governor. Keep player-facing subscription wording simple: price in SOL, countdown, and one Details sentence that the SOL buys my token; keep technical and fee disclosures in the terms page. Verify the selected UI languages and platform controls. Keep simulations, physical Seeker tests, signed APK creation and Store publication status distinct; report unavailable checks honestly. Do not buy tokens, move funds or sign transactions during setup.
CHOOSE YOUR INGREDIENTS
One game.
A connected ecosystem.
Start with the core. Add the components that serve your game.
Explore the whole kitchen ↗CORE ↗
Subscriptions
Daily, Weekly and Monthly passes paid in SOL, verified on-chain with a countdown. Configure your RPC, Token-2022 mint, prices and free scope; SDK reads are optional.
OPTIONAL MARKET ↗Buy your game token
An in-app quote with fresh on-chain routing, exact transaction checks and recovery for unknown outcomes. Added only if you choose it.
BROWSER WALLET ↗Phantom
Desktop extension and mobile wallet browser, with sign-in and in-app subscription purchase.
SEEKER WALLET ↗Seeker Connect + MWA
Native or web wallet integration matched to the APK architecture, with approval, cancellation and resume tested on a physical Seeker.
VISIBILITY ↗Scanner + badge
Let players inspect the mint and see live supply-lock evidence beside the game token.
COMMUNITY ↗FrigoPasta + sharing
Optional Telegram tools, token information and shareable score images.
ADVANCED ↗Seasons + TopShelf
Design score authority first. Robinhood integration needs separate configuration and operator support.
DISCOVERY ↗The wider kitchen
Connect, Health, Synapse, Team, Feature, Capital and verified bridge routes — selected when useful.
2%PROTOCOL FEENetwork costs are separate.
USE THE ECOSYSTEM. SUPPORT ITS BUILDER.
How the subscription fee works
A subscription deposits the bought tokens in the existing Fridge timelock program. When tokens leave the program after expiry, the current 2% protocol fee buys and burns PASTA; for PASTA deposits, that portion is burned directly. The game discloses this in Details before approval, along with network costs and route limitations.
PASTA is pappardelle.sol’s developer token. The project’s support model connects ecosystem usage to PASTA buy-and-burn, with the aim of supporting continued development and infrastructure sustainability.
Pass ends→2% protocol fee→Buy PASTA + burn
The fee is spent on buying and burning tokens. It is not a direct payment to an infrastructure or developer treasury, and does not guarantee developer income or a price increase.
Example: redeeming a 100,000-token vault leaves 98,000 tokens after the 2,000-token protocol fee, before separate network costs and token-specific effects. Non-PASTA redemption requires an executable Jupiter route. The game’s terms page explains the fee and route limitations; game screens keep it simple. Players do not need to own PASTA to buy a pass.
Read the fee and burn mechanics ↗YOUR CODING AGENT + THE DEVFRIDGE SKILL
Submit through your agent.
No Git experience needed.
Submit through your own coding agent with the DevFridge Game Builder skill. No Git experience needed. Your agent prepares the project details and evidence, handles the GitHub fork and pull request, checks errors and helps with review feedback. You provide missing decisions and sign in when needed.
Copy this prompt into your own coding agent with the DevFridge Game Builder skill installed. Your agent submits the game; this website explains the process and displays the reviewed projects.
Gallery submissions are open for review. Competition dates, prizes and final eligibility remain to be announced.
Your agent submits
It checks the playable game and evidence, validates the project details and opens a review request. You receive the real PR link.
DevFridge reviews
The owner reviews the game and project details. Your agent helps fix checks and address feedback in the same PR.
Your game goes live
After owner review, merge and a successful deployment, the project appears in the gallery automatically. Approval alone does not publish it.
PUT IT IN YOUR TOOLBOX
One download.
A complete playbook.
Includes Claude Code Game Studios 1.2.0 — 49 roles and 74 workflows used under DevFridge’s platform, subscription and release rules — plus a private RPC proxy, generated public app pages, a 50 FPS release gate, stage checkpoints, ready-state screenshots and private Drive delivery for selected files over 25 MB. Also included: platform and APK architecture discovery, configurable on-chain subscription prices in SOL, optional in-app token market, Phantom and Seeker Connect/MWA guides, independent Free Play promotions, web Game Room discovery, realistic asset and logo pipelines, SFX and soundtrack briefs, adaptive quality and icon tools, copy and secret checks, Store release preparation, competitive-mode guidance and guided hackathon submissions. New games use the subscription helper (any active deposit, countdown from its end time); the legacy exact-amount evaluator remains for existing games.
The .skill file contains the same ZIP package. Use it only if your agent supports this import format.
Read SKILL.md ↗Browse all source files ↗Install, then start a conversation.
Extract the ZIP. Place the devfridge-game-builder folder in your project’s .agents/skills/ directory, then invoke $devfridge-game-builder in Codex. If your Codex version uses a different skill directory, follow its current settings.
devfridge-game-builder/
├── SKILL.md
├── CHANGELOG.md
├── agents/openai.yaml
├── references/
│ ├── discovery.md
│ ├── devfridge-intro.md
│ ├── free-play-sponsors.md
│ ├── retention-and-economics.md
│ ├── program-and-verification.md
│ ├── ecosystem.md
│ ├── sdk-access.md
│ ├── phantom.md
│ ├── seeker-android.md
│ ├── seeker-wallet.md
│ ├── solana-dapp-store.md
│ ├── wallet-trust.md
│ ├── game-delivery.md
│ ├── game-room.md
│ ├── visual-realism.md
│ ├── competition.md
│ ├── hackathon-submission.md
│ ├── season-pass.md
│ ├── in-game-market.md
│ ├── release-pitfalls.md
│ ├── 3d-assets-and-characters.md
│ ├── gamedev-skills.md
│ ├── game-studio.md
│ ├── logo-and-store-art.md
│ ├── sound-prompts.md
│ ├── music-prompts.md
│ ├── rpc-proxy.md
│ ├── public-site.md
│ ├── incremental-build.md
│ ├── performance-and-capture.md
│ ├── release-updates.md
│ └── sources.md
├── assets/
│ ├── timelock-gate.mjs + tests
│ ├── season-pass.mjs + tests
│ ├── quality-governor.mjs + tests
│ ├── check-player-copy.mjs + tests
│ ├── devfridge-intro/
│ ├── check-no-secrets.py
│ ├── make-adaptive-icons.py + icon tests
│ ├── store-compose.py
│ ├── sfx-build.py
│ ├── rpc-proxy/
│ ├── public-site/
│ ├── checkpoints/
│ ├── release-capture/
│ ├── release-delivery/
│ └── templates/
│ ├── sfx-manifest.example.json
│ ├── music-brief.md
│ ├── store-listing.md
│ └── ASSETS_LICENSES.md
└── vendor/
├── gamedev-skills/
│ ├── LICENSE + NOTICE + README.md
│ └── 18 curated upstream skills
└── claude-code-game-studios/
├── LICENSE + README.md
├── agents/ 49 roles
├── skills/ 74 workflows
├── rules/ 14 coding standards
└── docs/ roster, templates, workflow notes“+ tests” and “+” group separate files in this tree. The package manifest lists each file and checksum. Helper tests do not certify a game or physical device.
Agent Skills is a folder format, not a hosted game generator. Your agent needs a coding workspace and development tools. Format specification ↗
BEFORE YOU BUILD
A few things to know.
Can I build for Browser, Seeker app or Both?+
Yes. The agent asks you to choose the delivery platform first and waits before implementing gameplay. An explicit answer is reused. Browser means desktop/mobile web; Seeker app means an installable Android APK whose game content can be included locally or loaded from a hosted website; Both shares gameplay source while keeping platform adapters separate.
What does Seeker app delivery include?+
First choose content included in the APK or loaded from your website. Both choices produce a signed release APK. The skill guides Android setup, a compatible native or web wallet path using the current Seeker Connect / Mobile Wallet Adapter stack, physical Seeker testing and Solana dApp Store preparation. The release checklist includes listing assets, privacy and support details, signing and review evidence. If a device, signing key or publisher prerequisite is missing, the agent reports the remaining work; an APK alone is not Store approval.
When does the skill ask about Game Room?+
For Browser or Both, or a Seeker APK that loads a hosted website. A bundled-only Seeker app skips this question and ignores any stale Game Room opt-in. Pending platform/content choices get conditional guidance until a web path is confirmed. Include means prepare integration/submission for review using the Game Room guide; it does not promise publication. This choice is independent of Free Play and both ad placements.
Does my Pump.fun token work automatically?+
The skill verifies the full mint, token program, decimals and extensions. Current Fridge integration uses Solana Token-2022. A Pump.fun link alone does not establish compatibility.
Do I have to use World’s tokens or 500,000-token minimum?+
No. Those are World-specific rules. Your developer chooses the supported mint, pass prices, free scope and what each pass enables.
Is a subscription a retention guarantee?+
No. A pass creates a participation window and a meme character can create a sense of belonging. Fun, progress and community activities give players reasons to return. The skill asks the developer to design and measure that loop; tokens held on-chain alone are not retention.
What happens when a subscription ends?+
Access ends at the deposit’s end time and the game offers to subscribe again. The bought tokens remain on-chain until the player requests their transfer after the term. The current program applies a 2% fee to buy and burn PASTA, with separate network costs. For non-PASTA tokens, an executable route must be available, so the end date alone does not guarantee immediate completion. The terms page explains this; there is no automatic renewal and no market value is promised.
Will Phantom work on my phone?+
For Browser, the skill targets Phantom’s mobile in-app browser and desktop extension, with an explicit Open in Phantom fallback. A Seeker app uses the native or web wallet path supported by its architecture; a WebView must not assume Phantom is injected. Physical-device testing is part of release.
Does the skill make scores impossible to cheat?+
No. Token gating, wallet authentication and score verification solve different problems. Competitive games need server-authoritative sessions; even those cannot guarantee the absence of bots.
Are free-play ads required?+
No. Before implementing gameplay, the skill asks the game owner two separate questions: include an OnlyFridge Club ad before every free run, and include the YOUR AD HERE / sponsored-token top card during free mode? Choose both, either one or neither. An unanswered choice stays unresolved and disabled; the agent must ask, and reuses explicit answers without asking again. These choices are separate from the optional ecosystem modules. If you explicitly choose no Free Play, both ads are not applicable and the agent does not add a free mode.
Does the game have to show the DevFridge intro?+
No. Before building, the skill asks whether to show the DevFridge Games intro before the game opens. Include plays the supplied page once from files inside the APK when there is one, with a link to build a game, and Skip enters the game. Exclude adds nothing. An unanswered choice does not add it. It is separate from Free Play ads.
When do the optional ads appear?+
If you include OnlyFridge Club, its ad appears before the first free run and every retry/restart, never on pause/resume. If you include the sponsored-token top card, it is the only ad during active free play. Neither integration appears on the pass gate, its review or in pass-gated or paid sessions.
Are all ecosystem components automatically included?+
No. The core is an in-app SOL subscription plus the wallet integration for your chosen platform. Other components are selected during discovery. Existing TopShelf, rewards or bridge systems require their own supported integration; the skill does not grant access to production services.