Apps, sites and tools people actually built, mostly solo with an AI agent, pulled from Reddit, Hacker News and elsewhere. Filtered to things you could build with what you already pay for.
9 Oct 2026
A darkroom timer made from an iPhone and a £20 smart plug
What it is
A darkroom printing timer that lives on your phone. Your enlarger plugs into a cheap Wi-Fi smart plug, and the phone switches it on and off to the second.
Why it is useful
Proper f-stop darkroom timers cost $300 or more. This does the same job, plus test strips, dodge and burn plans and split-grade printing, for under $50 including the plug. The builder measured it with slow-motion video and got 0.1 second accuracy, which is plenty when most prints need 4 to 60 seconds.
What it looks like
A black screen with dim red buttons, tested so it won't fog photo paper. You type in the plug's address once, then tap to expose. For a test strip it walks you through each step and clicks the light on for each band. Dodging and burning is laid out as a grid, so you plan which bits get extra light before you start, then the app runs the sequence for you.
How it was made
A film photographer printing in a bathroom darkroom realised the phone could already do the timing, it just needed a switch. They picked Shelly plugs because they have good documentation and accept plain commands over your home Wi-Fi, so there's no hub or cloud in the way. In their words it was "blindly vibe coded using Codex and Xcode" (Xcode being Apple's app-building program). It's free to use, with a one-off unlock of about $25 for the advanced tools.
What it would take you
The general trick is the one to steal: a £20 Shelly plug (the UK Gen2 model works) turns any mains gadget into something your phone can time or trigger, so it suits anything from a fan to a lamp in the studio. Claude Code can rebuild it as a small web page that runs on your Mac on the same Wi-Fi, which skips the App Store entirely. Shelly plugs can also be told to switch themselves off after a set number of seconds, which keeps the timing tight. An evening, plus the plug.
Turn any screen into a sign, where the web address is the whole app
What it is
A website that shows one message as big as the screen allows. You type the message, pick colours and an animation, and everything is stored in the link itself.
Why it is useful
Any old tablet, TV browser or spare laptop becomes a sign without installing anything. Share the link and you've shared the display. There's no account, no database and nothing to pay for, because there is nothing on a server to store.
What it looks like
You open the editor, type "Bar closes at 11", pick a black background with white text and a gentle pulse. The preview updates as you type. Copy the link, open it on the tablet by the door, and the words fill the screen edge to edge. It also does slides, countdowns and a QR code that can join people to the Wi-Fi, ring a number or open a map.
How it was made
The builder wanted to put a message on a tablet they could control remotely but couldn't touch. The fix: put the message after the # in the web address (the fragment). Browsers never send that part to the server, so one plain static page can show every possible message and never sees any of them. It's hosted on Cloudflare and caches well. After the Hacker News thread they added the ability to install it like an app so it works offline, and fixed bugs that only showed in Firefox.
What it would take you
One HTML file on Cloudflare Pages, free, an evening with Claude Code. It's an obvious one for Padharo events and the hospitality clients: a welcome screen, a Wi-Fi password QR or a countdown to the first dance, sent as a link the venue can open on any screen. The fragment trick also works for anything shareable that shouldn't touch a server.
A weather app that only speaks up when tonight is actually clear
What it is
A small Mac app in the menu bar for stargazers. It reads the forecast every half hour and sends exactly one alert, an hour before sunset, if there's a long enough clear spell to photograph in.
Why it is useful
It removes the nightly chore of reading cloud charts only to learn it's cloudy again. Silence means "don't bother". The builder lives on the edge of the Yorkshire Dales, where clear nights are rare enough to miss.
What it looks like
Most evenings, nothing happens. On a good one, a notification arrives before sunset with tonight's plan: which objects are up during the clear window, in order, with camera settings for each. A week view shows the next ten nights so you can pick the best. You can photograph your back garden with your phone so it knows which bits of sky the trees and houses block, and it'll suggest darker car parks nearby with a map.
How it was made
The forecast comes from two free weather services, 7Timer and Open-Meteo, which need no sign-up. The clever bit is the rule rather than the data: alert only when every hour of the dark window is clear, and stay quiet otherwise, so you trust it when it does go off. It's a native Mac app and the code is free on GitHub. The builder kept adding features from the thread's suggestions within a day, including aurora alerts and the nearest clear sky.
What it would take you
The same idea fits a photographer's diary far better than a stargazer's. A Cloudflare Worker that runs on a timer, looks at your outdoor shoots in Google Calendar, checks Open-Meteo for cloud, rain and wind at each location, and pushes to your phone only when something looks wrong the day before. Free, an evening. Open-Meteo's free tier is meant for non-commercial use, so check the terms if it ever becomes a client-facing feature.
Rembrandt, a free Lightroom replacement where you can type the edit you want
What it is
A free, open-source photo editor and library for Mac, Windows and Linux, built to do the everyday Lightroom jobs: RAW development, masks, healing, presets, batch editing.
Why it is useful
It costs nothing and doesn't lock you in. Edits are saved in the standard side-files (XMP) that Lightroom also reads, your originals are never touched, and it imports a Lightroom Classic catalogue with its edits, keywords and collections, then reports anything it couldn't bring over.
What it looks like
You press Cmd K and type "golden hour, shadows +25" or "paste the edits from the previous photo", and the sliders move on their own while you watch. You can also drag up or down directly on a part of the picture to lighten that tone. AI masks pick out the subject or the background, and denoise and 2x or 4x enlargements run quietly in the background, pausing while you work.
How it was made
The typed instructions aren't an AI chatbot. They're a fixed vocabulary of phrases mapped to slider moves, running on your own computer, which is why it's instant and free. The editing engine runs on the graphics card using the same tech as web pages, wrapped in a small desktop app (Tauri), and RAW files are read by a well-known open-source decoder. The builder modelled the colour maths on darktable, a more powerful but much harder free editor, because darktable's learning curve kept defeating them. There's also a mode that serves it from the computer holding your photos so you can edit from any browser on the house Wi-Fi.
What it would take you
Free to try today on a copy of one shoot. Still missing: print, book and web modules, face recognition and tethered shooting, and the downloads aren't signed yet, so macOS will ask you to approve it. The phrases-to-sliders trick is worth stealing on its own for any tool you build: it feels like AI and costs nothing per use.
Search every photo and every second of video on your Mac by describing it
What it is
A free Mac app that indexes your photo and video folders so you can type "dog on a beach at sunset" and land on the right picture, or the exact moment in a video.
Why it is useful
It finds things by what's in them, not by filename. It also reads any text visible in images, and searches the words people actually say in your videos. Nothing leaves your machine.
What it looks like
A search bar and a grid. Type a description and the matching photos appear, each with a little badge saying why it matched. Switch to Scenes and the results are video stills with a timecode; click one and the video opens at that second. A Dialogue mode finds an exact spoken line. You can pin a search as its own tab, like "screenshots" or "anything with an email address in it".
How it was made
It uses small open AI models that run on your own computer: one that understands what's in a picture, one (Whisper) that transcribes speech, and an OCR tool that reads text in images. They download once (about 435 MB) and then work offline. The builder is an iOS developer who wrote it all in JavaScript so it would be easy to move to other computers later. A commenter who built something similar gave the main warning: how often you sample video frames decides everything, and one frame a second across 12,000 videos takes days.
What it would take you
Free, installs with Homebrew. Point it at one finished shoot on the external drive first and see how long it takes before giving it the whole archive. A good way to find "that venue shot from two summers ago" without remembering which folder it's in.
An old LG TV's Plex app took 30 seconds to open, so its owner rebuilt it with Claude
What it is
A replacement Plex app for LG televisions, open source and free. On the builder's 2019 TV the profile screen now opens in about 3 seconds instead of 30, and scrolling runs smoothly at 60 frames a second.
Why it is useful
It brings an old TV back to life without buying a streaming stick, and it plays 4K, Dolby Vision and Atmos directly on the TV's own video chip.
What it looks like
The familiar Plex layout, a big banner of what you're halfway through and shelves underneath, but it keeps up with the remote. You sign in by scanning a QR code on the TV with your phone, pick your profile, and press play.
How it was made
The builder worked out why the official app was slow: it's really a web page running inside the TV's built-in browser, so no amount of tweaking could fix it. So they threw the browser away and drew the interface straight onto the TV's graphics chip. To learn how LG's own apps talk to the video hardware, they used Claude Code alongside Ghidra, a free tool that turns a finished program back into something readable. It started in C and moved mostly to Rust. It installs without hacking the TV, through LG's developer mode.
What it would take you
Claude Code plus free tools, but this is weeks of evenings, not one. The bit to steal is the diagnosis: when an official app on kit you own is slow, ask what it's really running on before trying to speed it up.
AI models painting in oils, one brushstroke program at a time
What it is
An online gallery and live studio where AI models paint pictures on a simulated canvas, mostly in the style of the German painter Caspar David Friedrich, without ever seeing one of his paintings.
Why it is useful
As a toy it's lovely. As a lesson it's sharper: it shows what these models reach for when left alone. Asked only to plan a painting, Claude Opus chose a jug with lemons six times out of six, and 31 of 65 titled paintings are set at evening, dusk, twilight or sunset.
What it looks like
A wall of finished paintings, each with the model's own note about it. A live page lets you watch a painter at work: it lays down a passage, steps back to look at the canvas, writes in its journal, then carries on.
How it was made
There's no image generator involved. Each model paints by writing code against a simulation of oil paint on linen, with bristle brushes, wet paint, drying time and glazes. Most of the 75 paintings were made at a virtual easel, a section at a time with a look in between, rather than in one go. In some rounds painters worked in a chain, each leaving written notes for the next but never their picture. The builder, Alice, runs it in numbered rounds and writes up what each change did.
What it would take you
Runs on Claude Code using your Max plan; comparing several rival models would need their own paid API keys. The method is the steal: give a model a tool, let it make a bit, look at the result, then carry on. That loop is the same one that makes AI-built web pages better.
A whole art history museum you can walk around in a browser, built from Wikipedia
What it is
A 3D museum in a web page, with a room for each period from Chinese painting through the Renaissance, Impressionism and Ukiyo-e to Pop Art, hung with real works.
Why it is useful
Wandering beats scrolling. You get a sense of how one period runs into the next that a list of images never gives.
What it looks like
You start in a hall with doorways labelled by movement and date. Walk through one with the arrow keys and the walls are hung with that era's paintings, each with its label. An Explore button lets you search for a particular artist.
How it was made
A Greek developer started it as a single prompt to an AI model, then spent a long time reworking it. The paintings and their details come straight from Wikipedia's free image library, which is why some are low resolution. Commenters suggested better art databases and an audio guide, and the builder is working through the list.
What it would take you
Free, a weekend, Cloudflare Pages. The obvious version for you is a walkable portfolio: one room per kind of shoot, your own photos on the walls, a link a client can wander round. Building the 3D room is the easy part for Claude Code now; choosing and grading the pictures is the real work.
How one founder got an AI-built website to look like a designer made it
What it is
A ten-minute write-up of how Yakko Majuri, who says they aren't a designer, built the Railcode homepage with Claude Fable and then kept getting asked which designer they'd hired. The site is a sky-blue amusement park with a rollercoaster along the bottom of the hero, nothing like the usual dark purple AI landing page.
Why it is useful
It's the problem you fight on every client site, written down as a process you can copy. They saved every prototype next to the prompt that made it, so you can follow the whole route from slop to finished page. The thread is worth a look too: several designers point out that this is simply the design process, and one says the glass panels still give it away.
What it looks like
The post is mostly short videos of each stage. Four ASCII and neon rollercoasters, a playable Rollercoaster Tycoon mini game that got binned, a thin strip of park rides added under the hero, then side-by-side copies of the same page with one or two things changed. One screenshot is a "playground" page with live controls for the grass, accent and background colours, which is how the green got picked.
How it was made
Four habits. Ask the agent for at least four versions of any idea, guide half of them and tell it to "go wild" on the rest, and ask for the idea on a scale from minimal to outlandish. Keep the whole site in one HTML file until the look is settled, because one file is quick to copy, tweak and compare, and only then split it into components. Never delete a copy. And for anything fiddly (colours, fonts, positions) have Claude build a little control page with sliders instead of asking for change after change. They also say they only use Anthropic models for design, because GPT models "really struggle even with specific directions".
What it would take you
Nothing new, just Claude Code on Max. The playground idea slots straight into your preview editor workflow. Free.
Pixel-art city windows at night, with lofi music made live in your browser
What it is
A website showing a night-time view over one of 25 cities (Paris, Tokyo, London, Cape Town and so on) in pixel art, with rain on the glass and an endless lofi soundtrack. Think of a YouTube "lofi beats to study to" stream that you can steer.
Why it is useful
It's a one-person passion project that pays its way several ways at once: billboards in the scenes you can buy, a job board, a Gumroad pack of the video loops and a Buy Me a Coffee link. Most of the top comments are people asking for their own city.
What it looks like
You land on Paris at the real local time, rain on an attic window. A side panel lets you pick a city from a globe or a grid, change the weather (drizzle, thunderstorm, snow, falling leaves), turn on a city tour that hops every 5 to 30 minutes or follows whichever city is nearest 1am, and set focus and sleep timers. A "passport" counts the cities you've visited.
How it was made
The builder, Safa Elmali, makes each city ahead of time: AI draws the pixel-art scene and a short animated loop of it. The music isn't a recording. It's generated in your browser by the Web Audio API (the browser's own sound engine), so it never repeats and costs nothing to stream. The weather is a separate layer, which is why, as the builder admits, you can have autumn leaves outside a Paris window.
What it would take you
darkroom for the scenes (free tier), your Kling credits for the loops, the site on Cloudflare Pages. A weekend for a handful of cities. The angle for you: the same trick for a client, say the view from Banana Wharf, changing with the real weather and time of day.
A working Enigma machine you can take apart in your browser, built with GPT Astra
What it is
An interactive 3D lesson on the Second World War cipher machine. You type on it, watch the current run through the wiring, and pull it apart piece by piece.
Why it is useful
The builder had watched two well-known YouTube explainers and still didn't get how the rotors stepped, so they built something they could press a hundred times. It's a template for any "how does this actually work" page, from a camera shutter to an espresso machine.
What it looks like
A 3D Enigma sits on the page with a chapter list down the side: send an encrypted message, the plugboard, inside one rotor, the reflector, the double step, put it back together. Each chapter turns the model to the right part and animates it while a few lines explain what you're looking at. There's a history section with period photographs too.
How it was made
Mostly with GPT Astra, from reference images and "hundreds of extremely detailed prompts", one part at a time. The clever bit: they had the AI build inspection tools first, little pages that measure and check where each part sits, so every gear and pawl could be checked for size and position instead of trusting the model's eye. They've promised to open-source it once the wiring on the rarer models has been checked.
What it would take you
Codex on your ChatGPT Pro (Astra or Sol), a free 3D library such as three.js, Cloudflare Pages. A long weekend for one object, longer if accuracy matters. Slow performance on phones was the main complaint in the thread, so test on yours early.
The whole Solar System live in a browser tab, down to 526,000 asteroids and every tracked satellite
What it is
A live 3D map of space as it is right now, at real scale, from the planets down to the Starlink satellites and the scrap metal circling Earth.
Why it is useful
It's built entirely from free public data that refreshes daily, and the builder says it took "a few evenings" as a by-product of another project. That's the pattern worth stealing: find an open dataset nobody has made nice to look at, and make it nice to look at.
What it looks like
Drag to spin, scroll to zoom, click anything for a card and its orbit, double-click to fly to it. A time slider runs forwards and backwards, and satellites appear and vanish by launch date. People in the thread found the ring of satellites parked 36,000 km up and noticed that almost one in three tracked spacecraft is a Starlink. During the thread the builder added an ambient mode with flybys, eclipses and generated music, full screen on F.
How it was made
Three free sources (CelesTrak for satellite orbits, NASA JPL's small-body database for asteroids and comets, JPL Horizons for spacecraft), pulled daily. The trick that keeps 526,000 asteroids smooth: the graphics card works out every asteroid's position every frame, so the main processor barely touches them. The 30 MB asteroid file loads in the background while you're already looking at the planets.
What it would take you
A Cloudflare Worker on a daily schedule to fetch the data into R2, Pages for the site, Claude Code for the rest. A few evenings, free. Closer to home, the same approach works for any public feed: tides, flights into Southampton, ships in the Solent.
Jevmem: your coding agent writes down what you decided, using the Jev you already pay for
What it is
A small add-on for Claude Code that keeps a running list of project decisions in a file called JEVMEM.md inside the project, and hands it back to Claude at the start of the next session.
Why it is useful
It fixes the "I said Postgres on Tuesday and on Thursday it invented SQLite again" problem, and the log lives in the project folder rather than in Claude's private memory, so it travels between tools and machines. Separately, the same week someone had Jev play Pokemon Red all the way to the Hall of Fame: 16,150 decisions for about $1.65, which gives you a feel for how cheap these small yes/no calls are.
What it looks like
You work as normal. After each message Jevmem asks Jev whether anything is worth keeping (a decision, a rule, a bug, a change of mind) and adds the keepers to the file. Reverse a decision and the old line is marked "superseded" rather than deleted. Next session, the live lines are slipped back into Claude's context.
How it was made
It hooks into Claude Code after every turn and asks Jev a few typed save-or-skip questions, which is exactly the job Jev is built for. The builder tested it on 66 messages against six frontier models: 98.5% right on save or skip (tied with Astra), at about 0.3 seconds and $0.000127 a decision, against 3 to 4 seconds for the big models. They're upfront that it's a single run they built themselves.
What it would take you
Nothing to build: `npm i -g jevmem` and your existing TypeSafe key. Worth putting side by side with your own memory setup. Your messages, with secrets stripped, do go to TypeSafe's API.
Think out loud through a chess game, and get back a narrated video of what you got wrong
What it is
A set of Claude Code skills that turns one of your chess games into a commented video, built around what you were actually thinking at the board.
Why it is useful
Normal chess analysis gives you scores and long strings of moves. This answers your own questions in plain words, and because every claim is checked against a proper chess engine it doesn't flatter you. The builder says Claude "would have a hard time" calling a move good when the engine says it's bad.
What it looks like
You play a slow game with a voice recorder running and think aloud (the builder did it in French). Afterwards you tell Claude Code to analyse the game and give it the lichess link and the mp3. About an hour later you get an annotated game file and a web page with an analysis board. Ask for a video and you get a 6 minute 49 second narrated walkthrough with arrows, a score gauge and subtitles, saying things like "at move eight you asked yourself whether the bishop belongs on c4 or e2".
How it was made
The clever bit is lining the voice notes up with the moves. Claude transcribes the recording on the computer (whisper.cpp), then uses the clock times saved in the game record to match each sentence to the move you were weighing up. Then several helper agents question the chess engine (Stockfish) the way a person would, "why not my move?", "what if Black just takes?", until each mistake makes sense, and a final pass re-reads the lot for errors. The video is built from a storyboard with free local text-to-speech.
What it would take you
It runs on Claude Max as it is, but the builder puts one game at about $15 at API prices, so it eats quota. The pattern is the steal: your own think-aloud recording, a tool that checks the facts, a narrated video at the end. Swap chess for a shoot (voice notes on set, matched to the photo timestamps) and you've got a client walkthrough or a teaching reel, voiced with `speak`.
A shopping list on a little e-ink screen on the fridge, synced to everyone's phone
What it is
A small e-ink touchscreen (the kind of display a Kindle uses) stuck to the fridge, showing the household shopping list grouped by supermarket aisle, plus a phone web page that edits the same list.
Why it is useful
The builder says it's the first home project their family actually uses every day. It was also a test of whether Claude could write the software for a brand-new gadget they'd never worked with, and they say they didn't hand-write any of the 2,400 lines.
What it looks like
The fridge screen shows the list by aisle, in the order you walk round the shop. Tap items off as they go in the basket, and the on-screen keyboard suggests things you've bought before. On your phone you add items, reorder the aisles and set when it syncs (nothing overnight, more at weekends). They also put a basic MCP connector on it, so an AI can help plan the week's meals straight onto the list.
How it was made
Fully vibe-coded with Claude Code. The skill was in handling e-ink: quick partial redraws for taps, a full refresh every 10 changes to stop ghosting, and Wi-Fi switched on only while syncing so the battery lasts. A small server in the middle holds the list, and the first time it sees an item it asks Claude which aisle it belongs in; move it by hand and your choice sticks.
What it would take you
An M5Stack PaperMono at $55 to $65 (out of stock on M5Stack's own shop when checked), Claude Code, and a Worker with a D1 database in place of their home server. A weekend. The client version: a specials or stock board behind a bar that staff update from their phones.
A private Google Photos that keeps your pictures on Cloudflare R2, kept alive by Claude Code
What it is
Noodle Gallery is a Google Photos replacement you run yourself. It's a copy of Immich, the popular self-hosted photo app, with a pile of features bolted on that Immich's own team wouldn't take.
Why it is useful
Plain Immich keeps photos on the disk of whatever box it runs on. Noodle can store them in cheap cloud storage instead, including Cloudflare R2, and it fixes Immich's habit of treating one person as three different people when their face turns up in your library, your partner's library and a shared album. For a photographer with 20 years of files, that's a searchable archive with face search that doesn't rent your library back to you.
What it looks like
A timeline of your photos you can zoom out to years or months, a People page where each person appears once, and a Cmd+K search bar where you type "Sarah, Portugal, 2019, Fujifilm" and the filters fill in as you go. Near-miss faces the recogniser wasn't sure about turn up as a banner on the right person, and you tap same, different or ignore. Shared Spaces work like a family timeline that several people add to, with roles and an activity log.
How it was made
The clever bit is how a tiny project keeps up with a big one. Immich ships updates constantly, so every time a new release lands, the fork's changes are replayed on top of it (a "rolling rebase"), and the team built a command that shows only what that replay changed, since the raw diff against Immich runs to about 750,000 lines. The README says it's written "with a lot of help from AI coding tools (Claude Code and Codex)", with humans leading ideas, testing and debugging, and 36 of the last 40 commits credit Claude. One HN commenter flagged the flip side: hundreds of commits in a few weeks and no outside contributors, so they're waiting to see if it holds up.
What it would take you
Nothing to build if you just want it: it's free and open source (AGPL), runs in Docker on a Mac or a cheap mini PC, and R2 storage costs about 1.5 US cents per GB a month (a 2 TB archive is roughly 30 dollars a month). The steal for your own work is the method: fork an open-source app that's 90% right, have Claude add the missing 10%, and replay your changes on each new release.
A dead-man's switch for your scheduled jobs, which only speaks up when a job goes quiet
What it is
Sigabrt is a tiny monitoring service built by one person. Each of your automated jobs "checks in" when it finishes, and if a check-in doesn't arrive on time, you get an email or an ntfy push.
Why it is useful
Most alerts fire when a job fails. This catches the worse case, the job that never ran at all (the Mac was asleep, the drive wasn't mounted, the task silently stopped being scheduled), which nothing else will tell you about. The hosted version is free for one job and 15 euros a month after that.
What it looks like
You create an endpoint called, say, "nightly-backup", say it should report every 24 hours and that you'll forgive it 15 minutes late. You get a web address, and you add one line to the end of the job that visits it. The dashboard shows three nights of green ticks, then "Thu 03:15, nothing arrived, email sent". There's even a read-only view you open from the terminal with `ssh sigabrt.dev`.
How it was made
The whole idea is inverted monitoring: silence is the alarm. The job does its work, then calls a web address only if the work succeeded, so one line of code covers "crashed", "never started" and "machine was off". The service just remembers when each job last checked in and runs a timer. In the thread, the builder's own backlog adds a "started" signal for long jobs, and other people pointed at free equivalents like healthchecks.io.
What it would take you
An evening. A Cloudflare Worker gives each job a check-in address, KV (Cloudflare's small key-value store) remembers the last check-in time, and a Worker cron trigger (a built-in timer) looks every few minutes for anything overdue and fires your existing `claude-push`/ntfy alert. Free tier, zero pounds. It would sit neatly on top of every scheduled task you already run, including this digest.
Send a client a locked file that unlocks itself in any web browser, with nothing to install
What it is
A tool that turns any file into a single password-protected web page. The recipient double-clicks it, types the password and downloads the original. Think of an encrypted zip that doesn't need the recipient to have any zip software.
Why it is useful
Contracts, invoices, a raw file for a picky client, anything you don't want sitting readable in an inbox. It works offline, the file never touches a server, and there's no account for the client to make.
What it looks like
You open the tool, pick a file, type a password and hit Save. Out comes an HTML file. Your client opens it in Chrome or Safari, sees a password box, hits Next, checks the file name and size, then Download. The demo GIF on the repo shows the whole thing in about ten seconds.
How it was made
The trick is that the page carries both the locked file and the code that unlocks it, packed so it can also be opened with standard tools (it uses the same encryption standard as signed email, and even plain `openssl` can open it without the page). The builder took the idea from old "self-extracting archives", the .exe files that unzipped themselves. HN commenters raised two fair points: you still have to send the password by another route (WhatsApp, a call), and the recipient has to trust the page they've been sent.
What it would take you
Free to use today (Apache licence, live demo online). Building your own version is an evening with Claude Code, since browsers now do AES encryption natively: a single-file page on Cloudflare Pages that outputs locked HTML files, perhaps branded for your studio. Cost: nothing.
A two-person company built their own support desk, sprint planner and deploy tool, and wrote down how they stop them rotting
What it is
A write-up from Geocodio (just two people for nearly ten years) about replacing scattered scripts and SaaS tools with proper internal apps built with Claude, and the rules that keep those apps maintainable.
Why it is useful
It answers the question you'll hit once you've built a dozen tools for yourself: how do you keep them all working? And it gives three plain questions for deciding what to build and what to keep paying for.
What it looks like
Screenshots of their apps: a deploy dashboard showing which version each server runs, a sprint planner called Bullpen, a support desk called Atlas that pulls billing, account and history into one screen, and Yak, an agent that picks up small jobs from Slack and returns a finished change with a recorded walkthrough. Every tool has its own little documentation site with screenshots.
How it was made
The method is the valuable bit. Weeks of planning, hours of building. They pick a plan apart with Matt Pocock's "Grill Me" skill, which questions it until the weak parts fall out, mock up the screens before building anything, and use Fable for the planning. All their apps share one set of design parts, so none of them grows its own look. And every project's CLAUDE.md has a rule that any change affecting the docs means Claude must update the docs in the same go. Their build-or-buy test: do we actually know this domain, what happens if it's down for a day, and does the value come from plugging into our own data? Email stays with a paid provider for exactly that reason.
What it would take you
Nothing to buy. It's a playbook: copy the "update the docs" rule into your project CLAUDE.md files today, and run the three questions on the next SaaS you're tempted to replace. Two of their tools (Yak and Treehouse) are free and open source if you want to look under the bonnet.
Every 24/7 live camera on YouTube, pinned to a spinning globe
What it is
LiveWorld is a globe you spin to drop in on live webcams around the world: sea otters at Seattle Aquarium, airport aprons, train stations, volcanoes. One person built it in two weeks.
Why it is useful
YouTube has thousands of round-the-clock live streams scattered across random channels where nobody finds them. Putting them on a map turns a pile of links into something you can wander around, and it costs the builder almost nothing to run because YouTube hosts and streams all the video.
What it looks like
A satellite globe covered in pins. Tap one and the stream plays right there, with a small chat for whoever else is watching the same view. There's a "Feeling lucky" button, favourites, ambient audio, and a submit form for adding cameras. It launched with 641 cameras and now claims about 2,100.
How it was made
The content is the product, and the builder let the crowd fix it. HN readers found pins in the wrong city (a cam in Ohio shown in Chicago, Toronto filed under California) and dropped in missing cams, and he replied with fixes the same night, added each wrong pin to a test list so it couldn't come back, and promised a "right-click the globe to drop a pin" submit flow to replace the long form. Money comes from donations and a few ads.
What it would take you
A weekend. Plain HTML and JavaScript with a free globe or map library, YouTube's free embed player, and a list of streams with coordinates kept in D1 (Cloudflare's database), all on Cloudflare Pages for nothing. The angle for you: the same pattern for one place, for instance every live cam, sunrise spot and photo location around the Solent on one map.
A font workshop that makes deliberately cursed typefaces, like Times New Roman with every seventh letter in Arial
What it is
Bastardica is a joke font maker. Upload two fonts and it mixes them into one real font file that swaps in the second font every few letters. It started from Times New Bastard, a famous prank font.
Why it is useful
Mostly for fun (ransom-note headers, pranking a designer friend with Helvetica that's secretly one-third Arial), but it's also a genuinely usable effect for a poster or a playful brand, and it shows you can do heavyweight font editing in a browser tab with no upload.
What it looks like
Two upload boxes, one for the base font and one for the mix-in, a "swap every Nth letter" setting, and sliders to scale, nudge and slant the mixed-in letters so they sit on the same line. A preview line updates live as you type, and there are presets like "Temu Sans" and "Royal Ransom Note". Download gives you a normal font that works in browsers, Figma and print.
How it was made
The clever bit is using a font's own built-in letter-joining feature (ligatures, what turns "fi" into one joined shape) as a swap rule, so the font itself decides which letters to replace and every app just follows it. The editing runs on Python inside the browser tab (via a free tool called Pyodide), so fonts never leave your machine. The builder's tip: use prime numbers like 5 and 7 for the gaps, so mixed fonts collide less often.
What it would take you
Free to use now. Rebuilding something like it is a weekend with Claude Code on Cloudflare Pages at no cost, and the same trick (a font that swaps words or letters on its own) could make a memorable one-off title face for a client campaign. Check both fonts' licences before using a mix commercially.
A quiet koi pond on a web page, where each fish is another person watching, built by someone who can't write JavaScript
What it is
koi.rest is a calm little website: a hand-painted pond, soft water sounds and koi drifting about. Every fish beyond the first three is another visitor who has the page open at that moment.
Why it is useful
It's a proof more than a product. Paul, the builder, has ADHD, had just lost his job, and had sat on the idea for ages because he doesn't know JavaScript. He decided "good enough" beat "perfect", directed an AI to write all the code, and did the drawing, testing and taste himself. It's the clearest example this week of an idea going from head to live site without the builder writing code.
What it looks like
A landing screen with his painting of a koi and an Enter button. Inside, the pond fills the screen, fish glide around, a counter shows how many people are there, and new visitors pop in as new fish. There's deliberately nothing to click: the point is to do nothing for a minute.
How it was made
One cheap trick carries the "together" feeling. Instead of syncing every fish's movement between visitors (hard), the server only counts who is connected, and each browser spawns its own fish for that number, with three always present so nobody is ever alone in the pond. The HN crowd gave him a free QA pass: it stuttered under launch traffic and his host started refusing requests, and people asked for fish to fade in rather than pop, and for a solo mode without other visitors.
What it would take you
An evening. The visitor count is exactly what Cloudflare's Durable Objects (a small always-on counter living on Cloudflare) are for, and the rest is a single HTML page with canvas animation. The Durable Object needs the 5 dollar a month Workers plan if you're not on it; everything else is free. The same idea works for a photo gallery that shows how many people are browsing a client's wedding album right now.
A picture frame that listens to the garden and draws whichever birds it hears
What it is
A framed print on the windowsill that changes itself. A microphone outside picks up birdsong, software works out which species made it, and the frame redraws with a hand-cut 1800s engraving of that exact bird.
Why it is useful
As an object it's just lovely, and it took 2,287 points on Hacker News on charm alone. The pattern underneath is the useful bit though: a quiet screen in a room showing something true about that room right now, with no app, no account, and nothing leaving the house.
What it looks like
An A4 frame on a kitchen windowsill, matte and papery rather than glowing. Six birds sit arranged on a textured paper background, the larger ones pulled toward the centre and scaled by their actual body weight. Hear nothing for a while and you get a bare perch. It only redraws when the set of birds changes, so most of the time it just sits there looking like a print.
How it was made
The clever move is that he didn't build the hard part. Identifying a bird from its song is done by BirdNET-Go, free open-source software that already exists and runs on the little computer in the frame itself, so nothing goes off to a cloud service. His own code just asks it what it has heard, picks the matching pictures, and lays them out. The art is 800-odd cutouts across more than 400 species, every one cut by hand from a real out-of-copyright plate, deliberately not generated (some retouched with AI, none created by it). Two nice details for anything on e-ink: the finished collage gets reduced to the six colours the panel can actually print, and it only redraws when the birds change, because an e-ink refresh is slow and you can watch it happen.
What it would take you
A Raspberry Pi 5, a mic, an A4 frame and an Inky Impression e-ink panel. It comes in 4.0in, 7.3in and the 13.3in he used, which is nearly A4 and the expensive one, so budget accordingly and check Pimoroni for the current price. The software is free and there's no API bill, because the classifier runs locally. It also runs with no panel at all, as a web page on any screen, which is the cheap way to try it. The version that transfers to your work is the same shape with a different input: a screen in a restaurant showing what came in this morning, or a frame in the studio cycling the newest gallery.
A machine you can walk around inside, built to explain one piece of software
What it is
A web page that turns an invisible bit of server software into an explorable engine room, with decks you can look around, parts you can click, and experiments you can run.
Why it is useful
The subject doesn't matter and you'll never need it. The technique does. Turning a process into a place, where where-a-thing-sits tells you what it is, is the most persuasive way to explain anything complicated, and it works just as well for how a kitchen runs at service or how a booking moves from enquiry to table.
What it looks like
A dark control-room interface. Live counters along the top (8 keys, about 128 KiB allocated, model time 0.2 seconds). Down the page, labelled decks stacked like floors of a building: outside clients at the top, then the running program, then the data, then memory, then the operating system, then the physical disk at the bottom. Every part is clickable. At the bottom sit four runnable experiments, including one where you send a command and watch the route it takes, and one that shows why memory stays high after you've deleted things.
How it was made
It's a normal web page with a small simulation running behind it. The layout is doing the arguing: everything is stacked in the real order, from outside the machine down to the disk, so the diagram teaches you the hierarchy before you've read a word. The numbers along the top aren't decoration either, they move as you poke at it, which is what makes it feel like a machine rather than an illustration. As far as you can tell from using it, the whole thing runs in the browser with nothing installed.
What it would take you
Plain HTML, CSS and JavaScript on a Cloudflare Page, so nothing to run and nothing to pay. The code isn't the work. The work is deciding what the layers are and what each experiment proves, which is a couple of hours of thinking and then an evening of building for a simple one. The obvious client use is a page that shows a process instead of describing it in a paragraph nobody reads.
An app you can send someone like a Word document, with its data already inside
What it is
A way of packing a small web app and everything it has saved into a single file you can email, AirDrop or drop in a chat. The other person taps it and it opens, with the data already in it.
Why it is useful
It goes at a gap that's got worse as building got easier. Knocking up a little tool as a web page takes minutes now, but the moment it needs to remember anything you're into hosting, accounts and a database. This keeps a tracker, a price list or a job log as a file you own, the way a spreadsheet is a file you own.
What it looks like
You describe what you want and get back a single file ending in .capsule. Open it and you get what looks like an ordinary small app window, your data already loaded. Move it to a USB stick or your cloud drive and it's still the same document, same interface, same contents. Anything in it can come back out as CSV or JSON.
How it was made
The file is a SQLite database, the small self-contained database that already sits inside your phone and your browser, with the page's HTML, images and other assets stored inside it alongside the data. His own comparison is the right one: a spreadsheet is also just an interface plus its data in one file. It's written in Rust with Tauri, a toolkit for wrapping a web page as a proper desktop app without shipping a whole copy of Chrome with it, and a capsule can't reach the network unless you allow it. The Hacker News thread went hard at the obvious catch, and it's fair: the recipient has to install the free player first, which is friction a plain HTML file doesn't have.
What it would take you
Nothing, it's free, with players for Mac, Windows and Linux. The idea is worth more than the product for your kind of work: a job sheet or a quote calculator that a client keeps as a file rather than as yet another login. Spend an hour on the examples on the site before deciding whether the install step kills it.
A flight simulator where you aren't the pilot, you're in seat 14A
What it is
Pick any two airports in the world and take the flight as a passenger. Real terrain out of the window, real weather, and the sun in the right place for the actual time of day.
Why it is useful
It started as a joke and found a real use by accident. In the comments, several people who are frightened of flying said this is the training they'd actually wanted, because cockpit simulators teach you to be a pilot and their problem is being stuck in a seat with no control at all. One had paid for simulator training with a pilot and said it missed the point entirely. That's the lesson worth taking: a build with one strong idea, done properly, finds uses its maker never planned.
What it looks like
It opens on a dark world map scattered with airport codes, asking where you want to fly to, with a from box and a to box. Pick a pair, hit continue, and you get the window seat: shade up or down, tray table, seatbelt. A recent update added legs, so you can now get up and go to the toilet on the long ones.
How it was made
It's a Next.js web app using Esri's satellite imagery for the ground. The thing that makes it work isn't technical, it's the discipline. This isn't a flight simulator with a passenger mode bolted on, and everything you're allowed to do is something a passenger can do. The atmosphere comes almost entirely from the boring stuff, the shade and the tray table and the walk to the toilet, not from the scenery.
What it would take you
Ordinary web work with tools you already have, and the only running cost is map tiles, where the free Esri and OpenStreetMap tiers cover a hobby project comfortably. The hard part is holding one idea and refusing every feature that sits outside it, which is the bit most builds fail at, and it costs nothing but nerve.
Someone measured how much screen a browser actually gives you, and it's less than you think
What it is
A small research site that measured real browser windows rather than screen sizes, then published the spread with a calculator you can test your own layout against.
Why it is useful
One number is worth the visit. A 1080p monitor doesn't give you 1080 pixels of page height, it gives about 920 once the browser's own chrome is taken off, and 1920 by 920 is the single most common desktop pairing in the sample at 11.7%. The median mobile width is 400px. So a hero built to fill 1080 is already scrolling for most people, which is a thing worth knowing before you design the next one. The honest caveat, which the site states itself: it's 962 qualified observations from people who visited a screen-size tool, so use it to test layout constraints, not to estimate market share.
What it looks like
A report page with a calculator at the top. Type in a content width or a starting page height and it tells you what share of observed sessions would fit it. Below that, a table of how many observations came from each device type, then a row of actual viewport shapes all drawn at the same height so you can see the aspect ratios sitting next to each other.
How it was made
Not clever at all, and that's the interesting part. He already runs a screen-size checking tool, so the data was a by-product he happened to be sitting on. The work went into the honesty: publishing the exclusion rules (old tablet readings thrown out because the original classifier could mistake a touchscreen desktop for a tablet), setting a minimum sample before a category gets published at all (tablets have none, so nothing is published for them), and saying on the page what the numbers can't be used for. That's what makes a small dataset trustworthy rather than embarrassing.
What it would take you
Nothing to build, just take the number. 920px is the height that should be in your head for hero sections, and it's worth sitting alongside 1920x1080 in the visual QC pass. The build pattern is one you could run though: a free tool that quietly records one measurement, and a published report off the back of it that becomes the thing people link to.
A place to see how other people have actually set up their AI tools
What it is
A community directory where builders publish their working setup: which tools, which agent, which skills, which workflow. One bloke built it because he couldn't work out from scattered posts what everybody else had figured out.
Why it is useful
Two ways. As a resource it's a shortcut to other people's configurations, which is otherwise guesswork pieced together from screenshots. As a build it's the cleanest example going of the most reliable small-site idea there is: find a thing people keep posting in fragments, and give it a proper home.
What it looks like
A plain page written in his own voice, opening with "What's the craic with your AI setup?", his own setup published as the first entry so the place isn't empty, and a community list behind a sign-in. Adding yours is the only thing it asks you to do.
How it was made
Ordinary web app work, nothing exotic in it. The craft is entirely in the framing. The homepage opens by admitting he hasn't got his own setup figured out either, lists the things that confuse him by name, and says out loud that this might well end up a community of one. That honesty is most of why it got 213 points, and it's a better opening than any confident pitch would have been.
What it would take you
Directly buildable on Cloudflare Pages with D1 holding the entries, free at this size, an evening or two for a first version. The move worth stealing isn't the code, it's the first-person opening that admits what it doesn't know. It reads as human because it is, and it costs nothing.
People are pointing agents at kit they already own and unlocking things the manufacturer disabled
What it is
Not one build, a pile of them in one thread. Someone got an agent to work out how their office printer talks and write working software for it, and the comments filled up with people who'd done the same to other locked-down hardware.
Why it is useful
It's a recurring trick now rather than a one-off, and the examples are better than the original post. A Samsung monitor whose second display output the manufacturer never bothered to wire up properly: the model read the firmware, worked out which compiler built it, changed the logic, repackaged it, and the owner gambled on flashing it, and it worked. An LG laptop whose fan speeds are locked behind LG's own control app, unlocked in under twenty minutes. An analogue synth whose firmware was pulled off it, its undocumented instruction set worked out, the whole device emulated and turned into a plugin you can load in music software.
What it looks like
Almost nothing to look at. It's a long conversation with an agent, feeding it firmware dumps, captured traffic and disassembled code, and asking it what the pattern is.
How it was made
The reason this is newly possible is that these problems have no answer online to look up. As one person put it, there was no prior code and no niche forum thread for what he was doing, so the model had to generalise from scratch. That's the actual shift: agents have got good enough at reading unfamiliar binary and undocumented protocols to work out a format nobody ever wrote down.
What it would take you
Nothing beyond time on the plans you already pay for, and it works on either Claude or Codex. Two warnings from the thread itself, both real. Flashing modified firmware bricks hardware, and the man who did it said so plainly in his own post. And one dry comment is worth keeping in mind before you start: the moment you have a custom driver, you maintain it forever.
A free image editor for Mac and Windows, described rather than written, for about 2,000 dollars of agent time
What it is
A desktop photo editor, free and working offline, built by someone describing what he wanted to GPT Astra over an extended run instead of writing it himself.
Why it is useful
The honest numbers are the reason to read it. He says it cost roughly 2,000 dollars in tokens, it got 170 users on day one, and he calls it usable but buggy and unstable. The comments agreed with that last part, firmly.
What it looks like
A normal desktop editor window with builds for Mac, Windows and Ubuntu, free, working with no internet connection.
How it was made
By description, over a long run, and two things came out of the thread worth keeping. First the cost: that 2,000 dollars is metered API spend, not a subscription. On ChatGPT Pro the same work wouldn't bill per token, but it would still eat several weeks of allowance rather than an evening, so treat "vibe coded" at this scale as a real commitment. Second the reception: saying it was vibe coded lost him the room. More than one commenter said that mention alone cost the app its credibility, and the recurring practical complaint was the familiar one, that it works right up until it doesn't, because the person describing it can't always tell what he forgot to specify.
What it would take you
Not this, and not at this scale. Take it as calibration instead. Ambitious desktop software built by description is genuinely possible now and genuinely expensive in agent time, and whether you say out loud how it was made is a marketing decision rather than a technical one.
A shared support inbox that runs on your own Cloudflare account for nothing
What it is
A self-hosted helpdesk, the free equivalent of Zendesk or Freshdesk, for a team of one to five people. Emails to your support address arrive as tickets you can assign, tag, prioritise and search instead of as a mess in one inbox.
Why it is useful
Every helpdesk on the market charges per person per month, and you outgrow the free plan the moment a second person needs to see the same inbox. This one has no per-seat cost at all, because it runs in your own account, and small volumes stay inside Cloudflare's free plan. The client data sits with you rather than with a supplier, which also makes a deletion request something you can actually honour: it exports everything held on one customer as a file, or erases it and cancels any mail still queued for them.
What it looks like
A three-pane inbox, tickets down the middle, the conversation on the right, an aubergine sidebar on the left that will look familiar to anyone who uses Slack. Click a ticket and you get the full email thread with attachments, a box to reply, a separate tab for a private note your customer never sees, and saved replies for the questions you answer weekly. Cmd+K jumps you anywhere. There's a Reports page with volume and response times you can export to a spreadsheet, a rules page that files and assigns tickets automatically, and a public help centre that publishes whichever knowledge-base articles you mark as ready while drafts stay private. It works properly on a phone, with the destinations moved to a bottom bar, and it does light and dark.
How it was made
It's one Cloudflare Worker, so one thing to deploy and nothing to keep patched. Incoming mail is handed straight to that Worker by Cloudflare's own email routing, and the tidy trick is what happens next: rather than send the reply there and then, it drops the job on a Cloudflare queue, so a send that fails gets retried instead of disappearing, and anything that fails repeatedly lands in a recoverable pile rather than the bin. Tickets live in D1 (Cloudflare's SQLite database), attachments in R2 (its file storage), and a cron job every five minutes picks up stalled mail and clears orphaned data. Outgoing email goes through Resend, because Cloudflare will receive mail but won't send it. There's a Deploy to Cloudflare button on the repo, which provisions the lot in your account in one go.
What it would take you
This is your stack, top to bottom, and the deploy button means an evening rather than a weekend. You need a domain sitting on Cloudflare (you have several), R2 switched on, and a Resend account with a verified sending domain for outgoing replies, which has its own free allowance. Two things to know before you start: heavy mail parsing may push you onto the paid Workers plan, which is the usual $5 a month, and the AI reply drafting is the one part that isn't free, since it wants an OpenAI API key. Leave that switched off, which is the default, and nothing is sent to anyone. Worth pointing at a client support address, or at info@ for Padharo.
An illustrated reference site built with AI, and a public argument about which bits still show
What it is
A browsable encyclopaedia of strange things the human body does, the sort of site that used to take a small team a year. Around 200 entries, each with an illustration, a plain description and a figure for how common it is.
Why it is useful
Not for the subject, for the argument underneath it. It hit the Hacker News front page and then took a proper kicking in the comments about which sentences still read as machine-written, with the man who built it answering and asking people to point out more. That thread is the most useful thing published this week if you build content sites for clients, because it is a live list of the tells readers actually notice, plus the exact instructions he uses to avoid them.
What it looks like
A grid you can filter two ways, by body region (brain, bones, muscle) or by kind (involuntary, perception, variation). Each card has a photographic illustration, two or three sentences in flat, dry English, and a prevalence line underneath: "about 1% have no mental images", "under 1% of people", and where nobody knows, it says nobody has counted. Click through and the entry has its own page with sources at the bottom. There's a changelog page listing what was added when, which is a small thing that makes a reference site feel maintained rather than dumped.
How it was made
Built with Claude in Astro, a site builder that spits out plain fast HTML pages with no framework running in the browser. The method is the interesting part, and it is his own description: the first version "looked like complete slop", so he now tells the model, element by element, which look to avoid, naming specific cliches (he calls out the famous left border on quote blocks). For the writing he instructs it to use Standard Technical English, to be dry and technical, and not to embellish or tell stories. Then he still edits the cringe out by hand. He says he does this because he makes lots of small sites and has learned to undo the defaults one at a time.
What it would take you
Nothing you don't already have, and the per-element ban list is what your own humanise and impeccable setup does already. Take the two lessons rather than the site. First, readers spotted the writing anyway and named the shapes: sentences that end with a hanging clause, and the word "quietly". Worth adding both to your scanner if they aren't there. Second, and this is the one that would actually embarrass a client, the sourcing got shredded: most entries cite only Wikipedia, and someone checked one citation and found the linked page never mentions the claim at all. On a client site that is a correction, not a comment.
He handed over the code of his 1993 game and the AI rebuilt it, proving byte by byte that it matched
What it is
A game written in Baghdad in 1993 for an Amiga home computer, rebuilt as a modern game for phones and Steam. The author didn't do the port. He asked for it, played every build, and made the handful of decisions that needed somebody who was there at the time.
Why it is useful
It is the best worked example going of how to move an old, undocumented, nobody-else-understands-it codebase onto something modern without guessing. The technique at the centre of it applies directly to the WordPress migrations you do: before changing anything, make the old thing rebuild itself, and prove the result is identical to what shipped. Everything after that is a comparison rather than a hope.
What it looks like
Buy the modern game and the original 1993 version is a second thing you can launch from inside it, running at the Amiga's own speed. The blog post itself is the artefact worth looking at: photographs of the same castle gateway in 1993 and 2026 side by side, his own assembly code with the comments he wrote to himself as a student, and unedited timestamps showing what happened when.
How it was made
Claude Code with a terminal and the filesystem, so it could edit files, run the assembler, build the game, launch it and read what came back. He gave it three jobs of rising difficulty over one weekend. The first was safe: move the 34,000 lines of C++ from his 2010 phone version into Godot, the free game engine. The timestamps are 22:23 for an empty project, 22:44 for a playable character, 02:15 for builds exporting to Mac, iPhone and Android. The second job was the real test: 72,758 lines of assembly (code written directly for the chips of a machine that stopped being made in the nineties), no useful comments, with the filenames mangled by a file transfer in 2008 and one source file cut off mid-table. Before porting a line of it, the agent got those 1993 sources to assemble again with a modern free assembler and kept going until the bytes it produced were identical to the binaries that shipped on the original floppies. Two more things are worth stealing. It added command-line switches to the game so it could test without him: load a level directly, place the characters at exact positions, press buttons from a script frame by frame, dump the state of every door and switch, take a screenshot and quit. And it kept two different clock speeds, 50 per second for the original and 60 for the modern one, because the game slows the player down by multiplying their speed a little every frame, so the same number gives different friction at a different rate. Nothing crashes if you get that wrong, it just feels wrong forever and never shows up in the code.
What it would take you
Claude Code, which you have, plus free tools (Godot, an assembler, an emulator). The honest bit is his, not mine: parts of it were wrong and he didn't notice for weeks, including a workaround that quietly shifted everything after one point in a file 944 bytes away from where it belonged, so the game built, booted, and drew the wrong thing. His safety net was the byte comparison, and it is the bit he says nobody asked for and he'd never have bothered with himself. A weekend, not an evening, and only worth it where you can make the old system prove itself the same way.
Hacker News with the AI stories stripped out, filtered by a small model he trained himself
What it is
A replacement front page for Hacker News that removes anything about AI. Two people shipped one in the same week, unaware of each other, and both hit the front page within a day.
Why it is useful
Forget the politics of it. This is a working, cheap recipe for the job you keep needing, which is judging a pile of content by a rule too fuzzy for keywords, without paying per item forever. It is also a lesson in what to do when the obvious paid API is too expensive.
What it looks like
Almost exactly like Hacker News, just shorter. A settings bar at the top lets you pick a layout and set your own exclusion filters (any topic, not just AI), and each filter can be turned into its own RSS feed, so you can subscribe to a filtered version rather than visiting a site. A line at the foot of the page tells you the damage: "79 of 179 submissions survived the filter". Comments open in a drawer rather than a new page. One reader said they had been using it as their phone client for months without realising the filter was new.
How it was made
Two stages, and the builder spelled both out. First a plain list of domains and keywords knocks out the obvious. Then, twice a day, whatever's left gets read by a small language model he fine-tuned himself on about 8,000 examples, which decides whether an article is really about AI. The part worth stealing is where those 8,000 examples came from: for the best part of a year he had an agent read the feed daily and put about 20 stories in front of him to judge, and his judgements became the training data. Once the small model could match him, the expensive model was out of the loop entirely. He also checks whether a GitHub project was written by an agent, by reading the commit messages for agent attributions, the contributor graph, and the config files an agent leaves behind. The other builder took a different route and paid for a detection API, and said in the thread that it was very expensive, which is the whole argument for this approach in one line.
What it would take you
The labelling year is the expensive part and you can skip most of it: you already have three subscriptions that will judge a few hundred items for nothing, so a weekend of automated labelling gets you a training set. Hosting is a Worker, a cron trigger and KV, which is free. The one new skill is fine-tuning the small model, and that is an hour or two of rented GPU time, so a few pounds at most. A cheaper first version skips training altogether: keyword rules plus one small model call per item, cached, which for a feed of a couple of hundred items a day costs pennies. Obvious uses for you are sorting incoming client enquiries by type, and filtering the hospitality and photography news you actually want.
A printable poster of what is in season this week, with all 731 prompts that built it published
What it is
A tool that makes a printable poster of what is in season at your local farmers' market, region by region, accurate to the week. Think of the seasonality chart a greengrocer pins up, except designed to go on a wall rather than into a leaflet.
Why it is useful
Two reasons, and the second is the bigger one. The poster solves a real problem for anyone planning around seasons, because the existing charts are month-level and built as reference leaflets. The real value is that the author published the entire conversation that built it, all 731 prompts, searchable and grouped into chapters, so you can read how a finished and polished thing actually got made instead of guessing from the result.
What it looks like
You pick your region (San Francisco or New York so far), tick the produce you care about, and print. The chart is a stack of ridges, one per crop, each swelling at the weeks that crop peaks, with faded bands for "peak only in some years". The artwork is old botanical watercolours, apples and plums painted by USDA illustrators a century ago, and that is the thing stopping it from looking like a spreadsheet.
How it was made
One continuous Claude Opus 5 session, 731 prompts, 22 working days spread over 46. The working rule is the part worth copying: the model wrote all the code but was never allowed to save it into the project's history, so every change sat unstaged waiting to be read before it counted. He says it took a bit of training at the start to get it planning small changes and doing them one at a time, then it held that habit with the occasional reminder. Two of the best ideas came from the model, not him. His original chart was a wobbly stacked ribbon that looked fine on fake data and fell apart on real spiky data, and the model proposed the ridge layout instead. When the poster felt sterile and he was floundering with clip art and stock photos, it suggested the USDA watercolour collection. It also dug out the government shipping data that gives week-level accuracy, then worked out that lorry loads leaving the farms around a city tell you more than deliveries arriving into it. He is straight about the misses too: far too many comments, too eager to spray code across new files, and naming decisions made at the drop of a hat when those are the things you most want discussed first.
What it would take you
Closest fit of anything here. It is print design driven by data, which is your Typst pipeline, and "what is in season this week" is exactly the thing the restaurant clients plan menus around, so a UK version off DEFRA or supplier data is a real client deliverable rather than a toy. Free: it is a static site, so it deploys onto Pages as-is. Copy the published-transcript page too, because showing a client how the thing was made is a sales asset nobody else is offering. A weekend for a rough one, longer if you chase good UK data.
A business card with no battery that lights up 21 LEDs when you tap it on a phone
What it is
A circuit board cut to credit card size and thickness, used as a business card. Tap it against a phone and 21 tiny lights run an animation. There is no battery anywhere in it.
Why it is useful
It is the physical half of a digital business card, and it solves the two things that usually kill these. Nothing to charge or replace, because the phone powers it for the second it is touching. And the link it hands the phone is a redirect he controls, so he can point the card anywhere, forever, without reprinting a single one.
What it looks like
You hold it flat against the back of someone's phone. Their phone opens his contact page, and at the same moment a ring of lights around the edge of the card animates, running on nothing but the phone's own field. His own note on it is that it is almost impossible to photograph, because the card has to be pressed against the phone to light up at all.
How it was made
The trick is how NFC works. Your phone throws out a small magnetic field a few times a second, so to a tag it behaves like a tiny wireless charger. Most tags use that scavenged power only to run their own innards, but a couple of chips will pass the spare voltage out to other components, and that is the one feature the whole card hangs off. The lights use a wiring trick (Charlieplexing) that lets six pins control twenty lights, at the cost of only one being lit at a time, which he hides by flicking between them too fast to see. The aerial is a flat spiral of copper traced round the card itself, tuned so it resonates at the right frequency. Here is the AI bit: the circuit board software has no tool for drawing a rectangular spiral and none of the plug-ins could do it, so he had an LLM write him a short script to generate the coil, had it working after a few minutes of conversation, and left the script in the repo for the next person. The boards were assembled by a factory rather than by hand, and he ordered 30 instead of 5 after working out that each extra card barely moved the bill.
What it would take you
The honest answer is that the card is hardware and is the furthest thing here from your usual work, and circuit board design is the real learning curve (three months for him, and he went in wanting the practice). He does not publish a total cost; the components are pennies each and the spend is the assembled factory run, so get a quote before committing to a batch. But one piece applies to your existing digital card today and costs nothing: put the card's QR and NFC link on a subdomain you redirect in Cloudflare, so the destination is editable forever and the printed cards never go stale.
Point a laser pointer at a wall and a projector paints where you drew
What it is
A web page that turns a projector, a webcam and a cheap laser pointer into a wall-sized drawing tool. You point the laser, and the projector paints a glowing line exactly where you pointed.
Why it is useful
For a venue it is a crowd activity with nothing to install and no hardware to hand out and lose. Set it up from a laptop in ten minutes at a launch night, a party or a festival stand, and people queue to have a go. It also photographs beautifully, which matters if you are the one shooting the event.
What it looks like
Plug the projector in as a second screen, aim a webcam at the wall, and open two browser windows. One click flashes markers into the corners of the projection so the camera can work out where the wall is. Wave the laser about for four seconds so it learns your particular dot. Then you draw: six brushes, wet ink that dribbles down the wall, a mode that extrudes your drawing into a slowly spinning 3D object, kaleidoscope mirroring, a sparkle trail. Hold the laser in the corner and a menu opens on the wall, so nobody has to walk back to the laptop. There is even tic-tac-toe against the computer, played by drawing an X on the wall. You can try the whole thing on the page with your mouse standing in for the laser.
How it was made
All of it runs in one browser tab with no libraries whatsoever. Two clever bits. The calibration: it flashes markers into the four corners of the projected rectangle, the camera spots them, and from those four points it can translate any position the camera sees into the matching position on the projector, which is why the paint lands where you pointed rather than where the camera happens to be standing. Then the dot learning: the four-second wave teaches it that specific laser's brightness and colour, and that is what lets it work on a shiny floor where reflections would otherwise read as a second laser. It is a from-scratch browser rebuild of a Graffiti Research Lab project from around 2007 that needed a desktop install to run.
What it would take you
Nothing to build, which is the point. It is MIT licensed and open source, so it is a fork, a restyle and a client's name on it. The transferable technique is the corner-marker calibration, which is the same maths any time you need to line up what a camera sees with what a screen shows. Cost is a laser pointer and a projector you probably already have access to, and green lasers read best on camera.
He used an AI to build a tool so that it would never need an AI again
What it is
A terminal helper. You type what you want in plain English and it hands you the command. The twist is there is no AI model in it at all. It runs on the processor, answers in thousandths of a second, and gives the same answer every single time.
Why it is useful
A thing that runs commands on your machine is the worst possible place for something that is right nine times out of ten. That is the author's own argument: for a terminal assistant, failing once in ten makes it useless, and the small local models he tried were too slow and too unreliable to trust. His version cannot invent a command that does not exist, costs nothing per use, works with no internet, and cannot be talked into anything.
What it looks like
You type `termy` followed by something like "delete every log file older than a week" and it replies with the command, instantly, in a faintly cynical voice. When you want it to understand something new, you open a plain text file in its dataset folder, add the phrasing and the command it maps to, and run one reboot command. No training step, no model to download, no waiting.
How it was made
The clever bit is the author's own, said plainly in the comments: this design is only feasible now BECAUSE good LLMs exist, because they are what makes building the dataset feasible. The reason nobody bothered with old-fashioned pattern matching any more is that somebody had to hand-write thousands of ways people might phrase the same request, and that is precisely the boring bulk work a model is good at. So he spent the model once, up front, generating the lookup tables, and the finished tool runs without one forever. The framework underneath also impersonates an OpenAI endpoint, so anything built to talk to a model can be pointed at it instead with no changes.
What it would take you
The most directly stealable idea in today's lot, and it is free. Take any client job where the questions genuinely repeat, an enquiry triage or a venue FAQ, have Claude generate the question and answer pairs once, then serve them from a Worker with no model call at all. It answers instantly, costs nothing per visitor no matter how busy the site gets, and can never say anything to a customer that the client has not already signed off. An evening, not a weekend.
Free software turns one off-the-shelf screen gadget into a cycling computer
What it is
Free firmware for a single thing you can buy: a 4.7 inch e-paper screen with a processor, wireless, touch and a card slot already built into the back of it. Load the firmware and it becomes a bike computer, with speed, distance, heart rate, offline maps and turn-by-turn directions.
Why it is useful
It does the job of a Garmin or Wahoo head unit, which run into the hundreds. The display choice is the interesting part: e-paper is the stuff in a Kindle, so it is readable in direct sunlight and uses almost no power, which is exactly backwards from the bright screens the big brands are moving to and is what got cyclists in the comments excited.
What it looks like
The first screen shows power, heart rate, speed, distance and ride time. Press the Home button and you get the workout screen, with your target, your live effort, how long is left in the current block and the shape of the whole session. Press again for a map, drawn from map files sitting on the memory card, following GPS with no phone signal needed anywhere. Tap the bar at the top for a menu to pair a heart rate strap or load a route. When you finish, it shows a summary before anything is saved, and only then writes the ride to a standard file your usual app will read. You can rearrange which numbers appear where either in a phone app or by editing a text file on the card.
How it was made
The shortcut is the whole story. Instead of designing hardware, he picked one board that already has every part the job needs, screen, processor, wireless, touch, clock, card slot and battery management, and wrote only software for it. That turns a parts list into a single instruction: buy this exact board. He is upfront that you buy it and sort out protecting it yourself, so there is no kit and no case. Worth noting the gap, because it applies to anything you publish: the most-liked suggestion in the thread was that he put a parts list and a rough price at the top of the page, which the project does not currently have, and the commenter's reason was that people need a ballpark before deciding whether to spend their weekend on it.
What it would take you
Only worth it if you actually want a bike computer, since this one is firmware for someone else's board rather than a method to reuse. The project does not publish a price, so check LilyGO's own shop for the T5 E-Paper S3 Pro before deciding. The transferable trick is the shortcut above: when a project needs several bits of hardware, look for one board that already contains all of them and write nothing but software.
One command that lists every AI tool on your Mac, and what each one is allowed to touch
What it is
A safety inspection for your own laptop. It works a bit like a virus scanner, except it's hunting for AI coding tools rather than viruses, and it removes nothing. It just tells you what's installed and how much damage each thing could do.
Why it is useful
Anyone who's been using AI coding tools for a year has quietly accumulated a dozen add-ons, each of which can run commands, read files and hold passwords. Almost nobody can answer "what's actually running on this machine, and what can it reach". This answers it in about ten seconds, free.
What it looks like
You type one line into a terminal. Out comes a list grouped by tool family, with tags in brackets next to each entry: EXECUTES, BROAD-FILESYSTEM, NETWORK, HOLDS-SECRETS. The example scan on the project page shows nine things across three families, seven of which can execute code, and one with an API key sitting in plain text in a config file. It names the key and then tells you, in ordinary English, what to do about it.
How it was made
The clever move is that it doesn't watch anything. No background process, no account, no data sent anywhere. It just reads the settings files these tools already leave lying around in your home folder and translates them into plain language. It also has no third-party code in it at all, which matters for a tool whose whole job is telling you what to trust. The author's line in the comments: "The radiation was already there, I just built the counter."
What it would take you
Nothing, run it tonight with `npx geiger-scan`. Free and MIT licensed. Given how many connectors you've got wired into Claude Code, this is the closest thing to a free ten-second audit of the lot. Building your own version would be a weekend, and the actual work is knowing where each tool hides its config.
A park where light travels at walking pace, and you can outrun it
What it is
A browser toy that drops you into a park where the speed of light has been slowed to 5 km/h. It's a first-person game with no goal and nothing to win. The point is that the world visibly bends as you speed up.
Why it is useful
It isn't, and that's rather the point. It's the best argument going that a plain folder of files, with nothing installed and nothing built, can still be the thing everyone's talking about for a day.
What it looks like
You click, look around with the mouse, and hold W to walk. As you speed up the park stretches out ahead of you, things in front turn blue and things behind turn red, and the watch on your wrist starts falling behind the world clock in the corner. There's a readout showing your speed as a fraction of light, which you can never quite reach. A settings panel lets you switch each effect off one at a time, so you can work out which strange thing is causing what.
How it was made
The author's own description of the project is "no dependencies and no build step". You serve the folder with a single line and open it in a browser, and that's the whole deployment story. The one genuinely tricky bit is that the ground gets quietly rebuilt in finer detail as you approach light speed, because the geometry stretches so far that a coarse floor would start showing its joins.
What it would take you
The plumbing is identical to any of your static sites, a folder dragged onto Cloudflare Pages. The hard part here is the physics, not the hosting. Cost: nothing, and the source is public if you want to read how it's put together.
A nuclear engineer mapped every reactor on Earth, then started selling the alerts
What it is
An interactive world map of all 442 working nuclear reactors, plus the research ones, built by one engineer who used to work in the field.
Why it is useful
For you it's the shape that matters rather than the subject. A free, genuinely good map pulls people in, and a paid layer sits on top of it: an email that tells you when a particular plant's output changes. That's a business model you could lift wholesale onto something local.
What it looks like
You land on a 3D globe with pins clustered by country, and a panel down the side ranking countries by capacity (United States 96,952 MWe, France 63,000, China 62,329). Drag the year slider and plants appear and vanish as they were built and shut down. A toggle flattens the globe into an ordinary 2D map. Then there are sections for comparing countries, a wiki, and a monitoring feed of output changes and news with a "subscribe to alerts" box attached.
How it was made
He paid for none of the map. The terrain and street data all come from free public sources (Mapzen tiles hosted on Amazon's open data programme, OpenStreetMap, OpenFreeMap), so hosting is close to his only running cost, and the reactor data is public too. Being a nuclear engineer is the actual moat: he knows which numbers are worth showing. Worth copying separately, he was shipping fixes to the site within hours of people complaining in the comments that the globe felt awkward to navigate, and said so in the thread.
What it would take you
Free map tiles, plus a public dataset, plus a Worker, is a pattern that fits half a dozen ideas you already half have. Every restaurant in the city by cuisine, say, or every listed building in Southampton. A weekend for something presentable, and nothing to pay as long as you stay on the free tile sources.
A social network you post to by typing a web address
What it is
A message board with no app, no form and no sign-up. You post by visiting a URL with your message written into the address itself.
Why it is useful
It's a joke with a sharp edge. Everything that would normally need a proper form submission is done with a plain link instead, which means anything at all that can open a web page can post to it, including software that was specifically prevented from posting to websites.
What it looks like
Posting is literally opening `gettogether.dev/post?name=alice&text=hello` in a browser. Liking something is another address, deleting is another. There's no password: the site hands your browser a small token the first time you post, and if you hang onto it you can delete your own posts later. Names aren't unique and aren't checked. It limits you to one action every ten seconds and screens new posts for profanity and crypto spam.
How it was made
Browsers won't fire the usual kind of "submit this" request from a plain link, so he built the whole thing on the ordinary "fetch me this page" request instead, which is the one that works from anywhere. The top comment in the thread spotted what that implies straight away and asked whether the whole site is a honeypot for AI agents that have been blocked from posting anywhere.
What it would take you
This is almost exactly a Cloudflare Worker with a KV store behind it: read the address, write a record, hand back the feed. An evening, and free on the tier you're already on. The transferable bit for client work is smaller and more useful than the joke: a single click in an email, or a scanned QR code, can do real work with no form in the way.
A game where you try to make one button blue, and lose
What it is
A single web page that plays out an AI coding session going wrong. You're given one job, make the "Add to Cart" button blue, and told not to let it change anything else.
Why it is useful
It's worth five minutes for the design lesson buried in it, and worth longer for the marketing one. There's no product here, nothing to sign up for and nothing to buy, and it still took 1,110 points and 430 comments on Hacker News in a day.
What it looks like
A little fake browser sits at the top of the page showing two buttons, "Add to Cart" in black and "Cancel" in white. Underneath you pick from three ways of phrasing your instruction and hit send. It then works, visibly: reads a component file, searches the stylesheets, edits the colour definitions. It reports back "Done. Add to Cart is blue." And it is. So is Cancel, because it went and changed the shared colour both buttons were pointing at, and you can see both of them sitting there blue in the fake browser at the top.
How it was made
Not published, and I'd be guessing at the code. What's clearly deliberate is that it doesn't just print a transcript at you, it changes the little preview as it goes, so you watch the mistake happen rather than reading about it. The comments were split, plenty of people said current models don't behave like this any more, which didn't slow it down at all.
What it would take you
A page like this is a day, and it's all writing rather than engineering. Genuinely worth considering for client work: a small interactive thing that makes someone feel a problem beats any amount of copy explaining it. Free to build and free to host.
A one-page rulebook that stops your coding assistant burying the answer
What it is
A short instruction file you drop into Claude Code or Codex that changes the shape of every reply it gives you. House rules for the assistant, basically: lead with the action, number the steps, and drop the "Hope this helps!" at the end.
Why it is useful
The before and after in the repo is the whole pitch. Before, you get a paragraph of throat-clearing with the actual file and line number buried somewhere in the middle. After, you get "Run `npm install jsonwebtoken@latest`, then edit `src/auth.ts:42`", three numbered steps, and one concrete next thing to do. You stop having to reread replies to find the instruction in them. Ten rules total, including cap lists at five items, give time estimates in real minutes rather than "a bit", and no preamble, no recap, no closers.
What it looks like
Installing is one line pasted into your agent, telling it to fetch the skill from the repo and follow the install instructions. After that nothing looks different, the replies just arrive in a different shape: a command or a file path on the first line, then a short numbered list, then a single line telling you what to do next. When it hits an error it says so flatly instead of apologising for three sentences first.
How it was made
The rules themselves are only 140 lines. The part worth stealing is that nearly 9,000 lines across 59 files in that repo are tests. The author wrote sample questions, ran them through his wording, checked whether the replies genuinely came back in the shape he wanted, and kept tuning the wording until they did. Most people write a prompt and hope. He wrote a prompt and then built a marking scheme to grade it against. The rules themselves are loosely adapted from a real ADHD self-help book, The Adult ADHD Tool Kit, reworked for how a machine should answer rather than how a person should plan their day. One oddity worth knowing: the repo keeps a GitHub issue labelled "AI Agora" where the coding agents working on the project are allowed to talk to each other. That does not come along when you install it, since only the skills folder gets copied.
What it would take you
Nothing. It is free, there is no API cost, and the same file works on Claude Code and Codex. The better use is to fork it and rewrite the ten rules as your own, which is an hour rather than an evening. You already keep global rules, so the new idea here is not the rules, it is writing a set of test questions and actually checking that your wording changed the output, instead of assuming it did.
One man joined eleven scientific databases nobody had linked, and got a browsable tree of 2.2 million species
What it is
A website showing every living thing as a tree you can open and close, from kingdom all the way down to individual species. Same idea as a family tree, except the family is all of life on Earth.
Why it is useful
As a thing to use, it is a genuinely lovely way to lose an hour. As a thing to learn from, it is a worked example of the most reusable trick in web building: take public data that already exists, do the tedious joining-up nobody else has bothered with, and the resulting site is something no competitor can quickly copy.
What it looks like
You land on a tree and click a branch to open it. Along the top there is a list of 41 things you can colour the tree by: what an organism eats, where it lives, how long it lives, how high birds fly, how deep fish go, whether it is endangered. Pick one and the whole tree recolours, so patterns jump out that you would never spot in a table. Tabs at the top switch between eleven different versions of the tree, because biologists genuinely disagree about how things are related, and hovering a branch shows you a photo of something in it.
How it was made
All eleven source databases are free public downloads, published by scientists under a licence that only asks for credit. Nobody had reconciled them, because the same creature has different names, different spellings and a different parent in each one. He wrote a nine-step build process that takes roughly 800 GB of raw downloads and grinds it into one linked set where every branch in every version knows what it matches in the other ten. He is careful about a line most people would cross: where a database says it does not know where something belongs, he leaves it there rather than quietly moving it to where he thinks it should go. The visual trick, folding the connecting lines around each other so you can still read the hierarchy when a branch opens, is entirely hand-made and took him a month by itself. He has form, too: he is the person behind ptable.com, the interactive periodic table that has been running since 1997.
What it would take you
The data costs nothing, so the price here is time. A small version, one dataset and one colour overlay, is an evening. The full thing is months. Cloudflare Pages will serve the finished front end for free, because all the grinding happens once on your own Mac and the site itself is just files. The move to copy is the boring middle bit: pick two or three public datasets nobody has joined, do the reconciliation properly, and the design largely suggests itself afterwards.
A checklist for spotting AI writing, taken from the people who read more of it than anyone
What it is
A single text file you hand to a writing assistant so it edits its own draft before it shows you anything. The list of what to catch is not one person's taste. It is Wikipedia's own published guide.
Why it is useful
Most "make this sound human" instructions are somebody's hunch. This one points at a list that Wikipedia's editors built up while reviewing thousands of AI-written submissions and noting down what kept giving them away, and that stays maintained by those editors without anyone having to rewrite the file.
What it looks like
You give it a draft and ask for a rewrite. It runs quietly and hands back clean text rather than narrating what it changed. What it is looking for: the tacked-on significance clause at the end of a sentence, stock words like delve, tapestry, robust, seamless and game-changer, the "it's not X, it's Y" habit, restating your conclusion back at you, too many em dashes, inventing a debate about something nobody actually disputes, the same four transition words over and over, headers and bullets where plain paragraphs would read better, a promotional lean where none was asked for, and the leftover "I hope this helps!".
How it was made
There is almost no engineering in it, and that is the point. He copied a public, community-maintained list into a file, added instructions on how to apply it, and stopped. The judgement in the write-up is the good part: no single item on the list proves anything on its own, it only works as a combined signal, and a piece with zero em dashes can read every bit as artificial as one stuffed with them. The stated goal is proportion, not elimination.
What it would take you
Free, and it is only a text file, so it works with Claude Code, Codex or anything else that reads instructions. It is a small project, 26 stars, so treat it as a starting list rather than a finished tool. The idea worth taking is aiming your own rules at a public source that other people keep updated, so the list ages on its own instead of going stale the day you write it.
A 105 GB model running on a Mac that hasn't got 105 GB
What it is
A free tool for Apple Silicon Macs that runs a very large AI model on your own machine, on hardware with nowhere near enough memory to hold it. It keeps most of the model sitting on the SSD and pulls in only the pieces it needs for each word.
Why it is useful
Running a big model locally normally means buying a machine large enough to fit it in memory, which is where the money goes. This swaps that requirement for free disk space, which is far cheaper. Nothing leaves the Mac, there is no account and no per-word bill, and once the download is done it works with the internet off entirely.
What it looks like
One line pasted into Terminal installs it. After that you can chat with it in the terminal, ask it about a picture, or point an app at it, because it pretends to be Ollama (the usual way a local model presents itself), so anything already set up to talk to a local model works with no changes. Speeds measured on real machines, in tokens per second, a token being a few characters: about 12 on a 48 GB MacBook Pro, 6 on a 32 GB Air, 21 to 22 on a 128 GB Max, and a fairly painful 1.4 on a 16 GB Mac mini.
How it was made
Written in Swift, using Apple's own on-device machine learning framework. The trick is knowing what to keep in memory. This particular model is built as a big collection of specialists, and only a few of them get consulted for any given word, so most of the file is dead weight most of the time. Slotstream leaves the specialists on disk and streams in the handful it needs, then throws them out again. The README is refreshingly honest about the catch: starting a reply is slow, because it has to read your whole question and the conversation so far before it can begin, and a long prompt can sit there for minutes before the first word appears.
What it would take you
Free and MIT licensed. You need an Apple Silicon Mac, macOS 14 or later, and about 110 GB of free SSD space for the model download. Worth knowing before you commit the disk space: the author is building a paid app on top of this, but he has said the command line tool, the interfaces and the code library stay usable on their own.
A small browser game. A three-line haiku gets cut into jigsaw pieces and scattered, and you drag them back into place. That is the entire thing.
Why it is useful
It is not useful, and that is why it is here. It is a reminder that a small, finished, pretty thing with one idea in it still gets 112 points on Hacker News and a page of people saying they enjoyed it. Not everything has to be a product.
What it looks like
Pieces sitting loose around a board. You drag one near where you think it goes and it snaps to its neighbour when you are close enough, so the poem assembles a fragment at a time and you read it as it comes together. The one complaint in the comments is worth noting if you build anything similar: the borders drawn on each piece cover the very edge detail people need to match pieces up, and several players wanted to park a piece anywhere on the board to test a match rather than have it spring back.
How it was made
The interesting part is a decision, not code. He built it for his existing puzzles site, The Daily Baffle, then looked at the finished thing and decided it did not fit the tone of everything else there, which is deliberately hard, whereas this one he wanted to be calm and pretty. So he put it on its own domain instead. He also says straight out that it was not a highly original idea and did not need to be.
What it would take you
An evening. It is drag, snap, a grid and a poem, with no server involved at all, so Cloudflare Pages hosts it for nothing. The habit worth copying is his: when a thing you have made does not fit the site you made it for, give it its own address rather than forcing it in or throwing it away.
He joined two council datasets nobody had linked before, and watched a whole city grow from 1880 to now
What it is
An interactive 3D map of Los Angeles that fills itself in, building by building, from 1880 to today, coloured by the decade each one went up.
Why it is useful
It is not solving a problem so much as proving what a solo coder can now do with data that was already public but scattered and badly formatted. The technique behind it (joining two open datasets nobody had combined, then asking Claude to visualise the result) is the useful bit, and it works for any council, any city, any archive.
What it looks like
You land on a dark 3D map and hit play. Buildings pop into existence in waves as the year counter climbs, coloured by decade, until 1.1 million of them are standing. You can hover any building for its address, year built and height, switch to a colour-by-height view and fly straight to downtown, or zoom in until the boxes turn into actual building shapes. Zoomed out, it draws a coarse grid instead of a million individual shapes, or it would grind to a halt.
How it was made
The data existed but was a mess: LA County's 2020 laser-scan of every building's height and footprint (called lidar, a way of mapping height by bouncing lasers off the ground from a plane) lived in one place, and the county's own year-built records lived in another, hosted on different systems that don't talk to each other. He wrote code to pull both, then joined them into a single file using DuckDB, a free database tool built for exactly this kind of one-off "match these two enormous spreadsheets by location" job. That file got turned into map tiles with tippecanoe (an open-source tool that carves a huge dataset into small chunks a map can load quickly) and rendered with MapLibre, a free alternative to Google's mapping library that can draw buildings as solid 3D shapes rather than flat outlines. The whole thing sits as plain files with no server behind it at all. The part he couldn't do himself, the flying camera, the timeline, the hover labels, he handed to Claude once the data was ready, and says it "blew his mind" what it did with it.
What it would take you
Every piece here is free and already in your toolkit: Claude Code for the build, Cloudflare R2 for the free static hosting, DuckDB and tippecanoe are open-source downloads. The real cost is time, not money, and it is mostly spent before Claude gets involved: finding a council or archive with usable open data and wrangling it into shape, since every public body publishes its records differently. Call it a weekend for the data, then an afternoon with Claude for the map itself.
A free control panel that stops Claude Code's subagents losing their work when a terminal closes
What it is
A small local tool that sits between you and Claude Code (or Codex) and keeps a proper record of every subagent you send off to do a job, so nothing gets lost.
Why it is useful
Anyone running several agents at once knows the failure mode: you close a terminal, or a session drops, and you have no idea what that subagent actually finished or where it left off. This gives every subagent job a durable record that survives a closed terminal or a crashed session, and hands back the complete result rather than a half-finished guess.
What it looks like
You install it and open a web page on your own machine. It shows your "team" of agents laid out on a canvas: who is running, what they are waiting on, and what came back when they finished. You can watch a job live, see each step's result as it lands, and if your terminal closes mid-task, reopen the page later and the record is still sitting there waiting for you.
How it was made
It is a small Python web app plus a background service (it keeps running quietly using your Mac's own built-in scheduler, the same mechanism that lets a printer keep working after you've closed its settings window). Everything it tracks, who did what, what was returned, what still needs your input, gets written to a plain local database file rather than living only inside a chat transcript. Nothing leaves your machine.
What it would take you
Free and open source (MIT licence), installs with one command the way you'd install any small Python tool, and runs entirely on your own Mac with no account or subscription needed. It slots straight into the way Ryan already works with Claude Code's subagents, so this is an evening trying it out rather than a weekend building it, since it is already built.
A browser game where the enemies are cookie banners, run off a to-do list two different AI agents both work from
What it is
A small, free browser game called Ad Nauseam where you fight the things that ruin the modern web: cookie consent bars, paywalls, tracking pixels, autoplay video and a boss called The Algorithm.
Why it is useful
The game is a joke worth playing for two minutes, but it earns its place here for the working method behind it, which is fully readable in public. The developer runs the whole project through GitHub's built-in to-do list, and writes every single job as a brief an agent can pick up and finish without asking follow-up questions. That is the same discipline Ryan already uses when handing work to subagents, except here you can open every ticket and read exactly how it was worded.
What it looks like
It plays in a browser with nothing to install. You get a top-down arena on a soft, muted pixel-art background, deliberately kept low contrast so the glowing enemies still read clearly on top of it. Each enemy is a familiar web annoyance drawn as a monster: a consent bar that walls you in, a locked paywall box, a blinking crosshair for the tracking pixel. The same code is also wrapped up as a phone app.
How it was made
The clever bit is the paperwork, not the game engine. Every task lives as a numbered ticket on GitHub, and each one is written in the same shape: the question being asked, the constraints, and a bolded "Done:" line saying exactly what finished looks like. One of them ends "Nate eyeballs and ships", which is the whole quality gate stated in four words. Tickets carry labels that decide who picks them up, `ready-for-agent` or `ready-for-human`, so the agent works the queue on its own and only hands back the ones that genuinely need a person. The repo also carries a short rules file telling any agent where the project's standards live, and there is config for both Codex and Claude Code sitting side by side, so the same ticket queue gets worked by whichever one is running that day.
What it would take you
Nothing beyond what's already on the machine. The game itself is TypeScript hosted free on GitHub Pages, and both agents driving it are ones Ryan pays for already. The transferable part costs nothing at all: writing tickets with an explicit "done" line, and labelling which ones an agent may take unsupervised, works just as well on a client site as on a game.
An 855-byte script that makes a plain HTML page update itself, no framework needed
What it is
A tiny JavaScript library called Mador. You point it at a bit of state (a number, a flag, whatever) and it keeps the matching bits of the page in sync automatically.
Why it is useful
Ryan's sites are single-file vanilla HTML, CSS and JS on purpose, no React, no build step. This gives him live counters, toggles and simple forms that update without a page reload, while keeping that exact approach.
What it looks like
you add one script tag from a CDN, write a couple of lines saying "when this changes, update that element by its CSS selector," and it just works. No components, no templates, nothing to compile.
How it was made
one developer built it over a weekend using a JavaScript feature called a Proxy, which lets code watch a plain object and notice the moment any of its values change. Instead of wiring that up to custom components, like most frameworks do, he wired it straight to ordinary CSS selectors, so it drops into markup that already exists. The whole thing is under a thousand bytes minified.
What it would take you
free and instant. Drop the CDN link into any existing site and start using it, no rebuild required.
A shared notebook so your AI coding tools stop forgetting your project between sessions
What it is
A small local database, called Engrim, that Claude Code, Google's Antigravity and a few other AI coding tools can all read from and write to on the same project.
Why it is useful
clear a Claude Code session and the AI loses every decision you made together, the constraints you gave it, all of it. Engrim keeps a running memory of the important bits outside the chat itself, so starting fresh does not mean starting from zero. It works across tools too, so switching from Claude Code to agy on the same project does not lose anything either.
What it looks like
you install it once, and from then on the tools quietly save key facts and decisions as you work. Next session, before you have typed a word, it has already loaded the relevant memories back in.
How it was made
the developer built it on SQLite, a small file-based database, and combined two search methods so it pulls back the right memory rather than everything: plain keyword search, and a lighter form of "meaning" search using small numerical fingerprints of each memory's content. It hooks into the startup and shutdown moments each tool already exposes, so there is nothing to babysit.
What it would take you
free, open source, one `pip install`. Works with Claude Code and agy specifically, both of which Ryan already runs daily.
A browser add-on that quietly removes AI slop from your YouTube feed
What it is
A Safari extension called Weedout. It hides any video YouTube itself has labelled "Made with AI," from the main feed, search, related videos and Shorts.
Why it is useful
this is exactly the itch behind this digest, wanting the good stuff people actually made rather than the flood of AI filler that now clogs YouTube's recommendations.
What it looks like
install it, and labelled AI videos simply stop appearing. No settings to fuss with, no filtering by keyword, it just reads the same "AI-generated" tag YouTube already shows and acts on it.
How it was made
the developer deliberately used YouTube's own disclosure label rather than trying to build an AI-detector, since those are unreliable and easy to fool. Everything runs locally on the device, nothing is sent anywhere. Source is public on GitHub for anyone who wants to adapt it, though the author isn't taking pull requests, forking is the intended route.
What it would take you
this is a Tampermonkey userscript in miniature, matching an element by its label and hiding it, which is squarely inside what Ryan already does with his tampermonkey skill. An evening's build, free.
A chess clock for your day, so one job can't quietly eat all your time
What it is
An iPhone and Apple Watch app called OwnTime. You name a few priorities, give each a daily time budget, and only one "clock" runs at a time.
Why it is useful
for anyone splitting a day between client work, a photography shoot and admin, this stops one thing swallowing the whole afternoon by accident. Start a new priority and it automatically pauses whichever one was running.
What it looks like
you tap a priority to start its clock, tap another to switch, and when a budget runs out an actual alarm goes off, not a notification you can miss while absorbed in something. Everything resets at midnight, and the full history can be exported as a plain database file if you want to look at the numbers yourself.
How it was made
the developer built it natively for iPhone and Watch specifically so it could trigger Apple's real alarm system rather than a normal notification, which he felt was too easy to ignore. There's no server and no account, all the data stays on the device.
What it would take you
the native app needs Xcode and Swift, which sits outside Ryan's usual stack. But the idea itself, mutually exclusive countdown timers with a hard alarm, translates cleanly into a small web app on Cloudflare Pages using JavaScript timers and the browser's own notification permission. An evening's build, minus the watch face and voice control.
Quiet one today. Reddit, Hacker News and Digg were mostly model launches (GLM-5.3, GPT-6-Astra, Muse Glimmer) and opinion threads (which harness do you use, is Astra worth it), not actual builds. Two of the strongest signals were repeats of things already covered here (the GLM/BlenderMCP penthouse from 5 Sep, the vibecoded Minecraft clone from 31 Aug). A broader sweep of solo-founder and side-project boards turned up nothing with real engagement or enough detail to explain how it was built, and the one genuinely good find, a solo dev shipping a full social media scheduling tool in three weeks with Claude and Codex, turned out to be four months old rather than a fresh one. Nothing here worth padding the list with. Back tomorrow.
5 Sep 2026
A dumber, cheaper model was quietly reading your files for you
What it is
A way of cutting an AI coding assistant's running costs by around 90%, by automatically handing the boring parts of its job (reading big files, writing routine code) to a cheap model, and keeping the expensive one only for actual thinking.
Why it is useful
It goes straight at the exact thing that burns through Claude usage without ever being "hard" work: an agent reading five files to answer one question, or writing a test file that's basically a copy of the twenty sitting next to it. Almost pure cost, almost no reasoning.
What it looks like
Two rules sit and watch everything the coding agent does. The moment it tries to read a file over 350 lines, the rule stops it and hands the job to a cheap secondary model instead, which reads the whole thing and hands back a tight list of bullet points rather than the raw text. Same again for repetitive code: a short spec plus one example file goes to the cheap model, which writes the actual file straight to disk. The expensive model never even sees the generated code, only the instruction and the short result.
How it was made
Spotify built this on their own internal AI platform, but the mechanism underneath is something you already have for free: Claude Code "hooks", a way to make it run a check before it takes an action, in this case before every file read. The hook checks the file's size, and if it's too big, blocks the read and redirects the work to a cheaper model. The instruction given to that cheap model matters a lot too: told explicitly to answer only in bullet points, no preamble, so the expensive model doesn't waste tokens wading through chatty prose.
What it would take you
Spotify's own platform isn't something you can sign up for, but you don't need it. Claude Code already has hooks built in, and you already have a free cheap-model worker sitting right there in agy, your Gemini access. This is a genuinely rare case where every piece is already in your hands: an evening to write one hook that catches oversized file reads and reroutes them to agy with a "bullet points only" instruction, automating almost exactly what your own model-routing rules already ask you to do by hand.
A free tool that builds a 3D room from one detailed paragraph
What it is
An open-source connector that lets an AI assistant control Blender, the free 3D modelling program, well enough to build a whole furnished room from a written description, no manual modelling at all.
Why it is useful
A way to generate room mockups, staged product scenes or interior walkthroughs from a written brief instead of paying a render artist or learning Blender by hand, useful for photography and web-design pitches alike.
What it looks like
With Blender open and the connector running, you describe the room as a single detailed prompt: room dimensions, ceiling height, stair proportions, window spacing, material properties for the glass and the marble. The AI agent then builds it live inside the actual 3D scene, placing walls, then a stairwell and mezzanine floor, then furniture, right down to small details nobody asked for, like the individual books on a shelf.
How it was made
An open-source project called BlenderMCP hands Blender's own modelling commands to an AI agent as a set of callable tools, the same connector technique ("MCP") that already lets Claude read and edit files on your own machine, just pointed at Blender instead. The person behind this post rented four to six top-tier GPUs to run a Chinese open-source model locally, purely to avoid paying for a hosted one. The part that actually mattered wasn't the expensive hardware: his first vague prompts produced what he called "3D goo", and it only became a real room once he specified hard numbers, ceiling height, stair rise, window mullion spacing, material roughness.
What it would take you
Blender is free and BlenderMCP is a free download; you don't need rented GPUs at all; Claude, already on your Max plan, can play the same role the expensive local model played here through that same connector pattern. A weekend to get BlenderMCP talking to Claude, then the real work is writing prompts as dimensioned as an architect's brief rather than a vague wish.
He couldn't get Google Ads to work for his own shop, so he built the missing "write" button
What it is
A plug-in that lets an AI assistant actually change your Google Ads account, not just read it. Google's own version can only look at your numbers; this one can also pause a wasteful ad, adjust a budget, or set up a new campaign, because you told it to in plain English.
Why it is useful
He and his co-founder were burning money on Google Ads for their Shopify shop (one conversion cost them £120) and couldn't afford an agency. This is the gap that leaves: Google Ads is famously fiddly to run well, and Ryan already handles it for Padharo and the Mustang Group sites by hand.
What it looks like
You connect it once, then talk to whichever AI assistant you already use. Ask it to find where the budget is being wasted, and it pulls the real numbers and tells you. Ask it to fix a campaign, and it actually makes the change, rather than just explaining what you should click. It also reaches into Google Analytics and Tag Manager, so it can join up "which ad" with "did they actually convert."
How it was made
The clever part is narrow on purpose. Google publishes an official connector for AI assistants, but it's read-only, presumably so nobody's agent accidentally torches a client's ad spend. He built his own version of that same connector with write access added back in, hosted so it stays logged into the ad account permanently rather than needing a fresh login each time. Everything else, the actual thinking about what to change, is left to whichever AI the user brings.
What it would take you
This is squarely a Claude Code build: Google Ads has a proper, free API, and a "read the account, propose changes, apply the ones I approve" tool is code, not a subscription. You already have the equivalent read-only version through your gws-ops connector for Search Console and Analytics; this is the same idea with a write step added, scoped tightly (propose first, apply on confirmation) given it's real ad spend. A focused weekend, not an evening.
He got sick of screenshotting website flaws one at a time, so he built a tool that just listens
What it is
A screen recorder for reviewing a website or app. You hit record, look at the page, and say out loud what's wrong as you spot it. Stop recording, and it hands you a folder: a written summary of everything you said, each point matched to the exact screenshot of what you were looking at when you said it.
Why it is useful
It replaces the loop everyone doing AI-built frontend work ends up in: screenshot the bug, paste it into the chat, type out what's wrong, go back, repeat, for every single thing that's slightly off. Spotting a dozen small issues on a page takes seconds; typing them all out one by one is what actually eats the time. That's exactly the "last 10%" of frontend work Ryan's own visual-qc process spends its time on.
What it looks like
You open the tool, hit record, and just talk while you scroll: "that button's too close to the edge," "this doesn't wrap right on mobile," "the spacing here is off." When you stop, you get a small markdown file (what you said, organised) plus only the screenshots that go with something you flagged, not the whole recording. You drag that folder into Claude Code and tell it to work through the list.
How it was made
The insight worth stealing is what he left out. He first considered handing the AI everything, the full screen recording, every frame, and found that was worse: more context isn't automatically more useful, it's mostly noise the agent has to wade through. What actually matters is just two things paired together: what you said, and what was on screen at that exact moment. Building that pairing (matching a spoken timestamp to the right screenshot) was the whole project; the rest is a fairly ordinary screen-recorder-plus-speech-to-text app, which he built largely by asking Claude Code to build it, including using an early version of the tool to review itself.
What it would take you
Genuinely buildable with what you already have: your Mac can already record its own screen, free speech-to-text tools exist, and Claude Code can write the "match this spoken timestamp to that screenshot" logic and package the output as a markdown file. A weekend project, and afterwards it costs nothing to run since there's no subscription involved, unlike the version he's selling.
He plugged a £15 gadget into his Mac and had Claude Code work out what it was and write its firmware
What it is
A demo of turning cheap, unlabelled circuit boards (the kind hobbyists use to build little gadgets, £15 to £50 each) into working devices, by having an AI write the low-level code that runs directly on the chip, with no manuals or setup involved.
Why it is useful
Programming this kind of tiny board normally means reading a datasheet, installing a specific toolchain, and wrestling with libraries built for one exact chip variant, the kind of fiddly setup that puts most people off ever trying. This skips all of it: you don't need to already know what board you're holding.
What it looks like
He plugged one board at a time into his Mac's USB port and told Claude Code to figure out what it was. It read the connected device, worked out the exact chip and its pin layout (which physical pin does what), and then wrote and uploaded working code for it, a small screen that displays information on one board, other features on the others. No Arduino software, no board-specific tutorial.
How it was made
The trick isn't the AI writing clever code, it's skipping the research phase entirely. Normally you'd spend the first hour just identifying which exact chip you've got and hunting down its pin map before writing a line of code. Here, that identification step is handed to the agent too: it reads what's plugged in, works out the specifics itself, and only then starts writing.
What it would take you
ESP32 boards (the chip family used here) cost roughly £15 to £40 each on Amazon, and Claude Code is the only other thing this needs. A genuinely doable evening project, and a good one to try if you want a physical, on-your-desk thing to point at, rather than another website.
A search engine that skips the SEO sludge and only shows you what people actually made
What it is
A personal search engine, but tuned to surface the small, human internet: portfolios, zines, one-person software, art projects, instead of corporate homepages and affiliate blogs. One person built the whole thing over a long weekend.
Why it is useful
It solves the exact "every search I care about drowns under a foot of SEO sludge" problem. And it's cheap: the entire weekend, including renting a graphics card by the hour to run the AI, cost him about £8.
What it looks like
A plain search box. Type a word or two and you get a scrollable list of small, independent sites, each with a one-line summary and a tag (portfolio, zine, software, nonprofit) that an AI wrote after reading the page. He also built himself a little dashboard so he could watch the index fill up in real time: how many pages catalogued, and whether the last hour skewed towards corporate sites or the interesting stuff.
How it was made
The clever part isn't the AI, it's the plumbing he built around it. A small program (a crawler) visits a page, grabs the text and any links off it. A second program hands that text to a small AI model running on a rented computer, which reads it and writes back a short description, a category and some tags. The moment that's done, the original page text gets thrown away, so nothing piles up. Left alone, a crawler like this fills itself with corporate homepages, because that's what most links point to, so he steered it instead of blocking anything: links found on "interesting" pages get followed first, links on "boring" pages get followed last. He also had to cap how many pages he'd take from any single big blogging platform (Tumblr would have swallowed the whole index otherwise), and built a second small watcher that samples suspicious clusters of pages and asks the AI "block, keep, or not sure" so spam farms don't flood things while he's asleep. Renting the graphics card cost about 30p an hour and got through 600 pages a minute; the whole 560,000-page index came in under £10.
What it would take you
Claude Code could build the crawler and the small AI-summarising step for you directly, and the results would happily sit in Cloudflare D1 or R2, which you already have. The one real cost is renting a GPU by the hour to run a small AI model at scale, and his own numbers suggest a few pounds buys a hundred thousand pages. Budget a proper weekend rather than an evening, most of the time goes on watching what comes in and nudging the settings, not writing code.
A public shame-file for every AI coding disaster, so you don't have to repeat one yourself
What it is
A website that collects real, sourced stories of AI coding agents going wrong, deleting files, leaking passwords, running up huge bills, and turns them into a searchable, source-linked list with the lesson each one taught.
Why it is useful
You use an agent on your own machine every day. This is a free way to check "what's the known list of ways this goes wrong" before it happens to you, rather than finding out the hard way.
What it looks like
A plain page with a running tally at the top: how many incidents logged, how many different tools implicated, what share were preventable. Below that, a filterable table: which agent, what it did, how bad. Click into any entry and you get the write-up plus a link back to wherever it was first reported, so you can check it's genuine rather than a rumour. At the bottom there's a short "how to avoid this" list: run agents in a sandboxed folder rather than your real desktop, never leave one holding your real passwords, and always get shown a destructive action before it happens.
How it was made
Deliberately simple. There's no database humming away anywhere, the entire dataset is one plain text file (in a format called JSON) sitting on the site. To add an incident, you write it up somewhere public first, your own blog or a forum post, so it can be checked, then you file it as a request on the project's GitHub page, and the site's owner folds it into that one file. It's a neat trick for any small crowdsourced directory: rather than building your own sign-ups and moderation queue, you borrow a system that already has spam protection and a paper trail built in, GitHub's own issue tracker, and use that as your "add an entry" form.
What it would take you
Free, and a genuinely easy weekend build. One static page, one JSON file to hold the data, hosted on Cloudflare Pages, which you already use. The GitHub-issue-as-submission-form trick would work for any small directory or reference site you want other people to help fill in, a list of good local suppliers, a photography kit wishlist people can suggest additions to, whatever.
He let an AI run alone for 12 hours and it designed, rendered and refined an entire room by itself
What it is
A demo where an AI model was set loose in an empty folder with one detailed brief and left completely alone for 12 hours. By the end it had built a full 3D interior, a rooftop skyline bar, in Blender (the free 3D design and animation program), lit and rendered like a proper visualisation.
Why it is useful
It's a genuine look at how far "describe it, then let the AI iterate on its own" can go for visual work, the kind of thing that would otherwise need a 3D artist. And crucially, this isn't locked to one company's model: Anthropic's own Fable 5.1 (the model behind Claude, which you already pay for) has been shown doing the identical trick, one Anthropic staffer fed it a photo of a plot of land and Fable designed a house for it, rendered it, and produced a cinematic walkthrough video, unprompted beyond the brief.
What it looks like
Nothing to click on, this was one continuous unattended run. The team gave the model a long written brief (what the space should feel like, sixteen fixed camera angles they wanted covered, the mood and materials) and pointed it at Blender. From there it wrote its own code, rendered a still image, looked at that image, decided what was wrong with it, rewrote its code, and rendered again, on a loop, for twelve hours, with nobody watching. The end result is a bar scene with skyline views that looks like a proper architectural visualisation, not a rough AI sketch.
How it was made
The trick isn't clever prompting for "how" to build the scene, it's spending the effort up front on describing "what" a good result should look like, in as much visual detail as you can manage: materials, lighting mood, exact camera angles, before you ever ask it to start. Once that brief exists, the model handles the modelling itself. The loop that makes it work is: write code, render an image, look at the image, critique it, adjust the code, repeat, which is the same render-and-look-again pattern a human 3D artist uses, just run by the AI on itself with nobody watching.
What it would take you
Free. Blender itself costs nothing, and there's an existing open-source connector (BlenderMCP) that lets Claude control Blender directly rather than needing anyone to run a separate, unfamiliar model. The one honest catch: the 12-hour unattended version in the demo burned around 100 million tokens, more than you'd want to spend on a whole week of ordinary Claude Max use, so treat this as something to try in a shorter, supervised burst (an hour or two, checking in occasionally) rather than copying the "walk away for half a day" version exactly.