<?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: Corbino</title>
    <description>The latest articles on DEV Community by Corbino (@corbindebug).</description>
    <link>https://dev.to/corbindebug</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%2F4057487%2F51449f89-a824-4fa4-90b7-73255127dbcc.png</url>
      <title>DEV Community: Corbino</title>
      <link>https://dev.to/corbindebug</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/corbindebug"/>
    <language>en</language>
    <item>
      <title>I Used AI to Build a Final Fantasy-Inspired Dashboard for AI Agents, Because Spreadsheets Are a Crime Against Morale</title>
      <dc:creator>Corbino</dc:creator>
      <pubDate>Sat, 01 Aug 2026 05:52:56 +0000</pubDate>
      <link>https://dev.to/corbindebug/i-used-ai-to-build-a-final-fantasy-inspired-dashboard-for-ai-agents-because-spreadsheets-are-a-4jnd</link>
      <guid>https://dev.to/corbindebug/i-used-ai-to-build-a-final-fantasy-inspired-dashboard-for-ai-agents-because-spreadsheets-are-a-4jnd</guid>
      <description>&lt;p&gt;I am a Canadian realtor, not a career software engineer. That is probably why I had no emotional attachment to the normal way dashboards are supposed to look.&lt;/p&gt;

&lt;p&gt;I had a practical problem. I was using different AI workers and tools for different jobs, but the screens used to monitor them all felt the same: grey tables, status labels, and a pile of information that technically existed but did not help me understand the team at a glance.&lt;/p&gt;

&lt;p&gt;The best interface I could remember for understanding a team was not business software. It was a classic JRPG party menu.&lt;/p&gt;

&lt;h2&gt;
  
  
  The party-menu advantage
&lt;/h2&gt;

&lt;p&gt;A good party screen answers useful questions immediately:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who is in the party?&lt;/li&gt;
&lt;li&gt;What role does each person have?&lt;/li&gt;
&lt;li&gt;Who is active right now?&lt;/li&gt;
&lt;li&gt;Who is running low?&lt;/li&gt;
&lt;li&gt;What quest comes next?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is almost exactly what I needed from an AI-agent dashboard.&lt;/p&gt;

&lt;p&gt;So I built RPG Party Dashboard, using AI as the building partner. It is Final Fantasy-inspired in the broad classic-JRPG sense, but unaffiliated with Square Enix or any game publisher.&lt;/p&gt;

&lt;h2&gt;
  
  
  HP means Headroom Points
&lt;/h2&gt;

&lt;p&gt;The most useful idea in the dashboard is the HP bar.&lt;/p&gt;

&lt;p&gt;In this project, HP does not mean health. It means Headroom Points: a simple visual estimate of how much useful room a worker or conversation has left before the thread should be reborn into a fresh chat.&lt;/p&gt;

&lt;p&gt;That turns an abstract technical problem into a signal I can understand instantly. Healthy worker? Green bar. Running low? Warning. Nearly done? Rebirth the chat before it falls apart.&lt;/p&gt;

&lt;p&gt;Call it remaining capacity if you want to sound respectable. I will keep the HP bar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Intentionally boring technology
&lt;/h2&gt;

&lt;p&gt;The public version uses plain HTML, CSS, and JavaScript. There is no account, backend, build step, or framework dependency.&lt;/p&gt;

&lt;p&gt;That was deliberate. I wanted someone to clone the project, change &lt;code&gt;dashboard.config.js&lt;/code&gt;, and understand what they were looking at without first joining a religion based on package managers.&lt;/p&gt;

&lt;p&gt;The public repo ships with fictional sample data. You can use the built-in CSS characters or point the configuration at licensed character art of your own.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI was the building partner
&lt;/h2&gt;

&lt;p&gt;I did not sit down pretending to be a career developer. I brought the operating idea, the business problem, the visual standard, and a willingness to keep correcting the thing until it felt right. AI helped with implementation, iteration, checks, and packaging.&lt;/p&gt;

&lt;p&gt;That is part of the point.&lt;/p&gt;

&lt;p&gt;Small operators can now build internal tools that fit how they actually think. We do not have to wait for a software committee to approve the colour blue or add a feature three quarters from now.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it could become
&lt;/h2&gt;

&lt;p&gt;The current public project is intentionally small, but the party metaphor could support:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;local AI-agent status feeds&lt;/li&gt;
&lt;li&gt;home-lab and self-hosted services&lt;/li&gt;
&lt;li&gt;team links and current assignments&lt;/li&gt;
&lt;li&gt;tool health checks&lt;/li&gt;
&lt;li&gt;stream-deck or creator command centres&lt;/li&gt;
&lt;li&gt;context/headroom receipts&lt;/li&gt;
&lt;li&gt;personal side quests and project boards&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The repo is MIT licensed. Clone it, change it, tell me what is dumb, or show me what your party looks like.&lt;/p&gt;

&lt;p&gt;Live demo: &lt;a href="https://corbin-debug.github.io/rpg-party-dashboard/" rel="noopener noreferrer"&gt;https://corbin-debug.github.io/rpg-party-dashboard/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://github.com/corbin-debug/rpg-party-dashboard" rel="noopener noreferrer"&gt;https://github.com/corbin-debug/rpg-party-dashboard&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Productive on purpose. Entertaining on purpose. Nostalgic on purpose.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
