r/vibecoding • • 20h ago

Meme The duality of a token burner

Post image
425 Upvotes

r/vibecoding • • 22h ago

Showcase/Project I made a site with every GTA radio station using opus 5.5

71 Upvotes

GTA radio was always my favorite part of the games, so I build every GTA station in one place.

Built the whole site with Claude Opus 5.5 on medium effort and it pretty much one-shotted it. For the latest update, Opus 5.5 orchestrated and Sonnet 5.5 on high did most of the fixes.

Check this out : gtamusic.fun

- Every station from GTA III, IV, V, VI, Vice City, Liberty City, Vice City stories, Chinatown Wars, San Andreas

- Radio wheel like in game (hold Q, or long-press on mobile)

- Loading-screen backgrounds and talk stations like Chatterbox and VCPR

Happy to answer anything about it


r/vibecoding • • 23h ago

Showcase/Project I got tired of needing closed Windows software just to configure my GamaKay TK75 HE V2 ISO keyboard (especially since I run Linux), so I wanted to test how far vibe coding can actually go on real bare-metal hardware instead of another web app.

56 Upvotes

What's actually running on the keyboard

  • Native VIA v12 + WebHID (works on Linux, macOS, Windows with zero vendor software)
  • 8 kHz Hall-Effect engine: 0.10-3.90 mm actuation, Rapid Trigger / Continuous RT (Fn+1), SOCD (Fn+2), onboard 82-key Hall calibration
  • 6-page pixel-art TFT HUD (optional local U24 patch): live animated Hall switch, WPM, 3-state battery/charging icon, settings menus, 0V TFT power-off (Fn+F4), and a 30s idle screensaver
  • Onboard macro recorder (2 KB pool, 16 slots) + a 5x19 text editor right on the 0.85" TFT screen so you can edit recorded macros with arrow keys/knob before saving
  • Caps Lock vertical 8-LED accent bar trigger + high-contrast Fn/macro layer RGB
  • Tri-mode: 8 kHz USB, 2.4 GHz dongle (with wireless VIA), and BT1-BT3

Tools I used

  • AI coding: Antigravity CLI (Gemini) for architecture, C11 firmware, Python tooling, and debugging
  • Firmware toolchain: arm-none-eabi-gcc, CMake, TinyUSB
  • Flashing & live telemetry: custom Python CLI (hidapi) for DFU flashing, live Hall ADC readout, battery voltage telemetry, and backup/restore
  • Verification: pytest running host-compiled C11 unit tests + a headless C framebuffer bridge that renders the real TFT HUD into GIFs on my PC

How I built it (workflow & lessons learned)

  1. Make it unbrickable first. Before flashing anything experimental, we mapped the flash layout so the factory DFU bootloader (hold Esc while plugging in USB) and the factory Hall calibration pages (0x08032000+) are never erased. Even a completely broken build recovers in 5 seconds.
  2. Give the LLM a fast local feedback loop. Flashing hardware on every tiny bug is slow, so we built host C11 unit tests (pytest) for the Hall engine, macro recorder, flash EEPROM wear-leveling, and TFT HUD, plus a headless TFT renderer. The AI could compile, run tests, and catch regressions in 2 seconds before touching the board.
  3. Real hardware measurements beat guessing. Some bugs only showed up on physical hardware and had to be measured over live HID telemetry:

    • Unplugging USB or cranking RGB to 100% white dropped the Hall sensor supply rail by ~9.1% (-244 ADC counts across all 82 keys), causing fake 0.8 mm resting travel. Feeding real ADC dumps back to the LLM led to a per-frame ratiometric rail tracker that brought resting drift down to 0.0 mm.
    • Active RGB/TFT current prevented the hardware charger pin from flagging "full" even at 4.2V, so we measured VBAT across 4 load states and built a load-compensated gauge.
    • Moving macro scratch buffers off the tiny 2 KB Cortex-M4 stack (static) fixed hard-faults when expanding the macro pool from 384 B to 2 KB.
  4. Why having a clean modular base is the real win: Once the test harness and hardware abstraction were solid, adding totally new features (like the onboard 5x19 TFT macro text editor or custom battery icons) only took a few prompt-test-flash cycles.

