A random mix from the whole library. Shuffle for a new set.
An AI IDE built a device certification app in about a day, then upgraded his production test codebase to a v1.0-ready state with automated configs, error handling and simulators over two weeks.
Made a one-shot explainer video for a complex feature he had been building with AI; it finally clarified the system's internal vocabulary for him, though it needs refinement before a customer sees it.
A Korean creator set up the AI to find possible clients on its own. Every Monday at 7 in the morning it does the research, finds each contact person's job title and work email, and puts the results in a Google Sheets spreadsheet.
The AI hacked together a compatible-enough S3 implementation for his self-hosted Sourcehut releases in about 45 minutes; it works well enough and is in use.
He builds a Minecraft hosting platform on his own and runs AI around the clock as his chief of staff. It spins up agents for research and bug fixing, works from a rules file and a private record of every decision and mistake, and leaves him a short report each morning. Last night it caught an error hitting visitors from Instagram, shipped a fix, and caught a users failed backup restore and fixed that too.
He runs Svippit, a small shop platform for creators. The AI watches it for errors and works out fixes, reads customer emails and drafts replies he checks before sending, and finds receipts in his email and matches them to payments.
A builder used AI in Google AI Studio and DeepSeek to build a 19 project .NET system over about 4 and a half hours. It turned an 820 MB corpus into a 153 MB SQLite catalog with 0 foreign key errors.
An engineer at Sumasate writes that his team connected the AI Tag to GitHub, Sentry, their database, log tools and Notion, and let it do the first look at every alert in Slack. After three months, fixes finished inside alert handling went from about 2 of 38 alerts a month (5.3 percent) to about 7 of 44 (15.9 percent).
He now uses AI for design work and for putting print plans together. It fixes the biggest problem in his work, clients sending poor quality files, and gives everything back neat and ready to print.
Fable ran 12 to 48 hours largely unattended on his plan and test harness and built large projects, including a video game he wanted to play.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.