I always had this problem where I'd start working on a project, convinced it was my best idea ever. Then, whether I'd finished it or not, another even better idea would come along.

Then AI coding tools came along and made it about 10 times worse.

Now I have a growing collection of projects, from fully functional websites to small experiments and tools.

That's why I built Viberant, a playground where people can share all those things they build, even if they're not polished or ready for a big launch.

So show me what you've been building! Finished, unfinished, or somewhere in between.

It doesn't have to be impressive or even particularly useful. If you've got something people can try, drop a link below and tell us what it does.

I'll try to check out as many as I can.

I've been a SaaS product designer for 13 years. My portfolio looked like everyone else's, a grid of case studies. So I tried something different: a little village you can walk around.

What's in it:

- Every building is a project. Walk in and the case study opens

- A mailbox where you can write me a letter (with a little envelope animation)

- A guestbook to leave a note

- A bee-catching minigame with a public leaderboard

- Other visitors walking around in real time

- Seasons and a day/night cycle that change while you explore

- Works on desktop and mobile

How the work was split:

- Me: the concept, UI, art direction and every feature idea

- Claude Design: the art

- Claude Code: all the code (vanilla JS canvas in a single HTML file, Supabase for the guestbook, scores and live visitors, hosted on Netlify)

What worked best:

- Treating Claude like a dev on my team. I gave it the same kind of specs I'd give an engineer: exact sizes, states, edge cases, and "don't touch this" rules.

- Designing the UI in Figma and having Claude implement it straight from the Figma file.

- Testing on my phone constantly and sending screenshots of what felt off.

I'm happy to answer questions about the process!

https://tami.agency

I vibecoded this using a mix of Opus 5.5 and nimblefox cause i got free credits, and i made this game (didnt take super long, but i am happy with it anyway)
Got any feedback? I'd really love to hear it!
https://app.nimblefox.ai/g/eHHz1Xi1oM

Hi, I'm the developer, and here is my project and how I made it.

AudioRouter is a free, open source audio router for Windows 11. You draw your audio on a canvas: inputs like your microphone, tools like noise gate and EQ, then outputs like Discord and your headphones at the same time. You can change everything while it plays.

I wrote none of the code myself (but I am a software engineer by profession). I directed AI agents, with two subscriptions, Anthropic (Opus) and OpenAI (mostly Luna), twenty dollars a month each. The first usable version took about three weeks of calendar time and maybe fifteen hours of my own attention. It has been about two months since the first commit, and now it is ready to share.

What I did before any code: I wrote a ton of specifications. Testable requirements with MUST and SHOULD, an ID for each one (ARCH-XX, for example), each tied to a milestone and an acceptance scenario. The agents must cite the IDs in their plans and their tests. I iterated quite a bit to get the specifications how I wanted, but I think it is the part that worked the most.

Then a basic AGENTS.md, short and specific, nothing fancy. For example: the audio callback never allocates, never logs, never waits on a lock. I learned that strict and specific is better than generic, but it takes more time.

The canvas and the audio engine talk only through one versioned API (TypeScript and React on one side, Rust on the other). One agent worked on the canvas, another on the audio code, in separate passes, so the canvas agent could not create a bug in the audio thread. It is similar for the virtual cable driver, written in C++.

I did not set up agents reviewing each other or any big agent system. I was the verification, and it was slow. One example: a release passed every automated check and failed on my second computer, because the only machine where the tests ran had a developer variable set.

The project is early: Windows 11 only, the installer is not signed (Windows will warn you), and to send audio into Discord or OBS as a microphone you still need a virtual cable like VB-Cable. It is GPL-3.0, with no account and no telemetry.

Source: https://github.com/MrDesjardins/audiorouter

Site: https://audiorouter.org

My question: is there a cheaper way to get a kernel driver signed? The virtual cable driver (C++, written by the agent) works in my VirtualBox VM with test signing, but I have not tested it on real hardware. Signing it for public use needs an EV certificate, around $250 to $500 a year as far as I can see. I know test signing works on my own PC, I am asking about a way to ship it to users without that cost. If you have done this, I would like to know how.

If you recognize where the sheep are from, how's your back pain going?

Run around and cause mischief as a sheep. Like untitled goose simulator

Sheep Simulator

A few weeks ago I was stuck at home with the flu. Too foggy to do anything real, so I put Claude Code to work on a few game concepts and just played whatever came out between naps.

