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

I built a band scraper to identify bands on Bandcamp, interact with them, and offer mixing and mastering services. A daily cron job runs an Apify Bandcamp scraper, stores the data, and supports a website hosted on Lightsail. Step-by-step: 1. I configured an Apify Bandcamp scraper to collect band data. 2. I scheduled the scraper to run daily with a cron job. 3. I stored the collected data. 4. I used the data to interact with bands and offer mixing and mastering services through a website hosted on Lightsail.

As a hobby/non-work-related creative outlet, I've started to write and create YouTube videos about retro football (soccer) stories. Part of the visuals are vintage stickers of the players mentioned. This used to be a time-intensive Google/eBay search when I was looking for 20+ players at a time. So I used Claude to build a local "Sticker Search" tool. It lets me enter the player, season, and team, find their sticker from that year, and download it to my working folder with one click. It's made my hobby way more fun and sped up the tiresome bit. P.S. I used Billy's guide on Manus to create the animated logo for the videos! Step-by-step: 1. I listed the inputs I needed for each search: player, team, and season. 2. I used Claude to build the local Sticker Search interface and search logic. 3. I added recent-search shortcuts so I could repeat or refine searches quickly. 4. I made each result downloadable with one click to my working folder. 5. I used Billy's Manus guide to create the animated logo for the videos.

I built Bubble Grotto, a skill-based arcade game for mobile devices, using AI as a development partner. The concept is deliberately simple: start with a small bubble, grow it, navigate through a cave filled with hazards, and decide when to escape. The larger the bubble becomes, the greater the potential reward—but the harder it becomes to manoeuvre safely. The aim was to create the classic “one more go” experience: controls that can be understood almost immediately, with gameplay that becomes progressively harder to master. The interesting challenge was that building a game is very different from implementing a list of features. The code can work perfectly and the game can still be no fun. Timing, movement, difficulty, visual feedback, and risk versus reward all have to feel right when somebody actually plays it. Step-by-step: 1. I used AI to discuss how the core concept should work, including bubble growth, movement, hazards, progression, scoring and rewards, and the escape mechanic. 2. Rather than designing the entire game upfront, I used AI-assisted development to turn each mechanic into working code and get it onto a real device as quickly as possible. 3. Once a mechanic existed, I tested it myself. I checked whether movement was responsive, whether the bubble grew too quickly, whether obstacles were fair, whether escaping was too easy, and whether failure made me want another attempt or simply became frustrating. 4. I brought those observations back into the AI workflow, identified the relevant behavior or code, made targeted changes, and tested again. 5. Once the core loop felt enjoyable, I refined the interface, visual feedback, progression, and presentation instead of allowing cosmetic work to hide weak gameplay. This produced a development loop of: idea → mechanic → playable build → play-test → adjust → repeat The final result is Bubble Grotto, an arcade game with simple controls but increasingly demanding skill-based gameplay. Players grow their bubble while navigating hazards and must balance risk against reward by choosing the right moment to escape. One of the most useful things I learned is that AI can dramatically accelerate game development, but it cannot replace judgment about whether something is enjoyable. AI can help create a mechanic, investigate why it behaves incorrectly, and implement changes extremely quickly. The human still has to play the game and decide: is this actually fun? That combination allowed me to move rapidly from a simple game idea to a functioning mobile game while spending far more of my time experimenting with gameplay than wrestling with implementation.

I created an online app where my friends can select the gigs they plan to attend. It shows who is going to each gig and when, along with a clear festival-wide timeline. The festival host only provides stage-based schedules, which are difficult to read and coordinate. My app brings the information together in a more practical format for planning with friends. Step-by-step: 1. I created an online app for coordinating festival plans. 2. I added a way for friends to select the gigs they plan to attend. 3. I organized the selections to show who is going to each gig and when. 4. I created a clear timeline that combines the festival’s stage-based schedules. 5. I used the combined timeline to make planning and coordination easier.