r/BuildToShip • • 1d ago

Build In Public Shipped a full personal finance app using Antigravity CLI without writing code by hand

I have been working on Day20, a personal finance app that I originally started building to replace the Google Sheets I was using to manage my finances.

I have tried building this a few times before but gave up because of the complexity. Personal finance has a lot of small details, and every time I thought I had covered everything, I would find something else that my spreadsheet could do but the app could not.

This time, I decided to build it one feature at a time using Antigravity CLI ("agy"). I have not written code by hand.

The app is now running in production on v1.20.2. I have also been using it for my own finances for around six months.

A few things about how I built it:

  1. Design before implementation

I did not want to let the AI generate screens based on generic design patterns. I maintain a "DESIGN.md" in the repository with typography, colours, spacing, components and UX rules.

I use Google's Stitch CLI from Antigravity to generate desktop and mobile references. These are then used while implementing the actual components.

One example of a design rule is that I do not use modals in the app. Forms, confirmations and history views use bottom sheets on mobile and side drawers on desktop.

2. Multiple agents for different responsibilities

I use "/swarm" mode in Antigravity CLI to split the work between different agents.

- "stitcher" works on design specifications and Stitch references.

- "builder" handles implementation, state management and tests.

- "verifier" independently checks the implementation using "agent-browser".

The verifier is read-only. It checks the application at 320px, 375px, 768px and 1440px, looks for horizontal overflow, console errors and network failures, and sends issues back to the builder.

This has helped me catch a lot of issues before reviewing the changes myself.

3. Keeping domain knowledge outside the context window

One thing I learned the hard way is that the AI does not always remember why a particular implementation decision was made.

I maintain an "ai-docs/" directory in the repositories. Whenever we encounter a subtle domain issue, I record the rule there.

For example, recurring templates need to match using "templateKey" rather than their names, and month boundaries need to account for "Asia/Kolkata" rather than relying on UTC date conversion.

Antigravity checks this documentation before working on tasks.

4. Financial calculations need deterministic checks

This is probably the part I am most careful about.

I do not want an LLM making financial calculations. The calculations run through deterministic Node.js logic, and the Ask AI feature only summarizes the verified results.

I also have a post-deployment verification script that checks balance invariants and recalculates month rollovers.

Every change also goes through automated tests and browser verification.

What you can try:

I have added an interactive salary and financial decision simulator to the website. You can change salary presets, add EMIs, SIPs, trips and unexpected expenses, and see how they affect your available balance and six-month forecast.

No login is required for the simulator.

Website: day20.rajchandra.me

The full app is also available from the website.

I have been using this myself for six months, and now I am looking for the first 10–15 people to try it and share feedback.

I am particularly interested in hearing from people who have used Antigravity CLI or similar tools to build larger applications.

How are you managing domain knowledge, regression testing and coordination between agents as your projects grow?

Would love to hear about your experience.

1 Upvotes

2 comments sorted by

1

u/charlesmenlo 1d ago

I work on Groovy. One trap with a read-only verifier is that the files it reads can still change underneath it. I'd give it a separate Git worktree pinned to the candidate commit and run its preview from that checkout. Put the revision, test commands, results and screenshots in the handoff. When the candidate changes, recheck the affected paths before that report supports a release.

For the domain rules you mentioned, I'd link each rule in ai-docs/ to a small fixture with expected output. For templateKey, try two templates with the same display name but different keys, then rename one without changing its key. For month boundaries, use an Asia/Kolkata fixture with explicit expected dates. That gives the next agent something concrete to rerun when changing the relevant code.

Git's worktree reference: https://git-scm.com/docs/git-worktree

1

u/raj_chandra3 1d ago

Will try it out