Remixed from Tidepool

Tidepool Duo

A fork of Tidepool for couples who share some money, not all of it

Mateo RuizLaunched 5 days agoWeb app
0:42

About

Forked from Tidepool. Adds a shared space for two people: split categories, who-owes-who that settles itself, and a monthly summary you'll both want to read.

How it was made

Shared by the maker. Numbers are their own estimate.

Build time
1 weekend
AI spend
$11
Prompts
~40
Written by AI
95%

Agents

  • Claude Code

    100% of the work

    Shared spaces and settlement logic

MCP servers1

  • Supabase

    New tables for shared spaces

Build recipe

The code is on GitHub. If you’d rather build it yourself than fork it, paste this into your own agent.

Written by Claude Code

From the project’s code and history · 359 words

Build a web app called Tidepool Duo: a fork of Tidepool for couples who share some money, not all of it.

What it does

Forked from Tidepool. Adds a shared space for two people: split categories, who-owes-who that settles itself, and a monthly summary you'll both want to read.

Stack

Use Next.js, Supabase, Tailwind. The original was built with Claude Code in 1 weekend, for about $11 in AI usage.

How it fits together

  • A server-rendered web app with a small API layer
  • A database for user data, with row level security on every table
  • Sign-in so each person only sees their own data

Build it in this order

  1. Set up the project, the database and sign-in, and deploy an empty page
  2. Build the main screen with realistic sample data
  3. Connect it to real data and add the one action the app exists for
  4. Add the empty states and error messages a new user will hit
  5. Write tests for anything that touches money, dates or other people's data

Tools to connect

  • Supabase MCP: new tables for shared spaces

A prompt that worked: Extend a fork without breaking upstream

This is a fork of Tidepool. Add shared spaces for two users without changing any existing table or component. Put everything new under features/shared/. Keep the upstream parsers untouched so I can still merge their updates. List every file you changed outside features/shared/ and why.

Watch out for

  • Don't build settings, teams or billing before the main screen works
  • Keep the first screen useful with sample data, so the app makes sense before anyone has set it up

Done when

  • A new user can sign in and get value in under two minutes
  • Everything works on a phone
  • Tests pass for the core logic

Before writing code, ask me up to five questions about who this finance web app is for and what the first version must do. Then work in small steps: after each one, tell me how to try it and wait for my feedback.

Discussion

4 comments · 1 built their own

  • Priya RamanBuilt one3 hours ago

    Built my own version from the recipe in an evening. The build log is the most useful part for me, I'd love more detail on how you structured week two.

    • Mateo RuizMaker2 hours ago

      Thanks! Good question, I'll write it up in the build log this week.

  • Lena Vogt6 hours ago

    Love how focused this is. One thing: the empty state took me a second to understand. Maybe show an example right away?

  • Kenji Mori1 day ago

    What did the agent struggle with most? Always curious where people had to step in.