<?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: ElephantLogix Studio</title>
    <description>The latest articles on DEV Community by ElephantLogix Studio (@elephantlogix).</description>
    <link>https://dev.to/elephantlogix</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%2F4244659%2Ff3fc5450-210c-4df9-afbe-19956d0ac929.png</url>
      <title>DEV Community: ElephantLogix Studio</title>
      <link>https://dev.to/elephantlogix</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/elephantlogix"/>
    <language>en</language>
    <item>
      <title>What my AI brief missed when I built an interactive three.js inn</title>
      <dc:creator>ElephantLogix Studio</dc:creator>
      <pubDate>Sat, 14 Nov 2026 15:00:00 +0000</pubDate>
      <link>https://dev.to/elephantlogix/what-my-ai-brief-missed-when-i-built-an-interactive-threejs-inn-15kg</link>
      <guid>https://dev.to/elephantlogix/what-my-ai-brief-missed-when-i-built-an-interactive-threejs-inn-15kg</guid>
      <description>&lt;p&gt;I wanted a website for ElephantLogix Studio, where I build puzzle and educational games. I wanted visitors to feel as if they had arrived somewhere: a wuxia inn with ink-wash artwork, characters, rooms and small things to interact with.&lt;/p&gt;

&lt;p&gt;This is what I learned while turning that idea into an interactive three.js website with AI assistance.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the experience, then name the tools
&lt;/h2&gt;

&lt;p&gt;My original brief described the studio's games, the Chinese ink-wash style, familiar inn characters, exploration, microanimations and support for desktop, tablet and mobile. It also specified three.js.&lt;/p&gt;

&lt;p&gt;Those constraints gave the work a direction, but a list of ingredients is not an interaction specification. A stronger brief also answers: Where does the visitor arrive? What should they notice first? How do they move between sections? What should happen when they tap something?&lt;/p&gt;

&lt;p&gt;For another build, I would separate the brief into four parts: the visitor's goal, the visual references, the actual interactions, and the conditions for calling a feature finished. For example, “playful dim sum” becomes “visitors can rearrange the steamers, see the result immediately, and still reach the navigation on a phone.”&lt;/p&gt;

&lt;h2&gt;
  
  
  Build the code concept before polishing the artwork
&lt;/h2&gt;

&lt;p&gt;I first worked on the concept in code. Claude helped turn the brief into a three.js prototype and iterate on the layout and interactions. That gave me a place to evaluate assets rather than judging each image on its own.&lt;/p&gt;

&lt;p&gt;A practical sequence is to establish the arrival view, section navigation and clickable areas before committing to final artwork. Otherwise, a beautiful asset can dictate a layout that is awkward to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  A still image and an animated character solve different problems
&lt;/h2&gt;

&lt;p&gt;The original characters felt flat. I then asked for AutoSprites assets so the characters could be animated and inhabit a 2.5D environment. Astra artwork and AutoSprites animation played different roles in the process.&lt;/p&gt;

&lt;p&gt;The lesson was to specify behavior separately from appearance. A character brief should describe what it does, where it stands, how much space its movement needs and how it sits against the background—not just its clothing and art style.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inspect the composition inside the real layout
&lt;/h2&gt;

&lt;p&gt;One artwork iteration gave the scene two suns. Other problems were less funny: framing could crop the lower part of the inn, and layouts that worked on desktop needed another pass on mobile.&lt;/p&gt;

&lt;p&gt;I would turn these into explicit review questions: Is the whole intended building visible? Can text be read without covering the important interaction? Does the scene still make sense at a narrow screen width? Does the visitor know what can be clicked?&lt;/p&gt;

&lt;p&gt;These are visual and usability checks. A successful code generation does not answer them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Small interactions give visitors something to do
&lt;/h2&gt;

&lt;p&gt;The inn includes section transitions, a menu, game previews and rearrangeable dim sum steamers. Those little actions help communicate the kind of playful experience I wanted the studio to make.&lt;/p&gt;

&lt;p&gt;They also create scope. Each interaction needs a clear trigger, visible feedback and a sensible result. I found it more useful to ask for a specific behavior than to ask for the whole page to be “more professional.”&lt;/p&gt;

&lt;h2&gt;
  
  
  Give sound a role
&lt;/h2&gt;

&lt;p&gt;The workflow also used LotsOfSounds for effects and Suno for music, including “Inn at Dusk.” The background track and interaction sounds have different jobs. In the build film I included a music-only section so viewers could actually hear the inn's soundtrack.&lt;/p&gt;

&lt;p&gt;For a similar site, I would make audio controls and the silent experience part of the brief from the beginning.&lt;/p&gt;

&lt;h2&gt;
  
  
  The finished experience and the build diary
&lt;/h2&gt;

&lt;p&gt;You can &lt;a href="https://elephantlogix.com" rel="noopener noreferrer"&gt;explore the inn for free&lt;/a&gt;. I also made a 4:43 film showing the brief, iterations, artwork mistake and final website walkthrough.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/Gds486Ve-JI" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The opening uses a filming camera in the actual 3D scene; it should not be mistaken for the exact camera controls of the public website. The ending demonstrates the public experience. Game availability varies, and the Arrow Dungeon gameplay cutaway is a separate app.&lt;/p&gt;

&lt;p&gt;Tools used across the project: Claude Fable 5.2, three.js, Astra, AutoSprites, LotsOfSounds and Suno. This article was prepared with AI assistance from the project's build history and creator feedback.&lt;/p&gt;

&lt;p&gt;What would you put in the brief to make a playful 3D website easier to navigate?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
