Getting Started | vibegame

← Home

Exp

Docs →

This section contains a more complex and varied summary of experiences. Unlike documents which are designed to solve a very specific problem, this section tends to describe a particular approach or summarize the most direct experience gained from a particular path.

How it felt

Titles and descriptions for every current Exp note—open a card when you want to see how that path felt in practice.

Convert

Layered design files into engine-ready scenes.

Exporting Figma designs to Godot: post-processing after Figma and Cursor Figma plus Cursor still leaves design-file post-processing open: layered, engine-shaped export that an AI IDE can read. VberAI Studio sits in the middle; Godot MCP keeps editor context.

Sprite

Sprite sheets, cleanup, and reskin on existing game art.

AI game asset generator, batch game art AI, one-click game theme reskin Festival reskins on existing game art are batch jobs with a shared prompt. Studio Reskin keeps structured settings and replaces presentation; scale needs batch API and the original environment parameters.

What does pixel sprite sheet cleanup look like without AI-assisted tools? A walkthrough of pixel sprite sheet cleanup with general tools—Grok Image, GPT Image 2, Pixian, Figma, Ezgif—and where the friction sits versus one-click products.

Using AI to generate sprite sheets and clean them up into game-ready pixel art Friction points when turning AI sprite sheets into engine-ready assets—and where VberAI helps with classification, structure, context rules, and metadata.

Localization

On-image text in store frames and UI sprites.

Localization of steam page: Almost all agencies use AI tools Two Image Translate runs—on a store marketing frame and on a game UI sprite—show the feature is tuned for sprite work, not store promo images.