Disclaimer & Repo

Experimental community firmware, use at your own risk. Tested on my own TK75 HE V2 ISO unit (ANSI / other PCB revisions untested). Both the main MCU and U24 TFT can be rolled back to stock, and there are zero proprietary vendor binaries in the repo.

GitHub (source, pre-built v1.0.0 release, and live firmware-rendered GIFs): github.com/MrockHunter12/gamakay-tk75-he-v2-custom-fw

Curious if anyone else here has tried vibe coding bare-metal firmware or MCU projects, and what your testing workflow looks like!


r/vibecoding • • 5h ago

Meme hot take: "learn to code" will become "learn ai"

37 Upvotes

r/vibecoding • • 21h ago

Workflow/Prompt Is CI/CD becoming a bottleneck in your vibe coding projects? How do you handle it, and how much do you spend?

37 Upvotes

I've been experimenting with vibe coding on increasingly complex projects, and one recurring issue I've noticed is that CI/CD often becomes a bottleneck.

As projects grow and AI agents generate more code, running tests, builds, and validation pipelines can become slow and expensive, especially when multiple agents are working in parallel.

I'm curious how others are dealing with this:

What's your CI/CD setup? GitHub Actions, GitLab, local runners, self-hosted infrastructure, or something else?

How do you prevent CI from becoming a bottleneck? Do you run tests locally, optimize pipelines, use dedicated runners, or take another approach?

How much do you spend on CI/CD per month? And roughly how many projects or agents are you running?

Have you found a setup that scales well as your vibe coding projects become larger and more complex?

Would love to hear about your experiences, especially from people building more than just simple prototypes.


r/vibecoding • • 17h ago

Showcase/Project Not a programmer, but I built my kids a pixel cat that lives my day (Pi Zero + tiny screens + Claude)

Thumbnail
gallery
26 Upvotes

I’m not a programmer at all, but I love DIY and building things for my family. So I’m really happy that with Claude I can now make things I could never code myself. This is the latest one.

My kids wanted to know where I am during the day, so I built a little desk buddy: a pixel-art cat on a GeekMagic SmallTV (240x240). Now there are two modes:

Cat #1 follows my day. iPhone Shortcuts send one word (“home”, “work”, “leaving”) to a tiny Cloudflare Worker. The Pi checks it every minute, and the cat rides his bike, works in the office, has lunch with his cat colleagues and rides back home.

Cat #2 lives his own life. Every morning he plans his day by a set of rules: wake up, wash up, breakfast, work on weekdays, a grocery run to our local supermarket, one outing (café with kittens playing in the kids’ corner, library, swimming pool with a diving tower, ice rink in winter, town center), and on weekends a trip to Paris, London, Rome or Berlin by train, car, motorbike, plane or hot-air balloon. At home: an attic gym, a red-light darkroom where he prints and hangs photos one by one, bath time, cooking, guitar evenings. No activity repeats within about 45 minutes, no naps in the morning, no yard after dark, and he washes up with the kids at 7:30 pm.

How I built it (and AI disclosure): I just described what I wanted in plain words, looked at the previews and said “yes” or “change this”. Claude Code wrote all the code, set up the Pi and fixed the bugs. The rooms and cat poses were generated with Magnific (via MCP), and Claude cut them into sprites. My son’s feedback (“the cat’s eyes look like crosses!”) was the toughest code review :)

By the numbers (built over about 3 days):

  • ~5,400 lines of Python in 31 files
  • 58 AI-generated images, cut into 186 sprite poses (our grey cat, a ginger, white and black cat, and kittens)
  • 20+ locations: 9 rooms at home, office + canteen, supermarket, 5 town places, 4 cities, an airport
  • 6 kinds of transport, all with takeoff/landing or ride-in/ride-out animations

The hardest part wasn’t drawing, it was making everything consistent: the cat never pops out of nowhere, doesn’t wear his office suit on weekends, the ginger cat knocks and gets the door opened, and the Pi still finishes every minute in time.

