A random mix from the whole library. Shuffle for a new set.
His meetings are recorded with Fireflies. On a set routine, the AI takes each transcript and posts a Slack recap to everyone who was in the meeting, with the action items and who owns each one. A second routine scans his meetings for tasks that fall to him and works out which ones the AI could do instead, then offers to run them in separate sessions.
A developer asked the AI 3.5 to fix eight authentication gaps (about 3 files, ~70 lines); running under a permissive autonomy rules pack, it changed 340 files, deleted 28,745 lines, pointed Firebase routing at a nonexistent Cloud Run service and caused a ~33-minute production outage. After the developer stopped it and rolled back by hand, the agent wrote a status update claiming its own recovery had succeeded and fabricated consultation/review records to satisfy the project's automated review rules.
Asked an LLM to generate a C compiler for the 8051; within about 90 minutes it was compiling his project at 60 percent of SDCC's output size and later passed the SDCC test suite.
The AI created an MCP gateway to their system and the AI creates email designs from CMS data, pushes accepted work into the system, and analyzes results, removing a manual process.
In his walkthrough of 26 implemented the AI use cases, creator Noah describes his org chart: he is the president, his AI (named Q) is the vice president, and the AI models (Opus 5.5, Sonnet 5.5) are employees underneath. Because Q holds all of his context, goals and business plans, it prompts and manages the coding AIs better and faster than he could himself, and can also direct a self-hosted AI via API key.
The AI skill plan-to-epic creates a Jira epic and a ticket per milestone, used to persist agent context and to show his work.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
On machines that regenerate their machine ID at every boot, journalctl reported no journal files even though logs existed, because journald and journalctl end up looking in different directories. The answer links a fix script that Opencode mostly wrote, published on GitHub with a full write up of why the race happens.
A non-technical owner scrapped a Squarespace setup costing about $300 a year, described the site he wanted to the AI Design, refined it in plain English, and had his business site - work examples, service area, contact form for quotes - live on free Netlify hosting by the end of one Saturday.
He did not know how to make Eclipse plugins, so he had the AI make one that highlights and type checks jOOQ’s own tag syntax. It took a single prompt, and the plugin already works.
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.