Getting things ready…
Getting things ready…
A 16-BIT HABIT TRACKER
Habits become quests. Built so an AI can run the game.
▼ SCROLL TO PLAY. THE HERO FOLLOWS YOU.


STAGE 1
An AI tool can plug into many MCP servers at once and see the status of each. It can even schedule tasks.
So I thought: why not build one of my own, to track the things I care about? The app is the scoreboard. The AI is the way in.
It was also a small, real experiment to try the stack I wanted for Stellar ERP: Supabase, Postgres, auth, row-level security and migrations.
Low stakes. If it broke, only my habits would.
Illustrative. Any MCP client can plug QuestOS in beside its other servers.
STAGE 2 · STR

Quests for today, dailies for habits, and side errands. Finishing them walks the hero toward the castle.
Real work you log that week is the damage.
STAGE 3 · INT
Skill trees are drawn like Skyrim constellations. A perk unlocks once its prerequisites are done, and old perks go rusty if you stop practising them.
I don't draw the trees. The AI does, through MCP.
Tag quests with a stat. The top stats decide your class. Press a stat to try it:

STAGE 4 · INT
YOUBuild me a skill tree for learning Rust, then plan today's quests around my rusty skills.
AIcreate_skill_tree add_quests
Illustrative prompt. It can also draw your avatar, set the weekly boss and log what you did.
The AI proposes, the server decides. Tokens are hashed, every row belongs to one user, and limits (like the node count of a tree) are checked server-side, not trusted from the model.
STAGE 5 · WIS
= 110 XP → LV 2
Every point of XP is a row. Level, skill progress and the boss's health are all worked out from it.
Next.js 14React 18TypeScriptTailwindSupabase AuthVercel
STAGE 6 · FINAL
STACK
Measured from the project's own source: 89 files.
Libraries & tools