Claude Code on FreeGameStore

Build a free game using Claude Code. The agent reads the platform's SKILLS.md and knows the brand rules, the CLI, and the deploy flow before it writes a line of code.

Set up Claude Code

1. Install Claude Code
   npm i -g @anthropic-ai/claude-code

   Or follow the latest install instructions at claude.com/claude-code.

2. Scaffold the game
   fgs init my-game --template canvas cd my-game
3. Add platform context to CLAUDE.md

   From inside the scaffolded directory:

   cat >> CLAUDE.md <<'EOF' # Platform: FreeGameStore Read https://freegamestore.online/skills.md for platform skills, brand mandates, compliance rules, and the publish flow. When this user asks for changes, edit web/src/App.tsx and supporting files. Use the existing Shell layout. Never add trackers, custom display fonts, or third-party scripts beyond Google Fonts. EOF

   Claude Code reads CLAUDE.md automatically at the start of every session — your platform context loads with no extra setup.

4. Start a session
   claude

Or skip the setup — connect the MCP server

The FreeGameStore MCP server lets Claude Code build, publish, and improve games without leaving the editor. Connect once:

Then there are two ways to build:

• Claude writes the code, the MCP ships it — create_game provisions + scaffolds + deploys a live game, then update_files / read_file / list_files iterate (each push auto-redeploys).
• You just prompt — the platform's VibeCode agent writes + deploys it — agent_build hands the whole build to the server-side agent (bring your own AI key), agent_status polls progress.

Authenticated tools take your fgs login session token via mcp-remote's --header "Authorization: Bearer <token>". Full guide: freegamestore.online/docs/mcp.

Prompt the build

Tell the agent what you want. Some examples:

Iterate

1. Run the dev server
   cd my-game && pnpm install && pnpm dev

   The agent will tell you which file it edited; refresh the browser to see the change.

2. Run compliance checks
   fgs check

   Catches missing brand fonts, tracking SDKs, oversized bundles, and missing PWA manifest before publish.

3. Publish
   fgs publish --store games

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

4. Push your code
   git push upstream main

   Auto-deploys via Cloudflare Pages in ~30 seconds. Future commits to main deploy automatically.

What the AI knows (and doesn't ask you for)

Once SKILLS.md is loaded, the agent will:

• Use the platform's CSS tokens (--accent, --ink, --paper, …) — never redefine them.
• Use Manrope (body) + Fraunces (display) — never custom display fonts.
• Refuse to add Google Analytics, Plausible, Mixpanel, or any tracker.
• Use localStorage for persistence (or @freegamestore/games KV for connected games).
• Push to main for deploy. Never wrangler pages deploy manually.
• Never ask you for Cloudflare or GitHub tokens.

The compliance suite (fgs check) enforces all of the above on every push, so even if the AI slips, the platform catches it.

Get the source

The CLI, SDK, and compliance package live at https://github.com/freegamestore-online/platform. Reading the source is allowed — and often illuminating when you're trying to coax a difficult prompt.

Tips for Claude Code specifically

• Use /init in a fresh repo to have Claude generate a richer CLAUDE.md tailored to your codebase.
• /agents can spawn parallel exploration agents — useful when you ask "what's the cleanest way to add feature X to this codebase?"
• The --continue flag resumes the last session in the current directory; great for multi-day projects.