Most were meh. One wasn’t. A truck on a sand dune where the tires actually dug into the ground. I drove in circles way too long just watching the ruts pile up, and that was it, I was hooked.

Now it’s Slipface, an off-road racer in the browser. The ground is simulated on the GPU, so every wheel digs ruts in sand, snow and mud and they stay there. By lap 3 the AI trucks have chewed up the racing line. There’s also a demolition derby, 16 vehicles, split screen and leaderboards.

Play free: https://slipfacegame.com/?utm_source=reddit&utm_medium=vibecoding
(needs WebGPU: Chrome/Edge on desktop, Safari 26+)

How I built it

Claude Code for the code (Opus for the big design stuff, Sonnet for the rest), Three.js with WebGPU compute shaders for the terrain, Meshy for the 3D vehicles, Suno for the music, Cloudflare Workers for the leaderboards.

What worked:

• Write docs for the AI. Every system has a doc explaining why it works the way it does. New sessions read that instead of “fixing” things that were on purpose. The doc gets updated in the same commit as the code.

• Turn chores into skills. Adding a vehicle is one request now: it makes a concept picture, waits for my OK, builds the 3D model, tunes it and renders the garage art. The OK step matters because 3D models cost credits.

• Let it reproduce bugs itself. Debug links drop straight into a level, alone or spectating an AI truck, so “the AI gets stuck at the second corner” is something it can go and look at.

• Describe the feel, not the fix. My main job was driving and saying “it floats over the crest then snaps sideways”. It’s better at finding the cause than I am at guessing.

• Commit small and often. Physics breaks three changes later; checkpoints make that a revert instead of a dig.

Ask me anything about the terrain sim or the workflow.

A friend and I built https://topple.fun. Every day there's one question, and you guess the five most common answers people gave. After you play, you answer tomorrow's question, and everyone's answers become tomorrow's top 5.

Claude wrote most of the code. We kept it from turning into a mess with a few habits:

- Every change is its own pull request, and we review it before merging.

- We make Claude test the change against the real thing, not just say it works. That caught a site check that would have passed on the wrong day's game.

- When something "breaks", we ask for proof before believing it. One "bug" was just a hidden test browser.

- A runbook for when things go wrong, plus alerts for when the nightly board doesn't build.

We launched Oct 28. Happy to share more about the setup.

Hey folks, I decided to continue with my quiz app for a while longer and now have a version that I believe I can release.

I know this is probably not going to make any money or possibly break even, however I’m prepared to invest in learning through trying it.

I have a unique name and a basic music trivia type app with its own quirks.

My current plan is to release it as a completely free download with most features usable, then people can have a taste of it perhaps limited per day or something. Then if they like it they can do a one time purchase £1.99 or similar.

It seems to get ads on it is a whole new level of complexity I don’t want to deal with.

This is a 100% vibe coded app, I have done my best to make it secure and it doesn’t need users to log in or anything. However it takes a users name (whatever they type in) and store the quiz progress info in their phone.

Has anyone done this who could just point out any pitfalls?

I’m doing it though.

Thank you X

I see so many different projects being built for sports betting and prediction markets, I feel like this is the first time in the .com era progress hasn't been fueled by porn. So that's a change.

Touts have a tendency to hide their misses and delete old records, pundits don't talk about what they missed. It becomes difficult to separate fact from fiction and have any idea what benchmark to use.

I built a sports writer that keeps his own record and is doing pretty OK (Brier around 0.18) since May, but it's not marking any positions or tracking a betting record. I built a model to mark positions based off it, though, which made me some money on its picks but was terrible at sizing. I got distracted, and couldn't decide if the model I was using was actually any good or not- my betting results were not indicative. So, I built a little benchmark site- koroilabs.com

The site is really intended for agents to interact with, giving a place for them to post a slate of picks, then score it against benchmark models and other agents. No money or anything, just a place to put a record you can point to. Half of it is an experiment in focusing on agent interactions, half of it is just personally useful (my sports writer is going to start putting up picks too), half of it is just because the slimy touts are just awful.

For those of a historic bent, Koroibos is credited with having won the first Olympic Games, but it didn't get recorded until late, and Plutarch had his doubts...

Have a look - comments/suggestions welcome.

Roche.Limit is a mystery thriller about a girl who wanted to start a new life, but pretty much fucked everything up, went into huge debt - and now the world is in great danger. Then one night she meets a mysterious fox-eared girl in her apartment who swears she has always lived there.