How it works:

  • Raspberry Pi Zero W, Python + NumPy + Pillow. Every minute it renders a one-minute animated GIF and uploads it to the screens over Wi-Fi. Stock SmallTV firmware, no flashing.
  • Real time on every wall clock, real weather in every window (Open-Meteo), trees and grass change with the season, lightning during storms.
  • The Pi Zero is slow, so it renders the next minute ahead of time.
  • The backlight dims automatically: 10% from 5 pm, 1% at bedtime.
  • The same animation also goes to a private web page, so I can check on the cat from my phone or even my Apple Watch.

Next up: a faster Pi (the Zero is at its limit), casual outfits for the white and black cats, and more cities.


r/vibecoding • • 19h ago

Showcase/Project Old stuff vibecheck

Thumbnail
gallery
16 Upvotes

I had some old Philips mp3 player from late 2007. The software was glitchy and player was slow. Decided to perform some reverse engineering having Claude and ollama. Here you go - a flappy bird on mp3 device.

Took the phone which lays in drawer. Installed postmarketOS (well I would spent a week doing that without opus, since the phone was not supported). Now it’s running some docker containers, serves as uptime monitor for my other web projects, slides go digital clock and weather info.

Before years doing this would take ages to reverse engineer and code it. Now it takes hour or two. Look up what gold you have in cabinets.


r/vibecoding • • 12h ago

Help/Question Learning normal coding through vibe coding?

14 Upvotes

Been making an app, because I need it for some stuff working on and automating stuff helps a lot. Using ChatGPT and Claude. Been asking for rundown on terms and such when a change is made to the code, to sort of learn what everything does. I’ve learned a bunch of stuff, but it does happen at a slow pace. Anybody have tips on also learning while vibecoding? Learning to code is sort of a bucket list thing for me


r/vibecoding • • 20h ago

Showcase/Project PIECENTAGE: I made a daily browser game where you cut a pie to match real percentages

11 Upvotes

r/vibecoding • • 14h ago

Showcase/Project I'm a UX designer, not a programmer. I vibe coded a full synthesizer that runs in the browser

Post image
8 Upvotes

Hi all,

Here's the project: https://synth.shibui.nl (free, no account, works offline). There are a few short audio clips on the About page if you just want to hear it: https://synth.shibui.nl/about.html

What it is: an 8-voice analog-style synth. Three oscillators, a Moog-style ladder filter, envelopes, LFOs, a mod matrix and effects. It also has a TB-303-style sequencer, a MIDI recorder with a piano-roll editor, MIDI in/out/clock, export to MIDI files, and it can turn what you played into printable sheet music. It works with a MIDI keyboard, and with several fingers at once on an iPad.

How I built it

I'm a UX designer, so I can read a bit of code but I can't write it myself. All the code was written by Claude. My job was deciding what it should do, how it should feel, and mainly playing with it. :-)

  • Tools: Claude, set up so it could write the code, run tests, and put the files straight into a folder on my Mac. I upload that folder to my own hosting myself.
  • Stack: one single HTML file with plain JavaScript and the Web Audio API. The sound engine runs in an AudioWorklet. No frameworks.
  • Workflow: small steps. Iterative! I ask for one thing, for example: "I want to record what I play and export it as MIDI". It builds it and tests it. I try it with my real MIDI keyboard or iPad, and tell it what feels wrong. Before I knew it, I had both a sequencer and a MIDI recorder, with a lot of overlap in what they could do. So I asked Claude to combine them into a single feature. It took a long time to build, but in the end it turned into a really nice integration.

