# OpenGame — Full LLM Context

## Site purpose
OpenGame helps visitors create playable browser games with an AI-assisted 3D game workflow. The public site is focused on the landing experience, pricing clarity, game examples, templates, community browsing, and the Studio workbench.

## Canonical origin
- Canonical origin: https://opengame.app
- The canonical production host is expected to be https://opengame.app.
- The www host is redirect-only and should not be treated as a separate canonical site.

## Public route map
- https://opengame.app/ — public landing page and primary product narrative.
- https://opengame.app/pricing — public pricing and credits information.
- https://opengame.app/studio — Studio entry for generating and previewing games.
- https://opengame.app/games — game examples and browse entry.
- https://opengame.app/showcase — curated game showcase.
- https://opengame.app/templates — game template browsing and remix entry.
- https://opengame.app/community — public community game list.
- https://opengame.app/community/leaderboard — public leaderboard entry.
- https://opengame.app/privacy-policy — privacy policy.
- https://opengame.app/terms-of-service — terms of service.

## Private or non-index targets
- /admin, /settings, /api, runtime callbacks, account billing pages, and user-specific history pages are not public crawl targets.
- pSEO game-type pages and legacy compatibility pages may exist outside the launch sitemap until those pages are audited.
- Authentication, checkout, webhook, runtime callback, and generation task endpoints should be treated as application routes, not content pages.

## Runtime architecture
- The public V2 app is a TanStack Start app deployed to Cloudflare Workers.
- Production data is served from Cloudflare D1 with generated artifacts stored in R2.
- Studio runtime work is delegated to FastClaw through the first-party site API.
- Generated artifacts are stored through the configured R2 binding.
- Secrets such as auth, runtime callback, OAuth, and payment tokens are Worker secrets or operator-managed secrets, not public configuration.

## Analytics and Search Console
- Google Analytics, Plausible, and Search Console should be configured for opengame.app.
- Analytics script injection is controlled by server-side site configuration and should be verified on the deployed host.

## Machine resources
- robots.txt: https://opengame.app/robots.txt
- sitemap.xml: https://opengame.app/sitemap.xml
- llms.txt: https://opengame.app/llms.txt