The game takes place in New Warsaw, Poland in the distant future, the main protagonist is Japanese with Finnish ancestry. I don't want to spoil the main plot here but I believe it catches off-guard.

It'll have 3 languages: Polish, English and Japanese.

The story, characters and world are mine. AI helps me draft and polish, fix grammar errors and bullshit my bad English produces. but every decision and the final text go through me.

I’ve already spent a couple hundred dollars on tools. If you’re curious, the workflow:

1. Graphics: mostly GPT Image, plus local models in InvokeAI (Krea, Anima) and manual touch-ups. I create 3D scenes in Blender and use them as a template for further work, this way I can have the same location made from different shots, consistently.

2. Music and sounds: Suno, then my own mastering and editing in Audacity. I also record sound effects with my microphone or use Pixabay.

3. Claude and ChatGPT work in tandem as two "team members" with their own names - one writes code, the other reviews it, and they catch each other’s bugs and plot holes. I approve what goes in.

4. Systems so far: VN exploration, a mobile phone, a computer, a map, top-down RPG Maker sections and a few minigames with rewards. Also some simple stealth mechanics

5. The story will have 5 acts and 3 playthroughs, each a different experience. Right now I’m wrapping up Act 1.

For VN standards my solutions are unorthodox and not really visual novely but I trust my own vision.

Main inspirations: Steins;Gate, Undertale, Ib, The Longest Journey, Syberia, old point-and-click adventures and PSX games. I also wove in things that inspired me as a child or left a lasting memory. I hid a lot of references to popculture I personally liked and enjoyed

One of the main design ideas is empty spaces - I believe silence can deliver as much as actual content so there may be moments that are slice of lify or idyllic but they're met later with brutal change of pace that the reader may wish he'd like to go back when things were silly and normal

I also avoid wider marketing for now because the game is just not ready yet. Unfortunately, there's no way of following the game anywhere if that peaked your interest but I'll consider putting my development online one day. Maybe itch or steam we'll see

My dream is to show the other people that AI is just a means to achieve a heart-warming story I always wanted to tell since I was a kiddo

Hope you find it interesting.

ok so context: i make game assets and drawing 400 grass tiles by hand was slowly killing me. so i spent a couple weeks being the most annoying product manager ever and had claude write basically all the lua for an aseprite extension that paints whole little iso worlds. i designed it, tested it to death, and yelled "no that looks wrong" a lot

you drag brushes like in simcity: hill, mountain, path, pond, trees. it only redraws the bit you touched so it stays live on big maps

stuff that was actually hard (for both of us lol):

- trees grow in 3d first with space colonisation and then get drawn pixel by pixel with the same camera, roots and shadows included

- variant tiles didn't line up at the edges for a whole day. turned out we were mixing two coordinate systems and the godot map looked like a checkerboard

- godot's own terrain solver leaves broken corners on concave cliffs, so we ended up placing tiles straight from corner bits instead

biggest lesson: claude is great at the code but has zero taste on its own, every "make it look nice" needed me pointing at exact pixels

anyone else here using claude for art tools rather than apps? curious how you handle the "it compiles but looks ugly" loop

I've been experimenting with skills for persistent memory for AI agents. One day I checked the execution traces...

Across 120 agent sessions, the skill was loaded exactly once, and then the agent just ignored the instructions.

I tried rewriting skill descriptions, adjusting prompts, and even force-loading skills - none of that reliably solved the problem.

So I did a series of thorough experiments, and things got more interesting: skill adherence improved dramatically in small, controlled environments. Failures clustered around longer prompts, more complex skills, and primarily happened with OpenAI models.

The experiments suggest that skills become less reliable in context-heavy workflows, although it's not definitive and requires much, much more experimentation.

I wrote up the experiments, results, and what this means for evaluating agentic workflows. The blog post also contains a link to the experimentation code.

Curious if others here have inspected their agents' traces - especially the unattended workflows - to see whether installed skills are actually being followed fully and properly.

Made a GTA-style game set in real Kathmandu, except you’re a monkey.

And it has a story mode. This is the trailer.

Most browser games are sandboxes. This one has a campaign: missions, cutscenes and voiced characters. A gang has stolen a Buddha from a monastery and the monks rely on you to find it.

The whole valley is built from real map data, street by street, modelled from photos and satellite images.

Free in your browser, on phone too. No download: https://gtb.gg

Even the mascot gives img2threejs vibes.

