Build a Game

Play & improve games

Every game on FreeGameStore is open source. You don't need to be a creator to make them better.

• Browse games — visit the store and play anything that interests you
• Report bugs — found a glitch? Open an issue on the game's GitHub repo
• Suggest features — ideas for new levels, modes, or improvements are always welcome
• Contribute via PRs — fork any game, make your changes, and submit a pull request. We review within 48 hours.

Become a Creator

Want to build your own game for the platform? Apply to join the creators team.

What creators get

• Your own game hosted at yourgame.freegamestore.online
• Auto-deploy on every push to main via Cloudflare Pages
• Listed in the FreeGameStore with its own game card
• Access to all game templates and the shared design system

How to apply

1. Open an issue at github.com/freegamestore-online/submissions with your game idea and GitHub username.
2. Review within 48h — we'll review your proposal and get back to you.
3. Get provisioned — once approved, you're added to the creators team and your game repo is provisioned in the org.
4. Start coding — clone your repo, pick a template, and build your game.

Requirements

• Free forever — no monetization, no ads, no paywalls
• No tracking — zero analytics, cookies, or data collection
• Open source — MIT license, public repo
• Uses the tech stack — TypeScript, React, Vite, Tailwind CSS, Cloudflare Pages

Workspace Setup

Organize your repos under a consistent folder so every tool — and every AI agent — knows where to find things.

Clone each game repo into the games/ folder:

The recommended layout:

This matches the paths in SKILLS.md, so AI agents reading the platform guide will find your code automatically. If you also build apps, use ~/dev/fas/apps/ for FreeAppStore projects.

Start Building

For approved creators — here's how to go from zero to a live game.

Templates

Pick the template that matches your game type:

Use the fgs CLI

The FreeGameStore CLI. End-to-end: scaffold, check, publish, list.

1. Install the CLI
   npm i -g @freegamestore/cli

   Requires Node 22+. Source on github.com/freegamestore-online/platform; package on npm.

2. Sign in with GitHub
   fgs login

   Device-flow OAuth — no password leaves your terminal.

3. Scaffold from a game template
   fgs init my-game --template canvas

   Eight game templates: canvas (2D arcade), grid (puzzles), 3d (Three.js), cards (card games), phaser, kaplay, pixi, babylon. Each is a runnable Vite + TypeScript project.

4. Develop locally
   cd my-game && pnpm install && pnpm dev

   Hot reload is enabled by default.

5. Run compliance checks
   fgs check

   Catches missing brand fonts, tracking SDKs, oversized bundles, missing PWA manifest, and (for games) document scroll. Games must fit the viewport — no horizontal or vertical scroll on html / body.

6. Verify the layout fits in a real browser (recommended for games)
   fgs screencheck

   Builds, serves the dist locally, and drives a real Chromium at the min_viewport_width declared in your manifest in both portrait and landscape. Fails if the canvas actually overflows. Static checks see intent; screencheck proves fit. Playwright is an opt-in peer dep; the command prompts to install on first run.

7. Publish as a game
   fgs publish

   Provisions github.com/freegamestore-online/my-game, the Cloudflare Pages project, the DNS record, the custom subdomain at my-game.freegamestore.online, and the storefront entry.

   Scriptable: pass --name, --category, --type, --oneliner, and --yes.

8. Push your code
   git push upstream main

   Auto-deploys via GitHub Actions in ~30 seconds. Future commits to main deploy automatically.

Other commands

• fgs list — see all apps and games you've published
• fgs logs my-game — tail Cloudflare Pages deployment logs
• fgs doctor — health check (Node, git, pnpm, auth, API reachability)

Full reference: github.com/freegamestore-online/platform/packages/cli

Brand and UI rules (mandated)

Every game on the platform looks predictable and consistent. The storefront, the detail pages, and every game share the same visual language so visitors learn the rhythm once and never relearn it. This is not a style guide suggestion — it's enforced by fgs check and the CI workflow that runs before merge.

• Use the template's CSS tokens. Colors, surfaces, lines, and spacing come from --paper, --ink, --muted, --accent, --line, --line-strong, --panel. Reference them via var(--accent), etc. Don't redefine them in component CSS or inline styles.
• Brand fonts only: Manrope (body) and Fraunces (display). System and monospace fallbacks are fine. No custom display fonts — even when they'd look great. Game-rendering canvases can use any pixel-fonts inside the canvas; this rule applies to DOM/HTML text only.
• No custom theme. Light/dark mode comes from prefers-color-scheme and the template's variables. Don't ship your own theme switcher or override color-scheme.

The fgs check compliance suite (run automatically before fgs publish and again in your repo's CI) enforces:

• No template placeholders — every APPNAME substituted
• No tracking SDKs — none of the 8 known trackers
• Brand fonts present — Manrope and Fraunces both referenced
• No brand overrides — no game redefines a platform CSS token outside the canonical theme file; no non-brand font-family declarations in DOM CSS
• PWA manifest — web/public/manifest.json with name, display, start_url
• Bundle size — main bundle under 300 KB gzipped

Run them locally any time:

AI-assisted development

Use Claude Code, Cursor, Codex, or any AI coding tool. Point it to our SKILLS.md and it knows the entire platform — tech stack, brand, templates, how to deploy.

Game engines

Depending on your game type, use the engine that fits best:

Need help?

• Developer questions — GitHub Discussions
• Bug reports — open an issue on your game's GitHub repo
• Platform docs — SKILLS.md (the full AI guide)