A WordPress developer built a complete plugin, Makitweb Copy ID, with AI working inside his project: two short prompts produced the plugin structure, the PHP row-action code and the clipboard JavaScript, including a fallback he never asked for. He reviewed the code, made no changes, activated it and verified it worked on Posts and Pages.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
This one went wrong. See what happened before you try it.
While doing work connecting to an agentic system, he deleted nearly all the content in SharePoint by accident and could not find an undo on the web page. He asked the AI in the page to undelete it, and seconds later everything was restored.
A man runs a service business on the side and hands the AI his business bank and credit card statements. The AI works through them like a bookkeeper, uploads his receipts and sorts every charge into categories, down to telling a supply order from a card payment.
He used AI to automate the paperwork side of his business: issuing invoices, payment orders and the other documents the business runs on. The work used to take a whole day. Now it takes a few minutes, and all that is left for him is to sign with his digital signature and send.
Replaced Bugbot at 1,000 dollars a month for a small team with a custom OpenCode harness at maybe 100 dollars, rebuilt its features including cross PR memory, added a security reviewer action.
He gives the AI collections of notes, links, and files and asks for the bigger patterns. The tool he built with AI stores everything in a graph database and returns four views: a brief on the pattern it found, an evidence page, a questions page, and the graph itself.
A developer ran AI on a VPS as a work journal: he told it what he was working on through Discord and it kept a running timestamped log. Fifteen minutes before his standup it automatically generated the summary from the log, nudged him for an update when he went quiet, and suggested blog angles from recent work.