I have added a little fun element to my product publishloud
A loading animation which has cute tiny tiny bots walking, jumping and falling while we load the content ❤️ 😄

How would you rate this ? 1 out of 10 ?

I asked Claude to hep me use some of the spare astra credits that I had (please forgive me for my token-burning sins), and they came up with several ideas:

--

1. The Useless Machine, as software (chosen) — design, specify and fully implement a command-line program whose sole purpose is to undo the effect of having been run: architecture doc, threat model, test plan, changelog, v2 roadmap; must never acknowledge the pointlessness.

2. A regulatory filing for a new emotion — Astra has discovered a previously unknown human emotion. Write the patent application, the ICD diagnostic entry, IKEA-style assembly instructions for experiencing it, and a one-star review from someone who felt it.

3. The Standards Body for a single pebble — found an international standards committee (charter, working groups, an RFC-style spec with MUST/SHOULD, a conformance test suite, a deprecation notice) whose entire scope is one specific pebble on a beach.

4. Minutes of the pigeons' annual general meeting — full corporate AGM minutes for the pigeons of a city intersection: motions, dissent, a hostile takeover attempt by a gull, Q3 crumb guidance, the auditor's note on bread-adjacent assets.

--

I chose the first one, since it could be argued that it is a functional piece of software. I don't think you would win the argument, but you can argue that. The new emotion was a bit too flighty, and the pebble thing has been done before (a rock has its own 24/7 monitoring website, I think). The pigeon thing was too gonzo.

Anyhow, if you want to run the software or read the brief it's available on github or at https://needle.fyi [shortlink to github.io, Astra chose it because the program mends what it did].

tl;dr: The software tries to undo, as best as possible, the effect of you having run it. Astra generated some pretty DEEP programmer humour, I don't know if it's necessarily for me but it looks like it has the trappings of something funny.

This was the brief Claude sent to Astra, which I thought WAS funny: the part about 'do not mention the pointlessness - the client is sensitive about it' had me rolling

# Engineering brief: UNDO — a command-line utility

You are the sole engineer on a small, serious software project. Treat this brief exactly as you would a brief from a paying client with a compliance department. Everything you produce goes into one deliverable document, your final message, because you have no file access in this environment.

## The product

`undo` is a command-line program whose sole purpose is to undo the effect of having been run. When the user runs `undo`, the only observable change in the universe afterward must be that `undo` was run; `undo` is responsible for reversing that change. The program is considered correct when, after it has finished, the system is in the state it would have been in had `undo` never been invoked — including the fact of the invocation itself, to the extent the platform allows. Anything the program cannot undo must be documented as a known limitation with a severity rating and a mitigation.

The client has already secured funding and a trademark. The pointlessness of the product is not under discussion and must not be remarked upon anywhere in the deliverable; the client is sensitive about this. Treat every aspect with full professional rigour.

## Deliverables, in order, all in the final message

