Submit with your agent

No Git experience needed

Ask the Game Builder skill: Prepare and submit my game to the hackathon gallery. Handle the GitHub workflow for me and ask only for missing decisions. Your agent prepares evidence and the registry file, validates it, creates or reuses your fork, opens the PR and helps resolve feedback. If needed, it guides you through GitHub sign-in without asking for a password or access token.

Review and publication

The submission target is mikeminer/devfridge, branch master. Each game adds one metadata file at scan/data/hackathon-projects/<slug>.json. Its source and playable demo stay in your own repository and hosting. Your agent follows the repository template and validates the file before opening a PR.

The owner reviews the game, evidence and ownership. A reviewed merge triggers the production build, which automatically adds the card to the gallery. Approval alone is not publication: merge and deployment must succeed. Your agent reports the real PR link and status. Dates, prizes and final competition eligibility remain to be announced; a listing is not a prize or an audit.

Your project package

• Name, one-sentence pitch, team aliases and your chosen public contact.
• Playable HTTPS URL and repository URL with the reviewed commit hash.
• Short gameplay video showing desktop, mobile and the real/labelled gate flow.
• Exact Solana mint, token program, network, launch status and supported extensions—or an explicit pre-launch fixture declaration.
• Minimum amount, duration and aggregation policy, expiry behaviour, redemption disclosures and known routing limitations.
• Setup commands, environment-variable names without values, asset licences and dependency notes.
• AI tools used, prompt/build log, human review notes and a summary of what existed before this project.
• Test evidence, device/browser details, security limitations and what remains unfinished.

Suggested demo sequence

• Explain the community and game loop in one sentence.
• Play a complete run, show the result and restart.
• Show the access policy and fee disclosure, then a qualifying and non-qualifying gate state.
• Demonstrate the mobile layout and wallet cancellation recovery.
• Show the relevant code, test results and one honest limitation.

Final self-review

Open your URL in a fresh browser. Can a reviewer understand and try the game without buying tokens? Can a new developer reproduce it from the specified commit? Are all simulation labels visible? Confirm that no private keys, API secrets or personal records are included.