<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>vibegame</title>
    <subtitle>Guides and notes on vibe coding, game development, and AI tools for building games with AI-assisted workflows.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://vibegame.uk/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://vibegame.uk"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-07-09T00:00:00+00:00</updated>
    <id>https://vibegame.uk/atom.xml</id>
    <entry xml:lang="en">
        <title>Extract - Manual Layering</title>
        <published>2026-07-09T00:00:00+00:00</published>
        <updated>2026-07-09T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://vibegame.uk/docs/sprite/extract-manual-layering/"/>
        <id>https://vibegame.uk/docs/sprite/extract-manual-layering/</id>
        
        <content type="html" xml:base="https://vibegame.uk/docs/sprite/extract-manual-layering/">&lt;p&gt;This guide introduces &lt;strong&gt;Extract - Manual Layering&lt;&#x2F;strong&gt;, a workflow focused on stronger human control during AI-assisted extraction.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;extract-manual-layering&#x2F;base_image_.webp&quot; alt=&quot;Base image before manual extraction setup&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
&lt;h2 id=&quot;step-1-manually-select-the-full-art-region&quot;&gt;Step 1: Manually select the full art region&lt;&#x2F;h2&gt;
&lt;p&gt;Select the complete area that contains the target art elements. Manual selection gives you finer alignment against AI auto-extraction and reduces unwanted region drift.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;extract-manual-layering&#x2F;step1_manual_layering_.webp&quot; alt=&quot;Manual selection for the target region&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
&lt;h2 id=&quot;step-2-manually-separate-art-layers-and-text-layers&quot;&gt;Step 2: Manually separate art layers and text layers&lt;&#x2F;h2&gt;
&lt;p&gt;Explicitly label which layers are visual art and which are text. This separation allows deeper influence on art-layer attributes, enabling stronger intervention in later processing.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;extract-manual-layering&#x2F;step2_rects_by_manual_.webp&quot; alt=&quot;Manual rectangles and region typing&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
&lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;extract-manual-layering&#x2F;step2.2_confirm_text_layer_.webp&quot; alt=&quot;Text layer confirmation after manual separation&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
&lt;h2 id=&quot;step-3-generate-the-processed-result&quot;&gt;Step 3: Generate the processed result&lt;&#x2F;h2&gt;
&lt;p&gt;Run generation after manual layering is confirmed. The output reflects your boundary decisions and layer typing rules.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;extract-manual-layering&#x2F;step3_ai_output_.webp&quot; alt=&quot;AI output after manual layering workflow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
&lt;p&gt;Manual processing is powerful for strict boundary control, but it can still encounter additional processing boundaries in complex scenes.&lt;&#x2F;p&gt;
&lt;p&gt;After processing, all output images are automatically assigned meaningful names that map clearly to each visual result, which makes later retrieval and asset management easier.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Getting Started</title>
        <published>2026-06-26T00:00:00+00:00</published>
        <updated>2026-06-26T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://vibegame.uk/docs/getting-started/"/>
        <id>https://vibegame.uk/docs/getting-started/</id>
        
        <content type="html" xml:base="https://vibegame.uk/docs/getting-started/">&lt;p&gt;This guide’s author, a beginner, experimented with and validated an “AI-first” game development workflow: identifying common production obstacles, utilizing AI-generated technologies to eliminate bottlenecks, and transforming outputs into assets directly importable into the game engine.&lt;&#x2F;p&gt;
&lt;p&gt;This process involves comparing and contrasting different tools, highlighting their strengths and weaknesses. &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;vberai.com&#x2F;studio&quot;&gt;VberAI Studio&lt;&#x2F;a&gt; is the core tool in this project: it provides an experience closer to native AI-driven game development.&lt;&#x2F;p&gt;
&lt;p&gt;The goal is simple: to let AI handle the time-consuming and labor-intensive content creation work.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Getting Started</title>
        <published>2026-06-26T00:00:00+00:00</published>
        <updated>2026-06-26T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://vibegame.uk/exp/getting-started/"/>
        <id>https://vibegame.uk/exp/getting-started/</id>
        
        <content type="html" xml:base="https://vibegame.uk/exp/getting-started/">&lt;p&gt;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.&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
