Lucas WintherandClaude Opus 5
acb4d97870
Three defects in the purchase list, plus NativeSelect for the rule-kind picker. Alignment: `px-1` on the row indented every description 4px past its own date heading, so the list had two left edges 4px apart. `-mx-2 px-2` puts the text exactly under the heading and bleeds the hover wash outward, so the highlight has an inset instead of stopping flush against the first character. The hover-action reservation: a fixed `w-[7.5rem]` kept the amounts from shifting when edit/delete appeared, which is right on a desktop. On a phone it was doubly wrong — there is no hover, so `opacity-0` made these the hardest controls in the app to reach, and the reservation still spent 120px of a 350px row hiding them, truncating descriptions to "Weeken…", then "Bik…", and the financed row to nothing but its badge. So the row is one line from `sm:` up and two below it: description on its own line, amount and actions on the next. `sm:contents` dissolves the wrapper above `sm:`, so the desktop row is the same flat flex line it always was. This is the call PostTable already makes at that width, for the same reason. Also: the month steps wrapped mid-label into "← 2026-" / "08" on a phone, and the error alert's "dismiss" was an unpadded underlined word. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.