Sundog

Sundog is the game-building project.

It used to be called Daydream Studio, which still describes the feeling pretty well: start with a fuzzy game idea, talk it into shape, and let the tool help with structure, assets, engine wiring, and the boring glue around the fun part.

Why I Like This One

Games expose whether an AI tool has any taste.

A business app can hide behind forms and tables. A game cannot. If the interaction feels dead, you know immediately.

What It Is

• Tauri desktop shell.
• Local-first storage.
• Godot/MCP bridge experiments.
• Companion tooling.
• A place to learn how agents handle creative projects where "correct" is not enough.

The Real Feature List

• Five collaborating agents: Planner, Code, Scene, Art, and QA.
• A Godot 4 MCP bridge with editor control tools for scenes, scripts, resources, project settings, and validation.
• A Unity bridge reference so the idea is not locked to one engine forever.
• A companion CLI that installs the plugin, launches the proxy, and keeps the editor connection boring.
• Local-first desktop storage in SQLite and the filesystem, with the web path using Supabase when running outside Tauri.
• Pixel art generation experiments with palette normalization and consistency constraints.
• A self-healing QA loop that tries to detect broken scenes, patch scripts, and re-run checks without making the user babysit the glue.

Why There Is No Tiny Demo Card

Sundog needs more room than a board tile. The interesting part is the pipeline and the editor bridge, not a little hat picker. It should stay on the board as a detailed project, but the demo should live in the actual product surface where the engine connection can breathe.

Try The Important Pieces

I do not want to cram the whole desktop app into a tiny card. The board should show the interesting pieces and then let people jump out when they want the real thing.