Lucas WintherandClaude Opus 5
cc896c1c60
Three pieces of work, eight commits. Month view (redesign sub-project 2 of 4). The header reads income -> allocation meter -> spend, and answers "did I overspend" at the month level instead of making you read down a column. The carry meter now belongs to its own row rather than sitting equidistant between two. Phone width worked at all for the first time: the five-column table became two-line blocks, so Spent and Remaining are no longer off-screen behind a horizontal scroll. Reset to a fresh install, in Settings. store.reset() is the same call load() makes on a first run, so "reset" and "a brand-new browser" cannot drift apart. It backs up before it destroys, and aborts if the backup fails. Docs restructure. AGENTS.md is now the single agent guide, with CLAUDE.md and GEMINI.md as pointers; the long-form docs live in docs/ without the superpowers nesting; TODO.md holds only outstanding work; DECISIONS.md indexes what was chosen and over what. Four claims that were no longer true are corrected, and a guard now fails the build when documentation names a path that does not exist. 446 tests, tsc clean, build clean on both FX paths. Verified in real Chrome in both themes at 1280px and 390px, and the reset was clicked through and read back out of IndexedDB. Still needs a human: how it all looks and feels, real offline behaviour, the install prompt, and whether the pre-destructive backup lands as an openable file. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Budget 2.0
A personal budgeting PWA. Envelope-style monthly budgets with rollover, split purchases, finance plans, multi-currency, and JSON/ODS export. All data lives in your browser — there is no server and no account.
Development
bun install
bun run dev # dev server with hot reload, on :3000
bun test # run the test suite
bun run build # production build into dist/
Self-hosting with Docker
docker build -t budget2 .
docker run --rm -p 3000:3000 budget2
To serve from a subpath, build and run with BUN_PUBLIC_BASE_PATH:
docker build -t budget2 --build-arg BUN_PUBLIC_BASE_PATH=/budget/ .
docker run --rm -p 3000:3000 -e BUN_PUBLIC_BASE_PATH=/budget/ budget2
GitHub Pages
Pushing to main builds and deploys to Pages automatically, using
/<repository-name>/ as the base path. Enable Pages with "GitHub Actions" as
the source in the repository settings.
Your data
Everything is stored in this browser's IndexedDB. Export regularly from Settings → Your data: the JSON export is both your backup and how you move your budget to another device.
Both destructive actions there — Import, and "Reset everything" — download a backup of your current data before replacing it, and abort if that download fails. Reset puts the app back to a brand-new install: the three starter posts, the DKK/USD/EUR currency table, this month at zero income, no purchases.
Known limitations
- Data is per-browser. There is no account and no sync. If you clear this browser's site data, or move to a different browser or device, your budget is gone unless you exported it first. The JSON export is not just a nice-to-have backup — it is the only way to move a budget between devices.
- Installing and offline use are unverified. The manifest ships the SVG plus 192×192 and 512×512 PNG icons, and the service worker demonstrably installs, activates and precaches every asset — but nobody has yet confirmed that Chrome offers its "Install app" prompt, or loaded the app with the network actually cut. It works as a regular tab regardless.
Documentation
docs/ARCHITECTURE.md— layers, data flow, and why the non-obvious choices are what they are.docs/PRODUCT.md— who this is for and what must never break.AGENTS.md— the rules for changing this codebase, and the test that catches each one when broken.CLAUDE.mdandGEMINI.mdpoint at it.docs/DECISIONS.md— an index of the choices that shaped the app, and what each was chosen over.docs/TODO.md— what is still queued.docs/specs/— one design document per piece of work, each recording the alternatives that were rejected.docs/plans/— task-by-task implementation plans.