This is our new home for all things related to building apps, websites, tools, games, and other projects with Claude and Claude Code. We're excited to have you join us!
What to Post Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your projects, demos, screenshots, prompts, workflows, experiments, coding tips, build processes, and questions about what you're building with Claude and Claude Code.
Share anything you've built with Claude, including:
🌐 Websites and web apps
📱 AI-powered apps and tools
💻 Projects built with Claude Code
🎮 Games and creative projects
🤖 Agents and automations
🧪 Experiments and prototypes
💡 Interesting prompts and workflows
📊 Benchmarks and build results
Community Vibe We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.
How to Get Started
Introduce yourself in the comments below.
Post something today! Even a simple project or question can spark a great conversation.
If you know someone who would love this community, invite them to join.
Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.
Thanks for being part of the very first wave. Together, let's make r/BuiltWithClaude amazing.
With the recent news about Voyager passing the 1 light day mark I wondered about where in space certain events would have travelled to and ended up creating this visualisation site that will allow you to pick a time and place on Earth and let you travel to the next star to receive it with over 12,578 visitable stars.
I turned music into a place you can stand in. Audio Probe XR is a free, open-source listening room for the Quest 3: seventeen visual worlds, all choreographed to one synchronized audio clock. Every kick, bass note, chord change, sung word and drop drives the scene in real time — and the same moment in a song always reconstructs the same view, so seeking around lands you exactly where you left off.
How it works: each track is analyzed offline into a timeline (beats, sections, drum hits, bass and lead transcription, energy curves). At runtime one audio clock drives everything — shaders, lights, formations, camera-facing staging — through a deterministic choreographer. No post-processing passes, no bloom textures: all the glow is faked in the materials so it holds frame rate on the Quest 3. Two quality tiers (Detail / Ultra), seventeen worlds.
A few of the worlds: a thunderhead where the drums are lightning, a brass orrery that realigns on phrase boundaries, a jellyfish deep-sea scene, a caldera where every kick throws a lava bomb, a rooftop over a rain-soaked megacity, floating islands at golden hour, and a black hole with a gravitationally lensed disk (one analytic shader, no ray marching).
Full transparency — this was made entirely with AI: the app was written entirely with Claude Code running Opus 5.5 (I wrote the direction, the reviews and the taste calls; the model wrote the code), and all the music was generated with Suno. Everything is in the repo, including the analysis pipeline, so you can see exactly how it's built.
It's free, no ads, no accounts, no data collection. Works with controllers and hand tracking. Photosensitivity warning: it flashes and strobes with the music — details in the README.
Feedback welcome — especially world ideas for the next batch and frame-rate reports from your headset (Detail vs Ultra).
I'm a solo developer and I built Aristodoc, a document management app for Windows, almost entirely in collaboration with Claude. It went from first commit to Microsoft Store certification in about five weeks. Here's what it does and how Claude helped.
What Aristodoc does
The problem: You have thousands of documents scattered across folders — tax notices named "Scan_0012.pdf" in "New folder (3)", invoices from five years ago, scanned letters with no searchable text. Good luck finding anything.
Aristodoc reads all your documents (PDFs, Word, scans, photos of letters, emails) and makes them findable:
Full-text search across every page, including scanned documents via OCR (using Windows' built-in text recognition — no cloud API)
Semantic search with a local AI model — search "money from the state for children" and it finds the child benefit notice, even if those exact words aren't in it. Uses multilingual-e5-small running locally via ONNX Runtime. No data ever leaves your PC.
A visual "map" of similar documents — documents are laid out by similarity so you can see clusters and relationships at a glance
Deadline extraction — payment deadlines, objection periods, cancellation dates are automatically pulled from letters and shown in one place
Smart filing suggestions — "this invoice probably belongs in your Tax/2024 folder" with a reason
Rename suggestions — turns "Scan_0047.pdf" into "2025-03_Payslip"
Everything runs 100% locally. No account, no cloud, no telemetry. The app doesn't even have network access except for an optional IMAP mailbox connection.
The tech stack
Python 3.13 for the backend
pywebview with Edge WebView2 for the UI (HTML/JS/CSS, no framework)
ONNX Runtime for the local embedding model (semantic search + document map)
SQLite with FTS5 for full-text indexing
pdfium for PDF rendering
Windows OCR for text recognition
Packaged as an MSIX for the Microsoft Store — no PyInstaller, custom packaging
~21k lines of Python, ~12k lines of HTML/JS/CSS, ~15k lines of tests, ~10k lines of dev tooling. All in 554 commits over 5 weeks.
How Claude helped
Claude was involved in essentially every part of the project:
Architecture decisions: The similarity map layout, the force-directed graph for the animated card, the embedding pipeline design, the rule-based deadline extraction — all discussed and iterated with Claude.
Feature implementation: From the OCR pipeline to the semantic search to the scan station (phone camera → straightened, searchable PDF), Claude wrote most of the first drafts and helped refine them.
Bilingual support: The app is in German and English. Claude helped design the translation system (t("deutscher Text") with a JSON dictionary), wrote English rules for deadline/amount extraction (different patterns for US vs. UK dates, currencies, tax forms), and translated the entire help system.
Testing: ~15k lines of tests including integration tests on sample documents, a "quiet test" that checks the app doesn't burn CPU in idle, benchmark suites for filing accuracy, name suggestions, and semantic search quality.
Microsoft Store certification: Claude helped build the MSIX packaging pipeline, debug certification failures (like the onnxruntime missing MSVC runtime issue), and prepare store listings in two languages.
Coordination: For larger features, Claude sessions would coordinate — a central session delegating work to specialized sessions, each with their own worktree.
The workflow is essentially: I describe what I want, we discuss the approach, Claude implements it, I test it in the real app with real documents, we iterate. For measurement-driven features (filing suggestions, name suggestions, deadline extraction), there are benchmark scripts that give hard numbers — Claude can't just claim something works, the accuracy has to go up.
Some things I learned
Claude is remarkably good at "boring" pattern matching work — writing regex-heavy rules for extracting dates, amounts, and deadlines from German bureaucratic letters, then adapting them for English. The kind of work that's tedious for humans but needs domain knowledge.
Having a thoroughCLAUDE.mdmatters enormously. Mine is basically a project handbook — architecture map, file purposes, how to run tests, how to build, what not to touch. New sessions can orient themselves without exploring randomly.
Measurement scripts are essential. When Claude changes the filing suggestion algorithm, I don't review 500 lines of code — I run the benchmark and check if accuracy went up. Same for name suggestions, semantic search, deadline extraction. Numbers don't lie.
The "map" of documents is the most unique feature and also the hardest to get right. It uses t-SNE on the embedding vectors, then a force-directed layout to animate transitions. Claude iterated on this many times with me.
I've been building Elsewise, a decision-mapping tool, with Claude.
The idea came from a problem I kept running into myself. I'd spend days thinking about a decision, make pros and cons lists, talk to people, ask ChatGPT, and end up exactly where I started.
I realised I didn't need more arguments. I needed a different way to look at the decision.
What it does
You describe a decision you're stuck on. Elsewise looks at it through three lenses (mental models like margin of safety, game theory and regret over time) and finds where they disagree.
Then it identifies the crux: the one question your decision actually hinges on.
For example, for someone weighing a two-year MBA, it came back with:
"Is what keeps you stuck a missing credential, or a missing opening that no degree would create?"
It doesn't tell you what to do. It helps you see what you're really deciding.
How Claude fits in
I used Claude and Claude Code throughout, from shaping the product and writing specs to implementing and iterating:
Model per stage. Haiku handles intake, lens selection, perspectives and quality checks; Sonnet writes the crux.
A critic that rejects generic output. Every card is checked for specificity, distinctness and whether it's avoiding prescriptive advice. One slow run turned out to be a single card failing that check three times. I changed the retry logic to swap in a different lens after two failures. That, along with moving the critic to Haiku, cut map generation time from about 2 minutes to around 70 seconds.
Claude as a product critic. I had Claude review the live app, then had two other models debate its findings. That debate changed how lenses are selected.
It's still evolving. The hardest part is making it genuinely more useful than asking a chatbot, rather than becoming another AI wrapper.
I'd love feedback from other Claude builders. Does the crux feel like something you wouldn't get from a well-prompted chat? And how are you handling critic or retry loops in your own pipelines?
I always start courses and never finish them. YouTube playlists, Udemy, PDF books. A week in, I stop, and nobody notices.
So I built inPace with Claude Code. It's a study app that's free, open source (MIT), and runs on Windows, Mac, Linux and Android. No account, no ads, everything stays on your device.
The part I'm most excited about is the open course library
- 52 free courses and 20 learning paths right now: Python, JavaScript, C#, Git, GitHub Actions, Docker, machine learning, system design, data analytics, and English, German and Spanish for Arabic speakers
- Lessons are written in full, with optional videos from freeCodeCamp and Harvard on top
- Every module ends with real work: a task, an explanation in your own words, and a quiz
- Anyone can add a course or a learning path. You make it in the app (by hand, from a folder of videos, or with Claude), publish it, a bot checks it on GitHub in a few minutes, and then anyone can add it with one tap
- Courses are signed with the author's key, so only you can update yours
What else it does
- Put any course in one place: a folder of videos, a PDF book, a YouTube playlist, or a course you're taking somewhere else
- Pick a friend or mentor as your "checker". You send them milestones with your proof and they approve them. Milestones are signed, so you can't fake them
- It remembers the exact second of a video and the page of a book, and you can take notes on any line
- Reminders, races with friends, a learning record for your CV, and a turtle called Tempo who grows a garden while you study
How Claude helped
- Claude Code was my pair programmer for the whole thing: the app, the Android version, the release pipeline and the library bot. I decided what to build and how it should feel, Claude wrote most of the code with me, and I tested every change
- Every feature came with tests. There are 237 now, and they run on Windows, Mac and Linux on every push
- Claude also wrote many of the library courses. I made it run every code example and check every video link and fact
- "Make a course with AI" in the app gives you a prompt to paste into Claude. You get a full course with lessons, tasks and quizzes, with no API key and no cost. And then you can share it with everyone
It's my first post here. If you make a course with Claude, please share it in the library, I'd love to see what people build. And any feedback is welcome 🙏
I’ve only recently started building stuff with Claude, and when the new custom themes came out I wanted to see how far I could push it. So I made a little cyberpunk mod for the desktop app.
It’s 7 themes. Each one puts an animated pixel-art scene behind your chat and recolours the whole app to match it.
Safety, since it’s a plugin: it only changes how the app looks. No network, no file access, and it doesn’t touch your chats. The only thing it saves is which theme you picked. The scenes are plain SVG with no scripts, and it’s all open source if you want to check.
It only works in the Code tab of the desktop app (not the chat app, terminal or mobile).
Would love feedback, or ideas for the next district. And if you want your own version, open the repo in Claude Code and just tell it what you want changed. That’s literally how I made these.
I built Ravenseat, a free and open-source harness and agent orchestrator for Claude Code.
For larger projects. I kick off the queue with my planned tasks, let agents work in parallel for hours and even days, and answer pending questions from my phone a couple of times a day via Claude Code Remote Control. Meanwhile, other tasks keep moving. No more babysitting the agents.
The queue keeps larger projects organized, and each agent starts with fresh context to keep token use down. A few other token saving practices from thorough testing, see repo for details. Once it’s installed, just talk to Claude as usual. Light mode for coding beginners, with project setup help. Advanced mode for experienced devs with total control and many options.
The visual kanban board is optional, great for overviews. Or you can just keep talking to claude code in cli / desktop as usual and never visit it if you dont want to.
I made it myself using claude code. It was gradually born, over many months, out of neccesity in a large project. At a certain project size and scope I desperately needed project and agent management tools and better overall workflows. I extracted it, and thought I would share, since I can't imagine working a larger project without it. I hope it will be helpful for you as well.
Its free, no paid versions / tiers. And MIT licence.
I'm a web developer and wanted a small Mac app that keeps the files I'm moving around and the things I copied a minute ago in one place. I built it with Claude and just released it as Traybox.
How it went: Claude wrote most of the Swift/SwiftUI code, I decided what the app should do, tested every change on my Mac and sent back screenshots of what felt wrong. That loop (try it, show Claude the screenshot, fix it) is how most of the app got built, including the floating panel, file previews, link previews, keyboard paste and the right-click file actions like zip and image convert. Claude also helped with the release side: code signing, notarization and the website.
What it does:
- Clipboard history with source app, link previews and quick text transforms
- A file shelf: preview files, drag them out, AirDrop them or move them to a folder
- Screenshots land on the shelf automatically
- Arrow keys + Return to paste, or Cmd+1 to 9 for the first nine clips
- Everything stays on your Mac, only the license check goes online
It is a paid app, so flagging that up front: $2.99 one time, no subscription, with a free mode. Notarized DMG, macOS 13+.
I wanted to build 3D models of places I've visited, to see their architectural features and to print them. So I built Your Place with Claude Code.
What it does: type an address and it builds the 1, 2 or 4 km around it as a model on the real terrain. Pin a house, share a link to that view, download a poster or an STL. Free, no sign-up, runs in the browser: https://yourplace3d.github.io/3d-city/
How the build went: - Claude Code wrote the app (TypeScript and three.js), the tests and the GitHub Pages deploy. - The STL was the hard part. OpenStreetMap outlines are messy: buildings split at tile edges, terraced houses sharing walls, outlines that cross themselves. Claude wrote the repair steps and checked 38,692 exported shells with trimesh until every one was watertight. - Its cloud sandbox couldn't reach the map servers, so it ran the live checks on GitHub Actions instead, and rendered this video there too, frame by frame from live map data.
It's open source and runs on OpenStreetMap data, which volunteers map by hand, so a model is only as good as the map: big cities are detailed, some villages are sparse, and where a building has no recorded height the app estimates it and tells you how many.
Have fun messing around!
Edit: thanks for all the feedback! Shipped an update a few hours later: the search now finds exact addresses (including numbered avenues) and accepts pasted Google/Apple Maps links, terrain spikes from bad elevation data are gone, and a shared model now invites people to make their own place. Bigger areas, stronger terrain exaggeration and a game-ready export are next.
Sheep is a question and answer game where you score points by answering the same as everyone else. There's daily game where you play against everyone else, with a daily, weekly, monthly leader boards. There's also the option to start your own game room (Flock) and add fiends and family. The host can use the in game questions, edit them or write their own
Over about two weeks I built a product with Claude Code, 153 features. My setup kept growing: every miss became another rule, and the rules file only got bigger. So I turned the process into something that cleans up after itself, and open-sourced it as Morphness.
What it does:
- A Technical Lead agent writes a plan with testable acceptance criteria and waits for my approval.
- A Full-stack agent builds it. A separate QA agent checks every criterion and records evidence, so "done" isn't the builder's word.
- After each feature, a short retro. A rule is only added if it names a miss in that feature it would have caught.
- Every ten features a prune audits the rules: the ones that fired stay, the ones that never fired get questioned and moved out of what every session loads.
From my own records on that project: 88% of features passed QA the first time, 15 prunes, and 4 bugs found after QA had passed. These are my numbers, unaudited, and without a control they show what the process produced, not what it saved.
Windows has Windows Hello and macOS has Touch ID, but Linux has no built-in passkey authenticator. When a site offers “Create a passkey”, Linux users get sent to their phone or a USB security key, and some sites (GitHub, for one) warn about “partial passkey support”.
So I built Linux Passkey. It makes your computer the authenticator:
A website asks to create or use a passkey.
A prompt pops up: “Create a passkey for github.com?”
You confirm with your normal Linux password, or your fingerprint if you use fprintd.
No phone and no hardware key, and the “partial support” warnings go away.
How it works (short version)
passkeyd is a small user service that acts as a CTAP 2.1 authenticator. Browsers see it as a virtual USB security key (through the kernel’s uhid), so it works in every browser even without an extension.
An optional browser extension (Chrome, Brave, Edge, Vivaldi, Firefox) makes it a built-in authenticator, the way Windows Hello is.
Verification goes through polkit, never cached, so it’s your system’s own password/fingerprint dialog.
Private keys are encrypted at rest (AES-256-GCM) under a master key stored in your login keyring.
A GTK4/libadwaita app manages your passkeys. There’s an optional GNOME Shell extension, but it works fine on KDE, Xfce and others.
Install: signed apt, dnf, zypper and pacman repos for Debian/Ubuntu, Fedora/RHEL 10, openSUSE Tumbleweed and Arch:
Being upfront: I vibe-coded a big chunk of this with AI. I’ve tested it as much as I can:
121 automated tests, including end-to-end WebAuthn tests.
CI builds the packages and installs them on Ubuntu, Fedora, openSUSE and Arch.
I’ve used it for real logins on GitHub and webauthn.io.
But it’s v0.1.0, and it handles your logins, so please be skeptical and poke holes in it. Reviews of the crypto, the D-Bus interface and the browser-extension origin checks are especially welcome.
Where I’d love help
🧪 Test it on your distro and desktop. KDE, Fedora, Arch, NixOS, tiling WMs, GNOME 50, fingerprint readers: tell me what breaks.
🦊 Snap and Flatpak browsers. The virtual USB key can be hidden from snap browsers; I’d like to hear how it goes for you.
🛠️ Contribute. Issues, PRs, packaging for more distros, translations. I’d really like to build this with people who know this stack better than I do.
Known limits: passkeys stay on one device (no sync), autofill suggestions still go to the browser’s own list, there’s no U2F/CTAP1, and the browser extension isn’t on the stores yet (you load it unpacked for now).
Thanks for reading. Feedback, roasts and bug reports are all welcome 🙏
I wanted a slick site to tie together my professional experience, side hustle photography business, and hobby software development — without it feeling cobbled together.