ildigi

Personal Finance Dashboard — Development skill for Claude Code

Development community

Self-hosted personal finance dashboard: Open Banking (PSD2) + Trading 212, read-only, with a one-command demo.

How to install Personal Finance Dashboard

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ildigi/personal-finance-dashboard and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Personal Finance Dashboard does

Self-hosted personal finance dashboard: Open Banking (PSD2) + Trading 212, read-only, with a one-command demo. FastAPI, PostgreSQL, React. Built with Claude Code.

Alternatives in Development

  • Financial Services Plugins — Plugins that turn Claude into a specialist for financial services — investment banking, equity research, priva 7.7k ★
  • Microsandbox — Open-source self-hosted MicroVM sandboxes with sub-200ms startup, hardware-level isolation via libkrun 5k ★
  • Vibe Research — Vibe-Research: Your Personal Trading Research Agent · A股/美股/港股 的个人投研 Agent:每日复盘、资讯雷达、个股数据、板块中心、我的持仓、研究记录、回测 2.5k ★

README

Finance Dashboard

A self-hosted personal finance dashboard that brings bank accounts, cards and a brokerage portfolio together in one place: where the money goes, how much comes in, how the investments are really performing and what the total net worth is, day by day.

It connects to real banks through **Open Banking (PSD2)** and to **Trading 212** through its official API, always **read-only**. It ships with a **demo mode** that generates 15+ months of realistic fake data, so anyone can run it in a couple of minutes without any credentials.

The user interface is in Italian (it was built for an Italian user and Italian banks). The design document ([docs/SPEC.md](docs/SPEC.md)) and the code comments are in Italian too.

![Overview](docs/screenshots/overview.png)

Built with Claude Code

This project was developed with [Claude Code](https://claude.com/claude-code), Anthropic's agentic coding tool, under my direction. I defined the requirements and the 17-section specification, split the work into 11 phases (0–10), made the product and architecture decisions, reviewed every phase against real data and approved it before moving on. Claude Code wrote the code, the tests and the documentation following that plan.

The phase-by-phase history (decisions, trade-offs and implementation notes) is preserved in [docs/SPEC.md](docs/SPEC.md) and in the [architecture decision records](docs/decisions/).

Features

  • Unified transactions from every account and card: search, filters, inline editing, bulk actions, manual entries, pending → booked promotion without duplicates.
  • Automatic classification with a deterministic pipeline: manual overrides → internal transfers → user rules → system rules → merchant defaults → MCC / provider category. Corrections can become rules ("apply to past and future transactions from this merchant"), and every transaction explains why it got its category.
  • Internal transfer detection: money moved between your own acc