How to use Cursor to build a poker tracking app
Chase reports a fully functional Laravel poker tracking application after two or three days of Cursor conversations, including a dashboard, statistics, imports and hand viewing.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a Laravel poker tracking app for [hand-history format]. Add an admin dashboard, hand imports, [required statistics], journal entries and a profit/loss chart. Help me run it locally with [environment] and deploy it to [server]. Ask me about missing format details.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- reillychase
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Chase reports a fully functional Laravel poker tracking application after two or three days of Cursor conversations, including a dashboard, statistics, imports and hand viewing.
- Human involvement
- The source does not describe formal review steps for the generated code.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Developed a Laravel poker tracking MVP through conversations with Cursor.
- Built the application locally using Herd for macOS.
- Deployed with Cursor assistance to a DigitalOcean Debian 13 server.
Reilly Chase describes turning personal poker tracking into a Laravel web application with Cursor. After playing and reviewing hands with PokerTracker 4, he began writing Python automations for hand exports, imports and balance checks. Help from Grok preceded his move to Cursor for a larger application.
In the earlier scripting work, Chase asked Grok to add a Gmail integration that retrieved a login PIN. He then had it replace print debugging with logging and refactor the monolithic script into a reusable class. He subsequently spent two or three days in extended conversations with the Cursor agent, building a Laravel MVP without writing any of its code himself.
The reported application included an admin dashboard, a PokerStars hand-history parser, poker statistics, journal entries, deposit and withdrawal records, file uploads and a profit/loss chart. It also supported daily balance checks, scheduled hand exports and email imports through Gmail IMAP. Chase built locally with Herd for macOS and deployed with Cursor’s help to a DigitalOcean Debian 13 server, keeping the repository private on GitHub.
Who it's for: Hobbyist developers who understand their tracking requirements and want to direct an agent through building a personal data application.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · reillychase
Frequently asked questions
What poker information did the app track?
The reported features included hand histories, VPIP, PFR and 3-Bet statistics, journal entries, deposits and withdrawals, and a profit/loss chart.
Where was the application developed and deployed?
Chase built it locally with Herd for macOS and deployed it with Cursor’s help to a DigitalOcean Debian 13 server. The code was in a private GitHub repository.
More details
About this account
The agent generated code from the author’s instructions, with the author directing the work.
Platform: Blog. Attribution: https://blog.rchase.com/i-played-1-000-hands-of-online-poker-and-built-a-web-app-with-cursor-ai/. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: reillychase on Blog
Source published
Added to Agents In Use
Source checked
Tools and topics
Cursor · Laravel · Herd · DigitalOcean · Gmail IMAP
AI coding
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.