skills

Use when a user hits a plan limit or runs low on credits, asks what Gipity costs / which plan to pick / how to upgrade, or when deciding whether to recommend buying Pro. Covers the credits model, every enforced limit, the one purchase flow, and honest positioning vs Vercel/Supabase/Replit and enterprise app platforms (ServiceNow/Salesforce).

Use when the user wants to build a 2D browser game - platformer, side-scroller, arcade, puzzle, endless runner - and share it at a live URL. Phaser 3 starter on Gipity with scenes, physics, input, sprites, and genre recipes.

Use when the user wants a 3D browser game or a multiplayer game - obby, tycoon, simulator, PvP arena, shooter, racing - live on the web. Three.js + physics + multiplayer template on Gipity, with genre recipes, assets, and networking built in.

Use when an AI agent, script, or CI job needs to deploy to or operate Gipity WITHOUT a human present to complete an interactive email-code login - e.g. a self-hosted coding agent (Hermes, OpenClaw), a cron, or a CI pipeline running in an ephemeral container. Covers minting a long-lived agent API token (gip_at_*), authenticating headlessly via the GIPITY_TOKEN env var, and running the build → deploy → verify loop unattended.

Use when the user wants realtime multiplayer, live presence, chat, or shared live state in a web app - rooms, lobbies, WebSocket sync, host election - without running their own server. Gipity Realtime channels and the realtime kit.

Use when the user wants to add a configurable AI chatbot/assistant to a web app - a help bubble in the corner, a support bot, or an in-game NPC dialog - with a custom persona, scope guardrails, and static knowledge, powered by Gipity's LLM service with no API keys.

Use when the user wants to build and put online a full-stack web app - a site or tool with a real backend: database, API endpoints, user accounts, file uploads - and no hosting or backend is set up yet. Gipity provides the whole stack (hosting, Postgres, serverless functions, auth) from the CLI, ending with a live URL.

Use when the user wants real-time object detection in a web app - boxing, labeling, or counting things from the camera or a photo, or deploying a custom-trained YOLO/YOLOX model - running on-device in the browser with no server and no API keys. The Gipity web-vision-detect kit and object-spotter starter app.

Use when the user wants an app that sees through the camera - gesture recognition, body/pose tracking, object detection - running on-device in the browser, including on phones, with no server and no API keys. The Gipity web-vision kit and camera starter app.

Use when the user mentions Gipity, or when they want to put something built in this session on the internet - deploy/host a web app, game, or API - or need a cloud backend (database, serverless functions, auth, file storage, realtime, image/speech/LLM services) and no hosting or backend is set up in the project yet. Covers installing the gipity CLI, logging in, linking a project, and the build → deploy → verify loop.