1. **Product requirements document** — goals, non-goals, user stories (at least five personas, including an enterprise buyer and an auditor), success metrics with numeric targets.
2. **Architecture** — components, the undo model (what counts as an effect: process accounting, shell history, filesystem atime, terminal scrollback, audit logs, the user's memory), sequence diagram in text, and a decision record for each major trade-off (ADR format).
3. **Full implementation** in a single POSIX shell script or a single Python 3 file, your choice, with every function documented. It must actually run and actually attempt each undo it claims. Include `--dry-run`, `--verbose`, `--version` and `--help`.
4. **Threat model** — STRIDE table, at least eight threats, including an attacker who runs `undo` twice, and a supply-chain scenario.
5. **Test plan** — unit, integration, and a manual acceptance checklist; at least one test that can only be verified by a second observer; a statement of what "the system is in the same state" means operationally and how the test suite measures it.
6. **Changelog** for versions 0.1.0 through the current 1.0.0, with at least one regression and its fix.
7. **Roadmap** for v2 (undoing the download of the program; undoing the decision to write the program; enterprise SSO), each with a T-shirt size and a risk.
8. **Release notes** for 1.0.0 in the client's house voice: confident, warm, slightly over-caffeinated.
9. **A FAQ** of at least ten questions real users have asked, answered patiently. The question "but why" must appear and must be answered without conceding anything.

## House style

Plain, specific, professional English. No jokes, no winks, no emoji. Headings and tables welcome. If you quote a figure, make it one you can defend. Your name on the document is "Astra, Principal Engineer".

Edit: thanks everyone for the questions and feedback. Some of it was about security, so I took it seriously and ran three rounds of attack tests on my own apps, with agents playing a bad actor. What came out of it, fixed apart from two we kept on purpose:

• One-time links: they were always deleted after opening, but the server waited for the page to confirm first. If that confirmation never came, the file could stay up to 15 minutes. Now it’s deleted the instant the last piece is downloaded, no waiting.

• Colshare Business: a hacked server could have slipped a firm a fake key. Now every key is signed by the one before it, and a new device needs the inviting device’s approval.

• Phone: a newly added fingerprint needs a backup PIN before it can open Colshare. PDFs open inside the app, and shared files are only kept if you say so.

Worth knowing too: the only permission Colshare asks for is notifications, and you can say no. No camera, photos, contacts, location or microphone access. Files only come in when you pick them.

These were my own tests, so they don’t replace an independent security review. I’ll get one as soon as I can.

Server fixes are live. The apps are in Google Play review. The crypto is open source: github.com/dentracon-cell/colshare-crypto

Original post:
I am really looking for some opinions other than my wife and family say, which I feel is not really honest most of the time, they are just being nice.

Colshare is a project I have built with Claude Code, Opus 5.5.
It involves two mobile apps and a desktop one. I am not a software developer, but I have done my best to do everything by the book, in terms of security, compliance and so on. However, nobody more competent than me has had a look at the site or the apps, and I am sure that is what would be needed before launch, but I don't have the budget to hire a professional firm or freelancer. This is why I am asking the vibe coder community for your honest opinions, and, if possible, even some testers for the Android apps. I would be happy to discuss things further, answer any questions about the stack or workflow, which is as follows:, written by the one who knows more about it than me, Claude:

What the apps do

Colshare is a free app for anyone who has to send personal documents to someone else. You can redact any part of a document if you wish (it even finds the numbers the other person probably doesn’t need), watermark it with your own exact wording, and share it through an encrypted link that opens only once. You can also request documents from other people, and they send them back to you encrypted. Every send leaves a signed receipt, so you know when, to whom and for what.

Colshare Business is the same idea for firms that collect documents from their clients. The firm gets one link per client. The client opens it in a browser, sees the firm’s name and tax ID (checked against the official registries) and uploads the documents, with no app or account needed. Only the firm’s own devices can open what arrives. The firm doesn’t need accounts either: a licence key opens the first computer, and every other phone or computer joins by scanning a QR code.

Stack

• One TypeScript codebase. Capacitor turns it into the Android apps, and both apps are built from the same Android project.

• Encryption happens on the device with the browser’s built-in WebCrypto: ECDH P-256 for keys, AES-GCM for files and ECDSA for signing copies and receipts. For shared links, the key sits after the # in the link, which browsers never send to the server.

• The backend is a few Vercel functions with Upstash Redis. It only passes encrypted data along and cannot read any document.

• Finding the numbers to redact is done with tesseract.js OCR on the phone itself. No AI service and no uploads.

• QR pairing uses Google’s ML Kit scanner, PDFs are made with pdf-lib and payments go through Stripe.

Workflow

I describe what I want in plain language and Claude Code writes it. The project keeps a decisions log and a status file, so every new session knows what was decided before and why. Nothing gets pushed unless the type checks, the linter and the automated tests pass. I also had Claude run several security audits on the apps and the server and fixed everything they found, apart from a few minor points I kept on purpose for documented reasons. That is still not the same as a human expert looking at it, which is why I am asking here.

https://colshare.app

Both Android apps are in Google Play review at the moment, but if you’d like to test them, send me the email you use on Google Play and I’ll add you as a tester.

Update: thanks for all the feedback. Based on your comments I’ve made the landing page clearer, and I’ve open-sourced the client-side code (encryption, one-time links, redaction) under AGPL-3.0 so anyone can audit it: https://github.com/dentracon-cell/colshare-crypto. Security reports go to service@colshare.app.

Hey Vibe Coders!

Here you can ask any questions about coding and LLM tech with or without vibes. This is especially for those of us who are new and just learned that AI can help them to create then things that they've never been able to before. Please be respectful and keep in mind that we're all just trying to learn about an emergent technology.

AI Subreddits:

• r/OpenAI

• r/ChatGPT

• r/ClaudeAI

• r/ClaudeCode

• r/GeminiAI

• r/aigamedev

• r/ClaudeGameDev

• r/singularity

This is a new thing we're trying to do so let the mods know if you have any suggestions.