r/BuiltWithClaude • u/SquareForeign • Oct 18 '26
r/BuiltWithClaude • u/theirongiant74 • 1d ago
The Long Broadcast
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.
r/BuiltWithClaude • u/Accurate_Adam • 18d ago
type any address and get a 3D model of the place, with real terrain and an STL you can 3D print
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.
Code (MIT): https://github.com/yourplace3d/3d-city
Happy to answer questions about the workflow.
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.
r/BuiltWithClaude • u/dot_mun • Aug 22 '26
👋 Welcome to r/BuiltWithClaude - Introduce Yourself and Read First!
Hey everyone! I'm u/dot_mun, a founding moderator of r/BuiltWithClaude.
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.
r/BuiltWithClaude • u/antarsoft • Oct 20 '26
I built a Claude Code harness with Claude Code, then let it prune its own rules (MIT)
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.
Built with Claude Code, MIT, plugin install. Repo: https://github.com/antarsoft/morphness
What I'd most like to know: which rule you keep re-adding to your own CLAUDE.md.
r/BuiltWithClaude • u/whiskeypie101 • 6d ago
I built Elsewise with Claude: a tool that helps you find the question your decision hinges on
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.
Try it: https://www.elsewise.quest/ (first map free, no account needed)
Example maps: https://www.elsewise.quest/example
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?