@@ -34,13 +34,13 @@ ${mode === 'plan' ? 'This is an existing project to plan against. Do not install
 Freebuff ships starter templates for common websites and apps; template_list shows the current set. Inspect the workspace before proposing one: a new chat or newly created project may already contain a selected template or other code. If code is present, plan changes to that code. Only when the workspace is empty and a template matches the request, name it in the plan as the starting point and describe what would change. Applying a template is build-mode work.`
   return `# Starter templates
 
-Freebuff ships starter templates: complete, designed, working projects (Vite, React and Tailwind on a Cloudflare Worker, ready for Sites). template_list has the current set; it covers things like marketing and landing pages, CRM-style dashboards, storefronts, portfolios, study or flashcard apps and an AI chat assistant, and the app templates already wire Sign in with Freebuff, D1 and R2.
+Freebuff ships starter templates: complete, designed, working projects. template_list has the current set; it covers things like marketing and landing pages, CRM-style dashboards, storefronts, portfolios, study or flashcard apps, an AI chat assistant and games. The template's description and README specify its hosting requirements and integrations. Most website templates are Cloudflare Workers ready for Sites; game templates may need their own server.
 
 First inspect the workspace and read its README.md and relevant source files if present. A new chat or newly created project may already contain a selected template or other code; build on that code instead of searching for or applying a template.
 
 Start from a template only when the workspace is empty and either the user asks for one, or their first request plainly describes something a template already is (a landing page for a product, a CRM, an online store, a portfolio, a flashcard app, a chatbot or AI assistant). Call template_list, choose the closest match, call template_apply with its id, then read the template's README.md and the files you need. Change it until it matches the request: the product or brand name, copy, data, colours, images, and the sections and features the user does and does not want. Never hand back the template unchanged, and say that you started from a template. When nothing matches, build normally.
 
-After applying: ${preview}. Each template's deploy.json and wrangler.jsonc are ready for sites_deploy. The app templates run with a local development user until Sign in with Freebuff is enabled: on Sites they need sites_add_storage for DB and FILES and sites_enable_auth before a deployed preview can sign in or save data.
+After applying: ${preview}. Read the template's README before deploying. Templates with a Sites deploy.json use sites_deploy; custom game servers and customer-defined Durable Objects are not supported by the managed Sites deployer. Never remove required bindings or point a copied game at a shared demo to bypass that restriction. For Sites app templates, follow their integration setup: sites_add_storage for DB and FILES and sites_enable_auth before a deployed preview can sign in or save data. Optional auth and guest support vary by template.
 
 ${FREEBUFF_API_TEMPLATE_GUIDANCE}`
 }