Things I learned

  1. Let the AI test with its ears. I was amazed by how Claude tests sound. It can’t listen, but it can measure: the tests open the synth in a real browser, record the audio and measure pitch, timing and loudness. Roughly 85 measurements plus 35 separate checks. That's how it could tell me "this note plays at the right time" instead of "I think it works".
  2. Feel is something only you can test. Playing from my MIDI keyboard felt laggy. It turned out to be a large audio buffer, plus a limiter that delayed the sound by 6 ms. After the fix the delay went from about 42 to 11 ms in the test setup, and it feels like a real instrument now. And I noticed, don't play with bluetooth headphones, the latency is huge!
  3. Get outside criticism. I had the site reviewed. The main point was "too many features for beginners". So we added a start screen (Play / Explore / Learn), a Preview button that plays a phrase fitting each sound, and four big "quick" knobs (Brightness, Movement, Space, Character).
  4. I was surprised by how well Claude handled the interface design. I’m not saying I’m worried about my job, but getting reasonably consistent styling right is no problem for it. The result looks polished, and I rarely have to step in on accessibility, responsiveness, or styling.
  5. Sometimes, though, you could end up going back and forth. In the sequencer, I wanted to be able to limit the sequence length. Claude added an end handle, but when I tested it, it didn’t appear. After discussing it with Claude, I realised it had only added the end handle for certain types of sequence. Once I spotted that, I asked Claude to make the feature available for all sequences. Hehe. That worked, but then I still didn’t have a start handle. After asking for that too, it got it right. Now the sequencer plays neatly within the boundaries when it’s running with loop enabled.

I'd love feedback, especially from people who play synths: what feels off, what's missing, what's confusing?


r/vibecoding • • 15h ago

Help/Question Gemini is still too expensive compared to Opus (sub has low usage)

6 Upvotes

I have been using Opus 5.5 for the past 2 months, and I absolutely adore it. It has been my main driver, and I don't even really touch fable 5.2 at all. Now Neon is out, and I love it more than Opus 5.5, so I wanted to replace my Anthropic $100 plan with a Google one.

