The Perfect Trade: A Trading Journal Its Users Can Rely On

Swing Trading Lab built The Perfect Trade, a trading journal, in Bolt.new, then synced it to GitHub, deployed it on Vercel and connected Supabase for accounts and data. The app was live and working. A journal is only worth keeping if traders trust it with every entry, and three problems were wearing that trust down: trades that would not save, a password reset that led nowhere, and reference images that never loaded. The team wanted two things, in their CTO's words: to "understand how this works" and to "solve the actual 3 main problems we have". We did both in one week.

Built your app in Bolt, Lovable or a tool like them, and now real people depend on it? I make it dependable and teach your team a workflow that keeps it that way. Book a call at cal.com/andres-sepulveda-morales or email andres@redmage.cc.

A journal that drops an entry stops being a journal. Saving a trade failed with a foreign key error on the trades table, the link between a trade and the account it belongs to. I traced it in Supabase and fixed it, and trades saved again.

The reset email took people back to the dashboard, because the app had no page to set a new password. We added the route and the page. One attempt from the builder broke login along the way, so I showed the team how to roll back to the last working version in Bolt, which is worth knowing on its own. The last piece was on Vercel: it did not know the app's routes, so the new page returned a 404. A small vercel.json rewrite fixed it, and a trader who forgets a password can now set a new one.

The app shows traders example setups to check their trades against, such as an EMA, a head and shoulders, a previous structure. Those images came up blank. The builder had saved them as small text files, each holding a link, and some links pointed at temporary addresses from the builder's preview. I pointed the app at the real image files and added a loading state, so a slow image shows a spinner instead of a gap.

Reliability has to outlast the week I was there. Every fix went through the process I was teaching, so the team could run it themselves:

Notes in the repo. The audit went into a documentation folder in the code itself, where the next person will look.

Branches and pull requests. Each fix lived on its own branch and arrived as a pull request. I walked the team through the branch, review and merge steps over chat with screenshots, and the CTO merged the pull requests himself.

The Golden Path. A recorded walkthrough of how to make changes in Bolt without GitHub falling out of sync.

A picture of branching. To make branches less abstract, I built a small Git branch visualizer in Bolt.

Tests next. A plan for unit tests with Vitest, run on GitHub so a failing test blocks a merge into the main branch.

Are your users starting to work around your app instead of with it? Send me what's breaking. I'll find the cause, fix it and leave your team a way to ship the next change safely. Book a call at cal.com/andres-sepulveda-morales or email andres@redmage.cc.