A random mix from the whole library. Shuffle for a new set.
A local model helped build a self-hosted services wiki and dataset in an Obsidian vault so his partner could keep systems running if he died, set up in a few hours.
Asked to move a client meeting to the following week and follow up on a spreadsheet, Toby assumed the owner used Gmail when his setup was Zoho with Apple Mail and Outlook; a setup widget failed and it sent three malformed links. Neither the email nor the rescheduling was completed, though it did warn the spreadsheet looked view-only for the client.
A church volunteer runs a weekly hybrid workflow: The AI translates six Chinese daily spiritual messages (Monday–Saturday) into structured JSON under strict rules — Bible quotations in NASB 2020 rather than translated, hymns left untranslated, ministry terminology matched — then Python inserts the text into a PowerPoint template, merges a bilingual twelve-message deck, and converts it to HTML for the church website. He keeps theological review, visual checks and final publishing approval human on purpose.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
He got the AI to build out a structured dataset of all 4,925 vacancies, with job titles, organisation, salary and location. He shared it in a spreadsheet for other people to play with.
Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
His claim was too small for a lawyer and the insurer had frozen it at $4,430, so he worked it himself with AI holding every letter in order. The agent surfaced six dated contradictions in the adjuster's own letters, including a legal basis for denial that changed three times, and reviewed each of his drafts as opposing counsel before anything was sent. After his letter quoting their own paper back at them, the offers climbed: $6,500, then $8,000, then $8,750, and the insurer accepted his split of the last gap the same morning, at $10,250.
A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.