Before you start
A coding agent, browser and an empty practice repository.
Why this lesson exists
This lab adapts the “Build a JRPG-Inspired Personal Operating System” project write-up into a practice build. The time is an estimated first session, not a promise to finish a production system. Use the public repository as a reference when available; the exercise can be built with original sample content.
Do the exercise
Define the practice version
Keep the first version to task creation, completion and a short review. Use invented tasks and no health or account data.
Build step 1
Define a `Quest` type with title, status, effort, and due date.
Build step 2
Save quests locally and build create, complete, and archive actions.
Build step 3
Add one “Today” view instead of ten dashboards.
Build step 4
Add a morning question: “What would make today count?”
Build step 5
Add an evening review that compares intention with outcome.
Build step 6
Add cloud sync and AI only after the manual loop works.
Run the experiment
Add two quests, complete one, reload and inspect the Today view. The evening summary must distinguish planned from completed work using those records.
A prompt to adapt
Replace the bracketed parts with your own practice details.
Work in a disposable practice project. Explain any setup requirements before changing files. Build one small step at a time and show how I can check it. Act as a product architect. Design a local-first daily planning app with quests, a morning standup, and an evening review. Create TypeScript domain types and a repository interface that can use IndexedDB today and Supabase later. Keep AI optional. Review this personal dashboard for cognitive overload. Rank every visible module by whether it helps the user choose the next action. Recommend what to hide, combine, or delay. My first-version boundary: Keep the first version to task creation, completion and a short review. Use invented tasks and no health or account data.
Run this experiment
Add two quests, complete one, reload and inspect the Today view. The evening summary must distinguish planned from completed work using those records.
Check your result
Use evidence from your output. A confident explanation from the AI is not enough.
- A completed quest stays completed after reload.
- The review uses stored records rather than invented history.
- The core loop works without an AI API.
If it isn’t working
If a dashboard grows before task persistence works, pause new screens and fix the create-complete-reload loop.
Optional. Progress stays in this browser.
Where this came from
Public project repository ↗. The practice lesson is an adaptation, not a verbatim transcript. About the sources.
Prepared September 2026. Tools and interfaces change; use current official setup instructions. Session lengths are estimates.