A random mix from the whole library. Shuffle for a new set.
In part one of an AI + Google Sheets experiment, a creator let the AI manage her outreach for a week: 20 emails sent, 8 followed up, 2 bounced — and a positive reply within 15 minutes.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
A self-described desperate vibe coder commented in an Reddit showcase thread that the SaaS he built with AI, which auto-generates landing pages and tracks who will pay, made $16k in 3 days with 876 paying users. It spread via Reddit and Twitter and got noticed in a hackathon Discord.
Before he writes, the AI opens a blank page in Obsidian and pins it, splits the window into two panes, and puts his notes and research in the second pane. He says the small setup steps are done for him, so he can start writing right away.
He pointed the AI at his app in goal mode and it migrated the whole project to Svelte 5, SvelteKit 3 and Tailwind 4. The run took 15 days, 229 commits and 3,523 file changes. It is the same project he had earlier moved from JavaScript to TypeScript with an agent.
The AI helps him put GA4 and Microsoft Clarity tags live, with reviews and confirmations built in so he can check the event triggers fire. Cross checking the two tools showed bots being lumped into direct traffic.
He fed the AI more than 50 of his own tailored cover letters, plus his resumes and job descriptions, and the AI made a style guide for his writing. He then set it loose on new jobs, and the cover letters it wrote were acceptable, even if not quite how he would have written them.
A reviewer uses AI as producers for his projects, with the bots managing multiple Cursor Cloud Agents doing the underlying work.
Domain experts use agents via MCP to provision real environments, e.g. a 200Gi PostgreSQL with PostGIS plus a copy of a Texas layer set, a big productivity boost over provisioning web interfaces.
A solo developer built a women's clothing brand's production WooCommerce store with AI writing most of the code: a custom block theme matched to the client's React prototype, real-time CommerceML sync with their 1C ERP (including patching a stock parser that silently dropped nested per-warehouse counts and cleaning up roughly 1,000 orphaned variations), and zero dollars in platform licenses. Two client revision rounds of about thirty items each cleared in days, and the whole build took weeks instead of months.
Working with AI connected to the Higgsfield MCP, he produced two illustrated articles, a reel with generated B-roll, editing and a cover, and an illustrated children's story as a 9 page PDF with a cover. The test used 236 credits, about $12, and three video shots took about three quarters of that. He also shows the connection mistake he made at the start.
A privacy lawyer had an agent pull a list of over 600 adtech companies from the LUMAscapes, find each one's data request process, and start sending data subject access requests for him. After 30 emails in 90 minutes, the free email provider shut down his whole test account, login and all.
Ported a legacy .NET WebForms app to Blazor with GPT-5.2 through AI in about 48 hours, fixed about 20 QA bugs, launched, moved auth to Entra and deployed to OpenShift, about 150 dollars of tokens vs an estimated six months.
For a cleaning business, the AI manages contacts, drafts client messages, chases reviews and maintains the CRM, holding every outbound message for approval before it sends.
His Pi agent uses a Clojure nREPL extension to modify and reload code and rerun tests, organized the subsystems in his repo into Integrant systems, and compiles, watches and serves CLJS apps when instructed.
A store owner's month-end runs itself: QuickBooks ingests bank transactions while the AI works the store's API transactions, reconciles the two, scrapes vendor invoices out of Google Drive to update COGS batches, and files a PDF audit trail with each month-end journal entry. Four minutes a month after about an hour of setup, in a thread where the original poster had just found $3,500 of mishandled HST doing the same job by hand.
Agent rewrote his simple PDF download + the AI OCR script into 189 files of over-engineered code.
A swarm of AI agents ran 4,654 searches to catalogue AI product names and trends, published as a public page.
A team ran an AI pipeline over a usability test of an investment app and saved about half a day of manual analysis. Every claim the AI made about the screen was checked against a video frame, and two claims that did not hold up were left out of the report.
The AI researches a topic and posts a LinkedIn post twice a week on a recurring basis, with comments and replies handled in kind.
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.