<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Damien</title>
    <description>The latest articles on DEV Community by Damien (@damien_e6e6109a325a98ab5f).</description>
    <link>https://dev.to/damien_e6e6109a325a98ab5f</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4150529%2F34e888cd-d99e-40a0-a4db-47f4b7f01e59.jpg</url>
      <title>DEV Community: Damien</title>
      <link>https://dev.to/damien_e6e6109a325a98ab5f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/damien_e6e6109a325a98ab5f"/>
    <language>en</language>
    <item>
      <title>Making an AI assistant check its own work in Unreal Engine 5</title>
      <dc:creator>Damien</dc:creator>
      <pubDate>Fri, 23 Oct 2026 07:10:27 +0000</pubDate>
      <link>https://dev.to/damien_e6e6109a325a98ab5f/making-an-ai-assistant-check-its-own-work-in-unreal-engine-5-6n6</link>
      <guid>https://dev.to/damien_e6e6109a325a98ab5f/making-an-ai-assistant-check-its-own-work-in-unreal-engine-5-6n6</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Falqpnfjfyvbrxwc6z1ik.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Falqpnfjfyvbrxwc6z1ik.jpg" alt=" " width="800" height="800"&gt;&lt;/a&gt;&lt;a href="https://ue-cortex.vercel.app/" rel="noopener noreferrer"&gt;UE-cortex&lt;/a&gt;&lt;br&gt;
I build Unreal Engine plugins, and I wanted to see how far an AI assistant can get on a new UE5 project if it works with a plan and gets checked, rather than just chatting. The result is ue-cortex, a plugin sold on Fab. This post is about the method, and about where it does not work.&lt;br&gt;
ue-cortex does not call a model. You bring your own assistant (Claude Code, Cursor or Codex). The plugin gives it 11 specialist playbooks (systems C++/GAS, multiplayer, world building, Blueprint, DevOps/build, UI, audio, cinematics, performance, technical art, AI) and 83 reference files, and it checks what happens in the editor.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Game design document first. The run starts with cortex_start and the assistant drafts a GDD. The plugin validates it: every feature needs testable acceptance criteria and assigned agents. For a small example, "Use ue-cortex to build a dash ability with a stamina cost" becomes a GDD with acceptance lines like "Shift moves the player 6 m", "costs 25 stamina" and "1.5 s cooldown". The GDD is written into the project as Docs/UECortex/GDD.json and GDD.md, so you can read and edit it before anything is built.&lt;/li&gt;
&lt;li&gt;An approved plan, split by specialist. After you approve, cortex_approve_plan builds a dependency-ordered task graph, one step per agent the GDD uses.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What it does not do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It covers roughly half to two-thirds (50-65%) of the engineering scaffolding of a new project.&lt;/li&gt;
&lt;li&gt;Art, level design, tuning and polish are human work.&lt;/li&gt;
&lt;li&gt;The assistant cannot play the game and cannot create a brand-new level.&lt;/li&gt;
&lt;li&gt;A generated project is a compiling, running starting framework, not a finished game.&lt;/li&gt;
&lt;li&gt;It is tested and ready on UE 5.8 only. UE 5.6-5.7 is a possible later version, not a commitment.&lt;/li&gt;
&lt;li&gt;Compile verification is Windows-only, because it uses Live Coding.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>gamedev</category>
      <category>claude</category>
      <category>computerscience</category>
    </item>
    <item>
      <title>Kompyla: an open-source LLM compiler that turns scattered sources into a self-updating wiki</title>
      <dc:creator>Damien</dc:creator>
      <pubDate>Tue, 29 Sep 2026 17:12:43 +0000</pubDate>
      <link>https://dev.to/damien_e6e6109a325a98ab5f/kompyla-an-open-source-llm-compiler-that-turns-scattered-sources-into-a-self-updating-wiki-48og</link>
      <guid>https://dev.to/damien_e6e6109a325a98ab5f/kompyla-an-open-source-llm-compiler-that-turns-scattered-sources-into-a-self-updating-wiki-48og</guid>
      <description>&lt;ul&gt;
&lt;li&gt;Kompyla is a self-hosted, MIT-licensed research agent: point it at a domain, and it pulls in web pages, arXiv preprints, GitHub repos, RSS feeds, and YouTube transcripts on a schedule, then compiles them into a structured, cited wiki.&lt;/li&gt;
&lt;li&gt;It ships two ways: a standalone CLI + Streamlit UI + Docker app, and a separate, much thinner Agent Skill that lets a coding agent (Claude Code, Cursor, Codex) drive an existing KB directly, reusing the host's own model.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;pip install kompyla&lt;/code&gt; is live today.&lt;/li&gt;
&lt;li&gt;Github repository: &lt;a href="https://github.com/damien220/kompyla" rel="noopener noreferrer"&gt;https://github.com/damien220/kompyla&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>python</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