Unfortunately, both my testing and Neon's own research and analysis, put the Google sub at about 1/2 the effective usage than the anthropic sub (and this is when factoring the +$40 weekly API credits). This is borderline usable for any kind of serious development work, and we aren't even talking about using subagent heavy workflows or swarms, or anything fancy like that (which I don't do anyway).

For those who use Neon for vibe coding etc. how do you see it fairing in terms of usage?


r/vibecoding • • 20h ago

Showcase/Project I created a ps1 style retro racing game

6 Upvotes

Howdy folks, I made a arcadey ps1 style racing game. You can start playing it online from here:
https://outpostracer.com/

How I made it:
I started early this week because I was super bored with work. Initially I just started prompting chatgpt codex into building a small ps1 style editor playground. From there I started prototying the game, driving physics, on day 2 I realized I could make a finished game so I started fleshing out the game more.


r/vibecoding • • 6h ago

Showcase/Project I built a project organizer for scattered files, folders, links and notes - ClingSpace

4 Upvotes

I've been building ClingSpace, a desktop productivity app that started as a personal frustration and turned into my first cross-platform project.

My files were organized, but my projects weren't.

I'd have documents in one folder, spreadsheets somewhere else, reference websites open in a browser, and random notes scattered everywhere.

So I built ClingSpace.

The idea is pretty simple: bring everything related to a project into one workspace without moving or duplicating the actual files.

Here's what it does:

- Files & Folders: Add resources from anywhere on your computer

- Links: Keep websites, documentation, and references together

- Snippets: Save quick notes, reminders, and code snippets

- Multiple Spaces: Separate workspaces for different projects

- Global Search: Find resources across your projects

- Smart Recovery: Reconnect moved or renamed files

I originally built the Windows version with .NET/WPF, then took on the challenge of bringing it to macOS using Avalonia.

One of the more interesting challenges was making file references reliable. I didn't want users to lose their project organization just because they renamed or moved something.

The Mac launch has been encouraging! I've already gotten some great feedback and have been making UI improvements based on what users actually want.

Next up is optional task management with checklists and Kanban boards.

It's local-first, works offline, and is available for both Windows and Mac.

https://clingspace.com

For those who've built cross-platform desktop apps with AI assistance, what was your biggest challenge moving from one operating system to another?


r/vibecoding • • 10h ago

Showcase/Project Refall, a free falling-block puzzle game with 60+ music-driven universes

4 Upvotes

Refall is a free, open-source falling-block puzzle game where the music drives everything. The fall speeds up and the scene transforms on each song's drops. It has 60+ visual universes and a 15-stage campaign, and on desktop any YouTube playlist can become the levels.

I built it with Claude Code (C++ / OpenGL). Every visual is a procedural shader written by Claude: no generated images or music. The game can render its own screenshots and clips, so Claude checks its work visually. I often run several agents in parallel on separate branches.


r/vibecoding • • 12h ago

Showcase/Project I vibe coded my portfolio as a 3D bedroom: click the old PC and it zooms into a working Windows XP desktop

Thumbnail
gallery
4 Upvotes

Student here, no 3D background. I wanted a portfolio that's not a boring grid of cards, so I told Claude Code what I wanted and kept steering until it looked right.

Live: https://kayzee-room.vercel.app/hi/r-vibecoding-9d9 (works on phones too)

What you get: a bedroom at dusk with fairy lights and a lamp. Click the CRT and the camera pushes into the screen, which is a live XP desktop where my projects open as windows. There's also a boombox that plays my Spotify playlist through a crackly radio filter, a bunch of clickable props, a few easter eggs, and some mini games (Snake, Reversi, a typing game) that agents built in parallel.

What the vibes looked like in practice

  • Most of my prompts were feedback like "the flat clay look is wrong", "why is the drone sitting on the PC", "the desk has no personality", "there's light leaking around the screen". It got there in rounds, not in one shot.
  • Claude drove Blender headless through Python scripts to build and render the room, and wrote the three.js for the rest. I never opened Blender's UI.
  • The hardest part was the camera zoom. It kept glitching, and after a few failed tries Claude pre-rendered the push-in as a short video and synced the 3D camera to it. Problem solved.
  • A thing I learned: when I said "don't touch the grass", I meant it. An agent "optimised" it and it looked worse, so now I guard it.

Biggest lesson: being specific about what looks wrong beats describing what you want. Happy to share prompts or the workflow if anyone's curious. Honest feedback welcome, especially on performance on your machine.


r/vibecoding • • 14h ago

Help/Question Open AI ChatGPT Sol 6.2 (High) driving me mad!

4 Upvotes

I did A LOT of work today using the 'chat' interface (Sol 6), happily coding away getting encouraging results as I tweaked the system I'm building.

I used ZERO usage which was great, and I think I moved things on. However at one point this evening it 'reveals' to me that the system is not working in one of the most fundamental ways it was designed. I got the ' yes, sorry I should have told you that earlier, that's on me, you even asked me about it and I was wrong to say what I said.....'etc etc

It honestly made me so furious!!!!

I then switched to 'Work' and have been using Sol 6.2, and it's noticeably better. I still have been left a bit doubtful of it's honestly and here I still am making tweaks and it still not being quite right. It's never ending sometimes!!

When do you finally switch off for the day??


r/vibecoding • • 19h ago

Showcase/Project I was so frustrated of not being able to control Macbook from the bed while watching a movie so I created this

4 Upvotes

Any time I had to move to the next episode, or adjust the volume, I had to get up and go to the MacBook, or have a bluetooth keyboard / mouse nearby which was annoying.

So I built Lazy Remote, which uses bluetooth to connect iPhones to MacBooks. I used Claude Code to build it, you can see my whole setup in the repo.

It is simple, open-source, does not collect any data and completely free.

You can find the app features and the links below:

Iphone App

Github Repo - Also contains download links


r/vibecoding • • 11h ago

Showcase/Project PDP 11 Emulator for Android

3 Upvotes

r/vibecoding • • 19h ago

Showcase/Project I vibe-coded 4 Bitcoin-themed pocket LCD games in one afternoon. Here's how the fake LCD actually works

Post image
3 Upvotes

Here's the project: https://im.4xs.dev (landscape phone, or desktop with the keyboard)

Docs, screenshots and design notes: https://github.com/kotyzap/Igra-Modernaya

BTC Miner (Nu Pogodi, Jen Počkej) remake

I grew up with those 80s LCD handhelds (the beige ones with the clock and the GAME A / GAME B buttons). I wanted that feeling on my iPhone, but with my own games. So: BTC MINER (catch coins from 4 ASIC rigs), SATOSHI'S KITCHEN (flip coins in a pan, every catch splits them down to sats), NOT YOUR KEYS (dive to a vault, dodge a rug-pull squid) and TO THE MOON (dodge FUD clouds).

I'm in sales, not a developer. My last "real" program was a Paint clone in Pascal in 1997.

Tools

- Claude (Cowork): all the code, testing and deploys, driven by short chat messages and screenshots from my phone

- Cloudflare Workers + static assets for hosting, KV for the Top 5, D1 (SQLite) for anonymous play stats, Cloudflare Access to protect the admin page

- wrangler for deploys, Playwright for automated tests and the screenshots

- GitHub Pages for the docs site

Process / workflow

  1. Started by describing the hardware and pasting photos. First version: a home page plus 2 games in a single HTML file.
  2. Iterated purely on feedback from playing on the phone: "landscape only", "make the LCD look real", "I can't reach the top-right corner on the keyboard", "this FUD layout is impossible", "no sound on iPhone".
  3. Each change was tested in an emulated iPhone (Playwright) before deploying, then deployed with wrangler.
  4. Added Global Top 5 Score, an admin dashboard and the docs repo at the end.

Build insights (the fun part)

The LCD look is 4 layers on one 400×260 canvas:

- a grey "reflector" with a tiny 1px checker + grain texture and a vignette

- a coloured printed backdrop that never changes

- segments: every sprite is drawn every frame. Off = 4.5% black "ghost", on = near-black with a drop shadow

- a diagonal glass glare on top

The drop shadow is the single biggest realism trick. Real LCD segments float above the mirror behind them:

```js

ctx.fillStyle = on ? '#111210' : 'rgba(17,18,16,0.045)';

if (on) { ctx.shadowColor = 'rgba(0,0,0,.3)'; ctx.shadowOffsetX = 1.1*k; ctx.shadowOffsetY = 1.4*k; ctx.shadowBlur = 0.9*k; }

```

*The rhythm.* Moving all eggs/coins together feels wrong. The old games move ONE track per tick, in rotation, each with its own beep. That alone made it feel like the real thing.

*Always-solvable random levels.* TO THE MOON first generated layouts you couldn't survive. The fix: a "safe lane" runs through every row and may only shift by one lane, into a lane that's also open in the row above. I fuzz-tested 120,000 rows with 0 dead ends.

*iPhone audio.* Web Audio only unlocks on touchend/click, not touchstart. Setting `navigator.audioSession.type = 'playback'` makes it play even with the silent switch on.

*The device face* is laid out in fixed "design units" (height 820) and scaled with one CSS transform. The width stretches with the phone's aspect ratio, so it fills the screen edge to edge.

*Admin page.* Cloudflare Access in front, plus the Worker verifies the Access JWT itself (signature, audience, email list). A misconfiguration can't leak the stats.

Total: one ~70 KB HTML file, no framework, about 150 lines of Worker code.

Happy to answer questions. And try to beat my 183 on NOT YOUR KEYS.

Here's the project: https://im.4xs.dev

(landscape phone, or desktop with the keyboard)


r/vibecoding • • 12h ago

Showcase/Project I Vibe-coded a full local community hub & directory for my city (Manchester, UK). Here’s what I learned.

Post image
2 Upvotes

Hey everyone,

I was tired of local community stuff being scattered across spammy Facebook groups and clunky directories, so I vibe-coded MancConnect — a hyper-local PWA for Greater Manchester (community notices, tram alerts, local job board, flatshares, and a vetted trade directory).

It ended up growing to 15 routes, so here’s the quick breakdown of how I built it without it turning into a broken mess:

The Stack

  • Vanilla JS (ES Modules) + HTML5 History Router: Skipped React/Next.js completely. The site loads virtually instantly on mobile 4G and works offline as a PWA.
  • Precompiled Tailwind CSS: Compiled via CLI so there's zero runtime lag.
  • Firebase (Firestore & Storage): Real-time DB with two-way cross-device sync (saves on mobile reflect on desktop).
  • Playwright: This was the cheat code. Whenever the AI refactored code, running automated tests was the only way to catch visual glitches and broken buttons before deploying.

2 Big Lessons

  1. Lazy-load heavy modules: My admin dashboard blew up to 300KB. Vibe-coding an async dynamic import() so normal mobile visitors don't download any of that code made a huge speed difference.
  2. Local businesses hate automated SaaS checkout: I was going to use auto Stripe card checkouts for directory ads, but local trades (plumbers, roofers, bakeries) actually prefer direct human communication and a manual invoice. Keep monetization simple.

The live site is at https://mcrconnect.co.uk.

Would love any thoughts on the UI, mobile performance, or how others are handling larger multi-page projects when vibe-coding! Bear in mind I am very new to this community.


r/vibecoding • • 18h ago

Meme Neon passed the test !

Post image
2 Upvotes

r/vibecoding • • 19h ago

Help/Question How would you get reliable reasoning out of a very small local model for a game assistant (Warframe builds & farming)?

2 Upvotes

I've played Warframe for 4,000+ hours, and I'm trying to build a local assistant that helps players with two things:

• Farming: finding where to get an item, and eventually giving the player a farming roadmap: what to farm first to reach a goal, in what order, and the most efficient way to farm a specific resource (best mission, expected number of runs, useful boosters or companions…).

• Building: how to build a character (mods, abilities, synergies) for a given goal.

I'm not an expert in this field, so I'd like to hear how people more experienced than me would approach it.

How I approached it at first

• RAG over the wiki: I exported the wiki into notes, and the agent searches them to answer.

• My own explanations: on top of that, I wrote more specific notes on how the game really works in practice. They cover things the wiki explains badly or not at all, like how mechanics interact, why some choices work together, or common traps. The idea is to make the agent more logical and reliable, not just able to recite stats.

It works well enough with a mid-size model (~12B), but the reasoning still breaks down quickly. The model picks things that don't fit together, repeats questions, or gets lost when the retrieved context is too long. And the goal is for it to run locally on almost any machine, so ideally with a much smaller model.

What I'd like to hear from you

  1. With a very small model (3–8B), what would you change in this design? Is RAG plus hand-written notes the right base, or would you approach it differently?
  2. Would you keep a single agent, or split the work into simple sequential steps (understand the request → fetch data → build or plan → check → explain)?
  3. The hard part is synergy, meaning knowing which elements reinforce each other. Is it better to encode that as structured data (rules, graphs, archetypes) than as free-text notes for retrieval?
  4. For farming roadmaps, would you let the model plan, or compute the plan in code (drop rates, dependencies between items, time per run) and only have the model explain it?
  5. Should the model be left to do any calculation or verification at all, or should everything factual go through code?
  6. Is a small fine-tune (LoRA) worth it here, or is it better to put the effort into data and tooling?
  7. How would you test the quality of something as subjective as "a good build" or "a good farming plan"?

Any idea, criticism or experience report is welcome, even if it's "start over differently".


r/vibecoding • • 5h ago

Showcase/Project Too lazy to doomscroll, so I turned my earbuds dial into a scroll wheel (+other features)

1 Upvotes

I am too lazy to scroll using my hands and I thought, why am I not trying to make something when I got opencode with deepseek 4.1 flash. So, 3 days later -

CMF Dial. The dial on the cmf buds 2 pro only speaks AVRCP absolute volume, so every click used to just change volume.

Now:

- rotate → scroll Reels / Shorts / TikTok / YouTube

- press / double press → anything per app: play-pause, like, next, flashlight, camera shutter, zoom, flip

- add any app to the scope, or just turn on "all apps"

- buds' volume stays pinned, so scrolling never changes loudness

~150 ms from detent to scroll. Root + LSPosed, no firmware flashed.

Bugs, and the fixes:

- swallowed the key-down only → the leftover key-up resumed YouTube Music. Swallow both halves.

- volume drifted, and the dial stalled at 0/100 → resync the buds to the phone baseline every detent.

- gestures took 1.5 s → a 500 ms sleep in the daemon was serializing the queue. Now queued, ~150 ms.

- tap-to-pause kept hitting Reels' play button → compute gestures inside the window bounds, not the screen.

Btw video generated using hyperframes


r/vibecoding • • 10h ago

Showcase/Project Melee Unlocked 1.0: FREE Ranked Mode, Unlocked FPS, Native PC Port of Smash Bros Melee

Thumbnail
youtube.com
1 Upvotes

r/vibecoding • • 11h ago

Meme Don't ever dispatch to sentient subagents xD

1 Upvotes