Share your best AI workflow. We could show it to 2M+ people.

I love playing poker, both online and live. One month, I performed poorly. Although it felt like the cards were running badly, I wondered whether I had developed a problem in my game and was blaming my losses on bad luck. I asked around, including asking AI, whether a tool existed that could measure luck from poker hand histories. The unwelcome answer was that it did not. I'm not a coder, but after doing some research into vibe coding, I started building a luck-detection app in a Claude chat. Claude built the UI directly in the chat window and advised me on the formulas I was using to calculate luck for the cards dealt, my performance on the flop, and my performance when I went all in. All three metrics have strong averages, and luck is what varies them. I used a bell curve to model hand outcomes and a Monte Carlo simulator, which Claude suggested and executed, to evaluate all possible outcomes. The result astonished me because it was so useful. I immediately fixed two major leaks in my game and felt better knowing that bad luck really was the main problem affecting my results. I liked the tool so much that I decided to turn it into a full web app with Claude Code, and now an iPhone app that I may let other people use for free. I also had a lot of fun building it—except for learning how to use Xcode. That was a pain, even with step-by-step guidance from Claude. Step-by-step: 1. I reviewed a month of poor poker results and questioned whether bad luck or problems in my game were causing the losses. 2. I researched whether a tool existed that could measure luck from poker hand histories and learned that I would need to build one myself. 3. I used vibe coding to start building a luck-detection app in a Claude chat. 4. I had Claude create the UI and advise on formulas for evaluating cards dealt, flop performance, and all-in performance. 5. I used a bell curve to model hand outcomes and a Monte Carlo simulator to evaluate possible outcomes. 6. I used the results to identify and fix two major leaks in my game and confirm that bad luck was also affecting my results. 7. I expanded the project into a full web app with Claude Code and then began building an iPhone app, working through the added challenge of learning Xcode.

I used /goal in OpenAI's Codex to build a Magic: The Gathering app so my brother and I can play asynchronously without needing to coordinate a call or awkwardly play over FaceTime. The idea is to let each of us take turns when we have time, track the board state cleanly, and keep a game going over days instead of trying to line up schedules. The command allowed Codex to continue running until everything was done, basically one-shotting exactly what I was looking for without any intervention. Step-by-step: 1. I defined the core problem: two people needed to play asynchronously without coordinating a call. 2. I described the app’s essential behavior, including turn-taking, persistent board state, and games that continue over multiple days. 3. I used /goal in Codex so the build could continue autonomously toward the finished result. 4. I let Codex implement the app and resolve the work without requiring step-by-step intervention. 5. I tested the finished flow to make sure each player could return later and continue from the correct state.