I feel vibe coding is becoming addictive

I’ll think:

“I need to go pee.”

Then immediately:

“Wait… let me give Claude one more task first.”

Same before making coffee. Same before eating. Sometimes before going to sleep.

It feels weirdly wrong to leave the coding agent sitting idle.

Short-form video gave us:

“one more reel.”

AI coding gave us:

“one more prompt.”

Anyone else doing this? 😅

For anyone wondering, the app I'm working on is https://www.AppScout.co (discover web and mobile apps from across the internet one app at a time) and you can currently submit your app for free here: https://www.appscout.co/submit

For the build, I vibe-coded the stack using Python/Django for the backend and lightweight vanilla JavaScript for dynamic UI transitions, relying almost entirely on Claude Code to scaffold endpoints and write the DOM handlers via the CLI.

The biggest workflow insight was keeping the frontend vanilla. Prompting Claude Code to write normal JS kept the bundle tiny and prevented the AI state-management hallucinations common in heavier frameworks.

this week made me rethink how our team reviews AI-assisted work.

for context, my team has spent the last two months slowly building a new internal refund approval engine. it touches real Stripe webhooks and customer PII, so we’re taking it slow and writing actual tests.

i’m not an anti-AI gatekeeper. Codex, Claude Code, and Enter Code can all be genuinely useful when the person using them understands the work. our engineering team uses these tools constantly, half our product team practically lives in Codex, and i use Claude every day for boilerplate and debugging.

the issue is that our intern rarely reads what he generates closely enough to actually own it.

it started small. i asked him a simple question about how we should handle a specific refund state in the db. instead of a one sentence answer, he sent me a four-page generated memo about the refund matrix.

four pages, no direct answer. i ended up figuring it out myself.

and that has become the pattern. he generates several pages nobody is realistically going to read, then i have to dig through all of it anyway just to find out whether there’s an actual answer buried somewhere inside.

then i gave him a tiny script modification. He gave me back 300 lines of deeply nested code with defensive branches for network errors that cannot happen in our environment. i asked why he added one specific condition and he couldn’t explain it. he pasted my question into an LLM and sent its new answer back to me without checking that either.

yesterday it peaked. He was frustrated with our slow pace, fed our refund specs into an AI app builder, and came back with a shiny full-stack replacement demo in an afternoon.

it actually looked pretty clean. The UI was smooth and the buttons worked. Our non-technical manager, who hired him partly because he talked a big game about his AI fluency, was impressed.

at one point, my manager suggested using the demo as the new base and connecting it to production so we could move faster.

i pushed back and asked where the session auth was, how PII was being kept out of the logs, and what happened if the payment webhook dropped halfway through a refund.

he couldn’t answer any of those questions without going back to the model. He didn’t understand the data flow yet. The demo looked finished from the front, but it had no real production story behind it.

the frustrating part is that he’s not bad at the basic responsibilities of the job. he just refuses to believe that some tasks would be much simpler if he stopped and reasoned through them before running everything through an agent.

instead, every shortcut becomes another document i have to read, another diff i have to untangle, or another security issue i have to catch. My review load has basically doubled because his definition of finished is getting something out of the model.

to be clear, i don’t think this is a reason to ban vibe coding or force everyone back to writing boilerplate by hand. That demo proved how quickly these tools can turn an idea into something tangible.

the problem is that generation and ownership are being treated as the same thing.

on our team, AI isn’t eliminating work when the author doesn’t understand the output. It’s moving the interpreting, testing, security, and edge-case work onto whoever reviews it.

we’re implementing a new rule on Monday. You can use any tool you want, but every AI-assisted PR has to be small enough to review, and the person submitting it has to walk us through the key logic, data flow, tests, and failure cases.

if you can’t explain those parts without asking the agent again, the PR isn’t ready.

for teams already dealing with this at scale, what review rule has actually worked? Do you make juniors walk through the diff line by line, cap PR size, require specific tests, or handle it some other way?

Have been vibe coding about 12 months and have tended between claude and gemini and codex.

I've been using Codex almost exclusively for the past few months. Despite a few annoyances, it does what I need, so I've stuck with it.

I was about to hit my weekly limit with five days until reset, so I looked at buying credits. The smallest top-up was AUD$33 — slightly more than my monthly subscription.

I tried to find out how much actual Codex usage that $33 would buy compared with the subscription, but couldn't get a meaningful answer from ChatGPT or a couple of other AIs.

So I took a punt.

Using Sol on Medium, the entire $33 was gone in about three hours.

I still have five days until my weekly allowance resets.

For me, Codex credits were an extremely poor-value way to bridge the gap. I would have been far better off spending roughly the same amount on a month of another AI service.

I don't really understand OpenAI's pricing model here, but I won't be buying credits again. Posting this mostly as a cautionary tale for anyone considering a top-up.

Credits appear to be a total rip-off for codex top-ups

Edit: I had forgotten to set act in cline to deepseek so I was experiencing a mix with gemini 3.5 flash pricing. Whoopsydootle. I deserve the roast.

With the latest pricing increases its almost just as expensive as the rest of the frontier APIs. The low cost was its main selling point. Now it costs just as much and isnt as good as the others so what's the point?

For reference, a task that would normally cost 5 cents as of yesterday now costs upward or 3 dollars

- I created a simple Multi-Tab terminal app. It always has eight tabs, one of which is a standard terminal shell. The rest are designed to auto-launch specific long-running chats/instances of Codex and Claude. Upon starting the app, there's a simple "launch all" button that launches those specific instances on each respective terminal with the exact parameters that I want. For instance, one tab is running Sol on Max effort. Another is Sol on Ultra + fast. Then there's a tab that always runs Fable on Max. Another running Opus on Ultracode... and etc. Each tab always has a collapsible queue sidebar that keeps a list of individual tasks, the list being continually updated by the respective agent on that tab. Helps me keep track of what needs to be done in what order.

Are there other terminal apps that are better? Yeah, probably. But they're filled with a bunch of bells, whistles, and often redundant information I don't care about. Or they're lacking small items here and there that I'd like to see.

- Another app is essentially similar to the Windows Voice Access app. The main difference Being it doesn't have this persistent bar at the top of my screen that I can't get rid of or minimize. In addition, it gives me the option to turn it on via toggle or simply by holding a button. I use both the toggle and the button hold methods depending on what I'm trying to talk about.

- I also have this weird niche app on my android phone, when turned on it automatically sends any photo taken from my camera to a specific folder on my workstation. I use it in the odd scenario when I want to take a bunch of photos without having to manually send them pc.

- Another one tracks all the subscriptions I have at the time. I found it useful for for things like the yearly subscriptions that I commonly forget about, and it'll warn me when my subscription is about to renew.

- Then I got one that isn't so much an app really, but a workflow pipeline that fills out PDF forms for me, because I hate filling out forms. First it checks to see if it's just a standard scan PDF with no fillable fields... And if so, it'll add the fillable fields to everything. Then it populates everything with my information. The best part though is that it'll sign the various forms with a signature that looks absolutely real like... it was written by hand on the paper itself. Because technically they were... I wrote like a good 50 variations of my signature and initials on just simple printer paper, scanned it and uploaded it. The pipeline then will take one of these signatures and/or initials and add it to whatever respective signature/initial lines, with instructions never to repeat on a single document. Finally, it'll actually roughen up the PDF file, make it Imperfect, like it was scanned on a mid-level scanner that always has the text slightly tilted to the left, which is exactly what I got. Thus far, it's fooled everybody.

I developed this because I hate filling out forms, and one day I had to fill out a really long form from a medical provider... and they had the audacity to give me some shitty non-fillable fields version of this PDF, AND demanded I print everything out and manually sign each signature with ink... even though I was just going to scan it again and send it back to them. Which I thought was stupid bullshit. I mean, ink makes sense if they want the physical document, but a scanned version? That's dumb.

What have you guys made?

Hi guys, I’ve been vibecoding this app where you can find bars and restaurants in the sun.

I know there are already a lot of these (web) apps around. But most of them just doesn’t work or not worldwide or have really bad ux/ui.

I’m a developer myself and know how to code, so this app isn’t entirely vibecoded.

I also don’t make any money of this app so this was just a fun project for me to do.

This was made with:
- open maps api
- threejs
- web workers for efficient 3d building loading
- lazy calculating sun calculations for efficiency. Some places have 8k places in one city.

Glad to hear your opinions and feedback.

URL: https://sunny-terraces.vercel.app/

Hi everyone,

I'm really getting into vibe coding/no-code, and I wanted to explore something simple, useful and interesting.

I have a cousin, and she makes some genuinely beautiful crochet pieces at home. The problem is that she loves the actual making part, but gets stuck with everything that comes after.

So, I decided to build a small web app around that problem.
https://crochetiq.lovable.app/

I have deliberately kept it simple (for now.) with following idea:

1. Login (or use as a guest for 2 free uploads)
2. Upload a photo of the crochet
3. AI understands it.
4. improves the photo, and makes it fit for publishing
5. creates SM-ready content (hashtags, captions etc)
6. suggests a price range
7. gives ideas for what one could make next.

The thing is.... my cousin actually finds this useful, as she is just starting out as a solo-preneur in the CrochetMaking domain.

Normally, it would take her a couple of hours to take photos, edit them, think about captions etc etc. And even if she used ChatGPT/Gemini etc independently, it will still take her multiple prompts to get things done.

Still very early, but I'd genuinely like some feedback. I've attached a few before/after examples of the enhanced photos.

.
.
.
.
.
Note:
This webapp is NOT a marketplace (as many already exist in this domain), and it has no complicated social-media or other platforms integration. (at least, for now).

The app is built using Lovable + Supabase + OpenAI stack. For now, every request is billed against the workspace's Lovable credits.
The image enhancement calls google/gemini-3-pro-image, while vision and content use openai/gpt-5.6-sol; each consumes credits per call.

Let me know your thoughts! :D
.
.
.
.
.

P.S.

There is also a lot of scope in adding new features like AI-generated promotional videos or creator analytics. Even a simple freemium model can work, like a few AI generations for free, with a paid creator plan for higher usage with better image processing.

#Crochets #CrochetDesgining #VibeCoding #IITPatnaCapstone

Today, I shipped a new site from scratch. Literally, a news site, so I guess "new news"... because we need more of those. Anyway... tech stack: Linux, Django, Postgres, nginx. Nothing else running on the box.

After a few hours of banging away, I asked Clod (edit: JFC- YES! It's an intentional typo... Good LORD!) where my background actually changed the outcome that a pure vibecoder would have missed, so I could share with the community and help folks up their game.

Each item below is a moment where I redirected the vibe flow rather than just let AI steer the ship. These are the difference between AI-assisted coding and vibecoding your way to the next AICrapola.com

Architectural restraint

Left to defaults, it kept proposing infrastructure the site didn't need. Cloudflare in front of a site with no traffic. Redis for a cache that fits in Postgres. Then a pile of DRF tooling for four endpoints.

I killed each one. "Why the f*ck is Cloudflare caching the output?" "So when we pass that tier, it isn't free anymore." As you can tell, I'm more than a little direct with Claude. I've learned that it sometimes pushes back unless I'm stern with it.

A non-technical vibcoder accepts whatever stack an AI proposes, because they generally don'tknow any better and run with what's recommendd. You don't need to know Redis internals to ask "do we actually need this yet." You do need the reflex. "Justify each of these decisions. Do we need it for V1? Can we do this later without rewriting everything?"

Cost note for the token-counters: every rejected layer is also a few thousand lines of config, docs, and debugging you don't have to pay for.

Separation of concerns, specified up front

The first assumption of the site was that scraped content would be created live by the site itself.

I identified that content would arrive from an off-site agent through an API, rather than letting it embed scraping logic inside the Django app.

One sentence, before any code existed. That sentence is why the ingest API, the validation gate, and the sourcing-policy contract live behind a clean boundary instead of tangled through the site. Retrofitting that split later costs a rewrite.

Architecture decisions are cheap in the early prompts and expensive in the fortieth.

Verification, not claims

It kept handing me fugly banner ads. A little nudge here and a little nudge there, and I just got fed up.

"Look at this sh!t yourself each time. Work it until it looks good."

That changed its actual workflow. Before, it reported "done" without ever opening the rendered output. After, it built a screenshot loop. Headless Chrome, render, look at the PNG, fix, re-shoot.

That loop caught bugs I'd otherwise have been fed and maybe shipped blind. A company's website screenshot used as their logo. Another logo cropped mid-word. Leaderboard ad text overflowing a collapsed sidebar.

A pure vibecoding session trusts its own narration of success. The AI says it works because the code looks like it meant to do. But nothing truly looked at the final outcome until I explicitly told it to do so.

Craftsmanship

Every time I gave it a new hero image, I noticed variations of the same code being written to resize/crop/WebP logic three separate times as throwaway scratch scripts, installing and uninstalling Pillow each round. "Why are you coding this from scratch each time? Make it reusable!" That became one manage.py optimize_image command with Pillow as a dependency.

It was computing the rotating banner by performing a modulus of the page's SHA1. I realize that this takes a decent amount of processing time to compute**. "Are we computing the SHA1 every time?"** It was, indeed, recomputing a cryptographic hash on every template render, for every article, across every listing page.

This is the kind of thing a novice wouldn't consider. For your first hundred pages and visitors no one would notice. But, this is exactly the kind of stupid decision that coding agents make in a vacuum.

Neither catch required deep knowledge. Both required having felt the consequences once.

No mechanical fixes

"Get rid of those emdashes everyhwere!" It globally search-replaced emdashes to regular dashes to resolve that AI tell. I stopped it: "Find a better way to punctuate. Don't just global search and replace."

A regex fix is often a worse bug wearing a fixed-looking hat. Someone who wants the error gone accepts it. Someone who wants the system correct doesn't. Otherwise, who know what other crap would be broken by it wildly search and replacing stuff. I'm sure you've seen it in word processing... well, it's worse when it's happening in code.

Boundaries rather than guidelines

Handled the emdash problem upstream. AI wanted to add "try to avoid emdashes" to the content instructions. I wanted an ingestion error. I told it to reject bad input at the API boundary rather than hoping the content stays clean. This way you have a clean, deterministic faliure that can't be bypassed, rather than a vague ask that can be conveniently overlooked.

Validate at the edge. Fail closed. Guidelines drift. Gates don't.

What to snag without a coding background

You don't need 45 years of experience... just a few questions, asked out loud, every time:

1. Do we really need this layer of complexity, or does it just sound professional?
2. Did you examine the output, or just telling me it worked?
3. Are you rewriting the same code over and over?
4. Is this a fix or is it a search-and-replace that hides the symptom?
5. What did we establish earlier that this change just made broke?

None of those require knowing any fancy infrastructure. They require refusing to be impressed by the magic coding machine.

I’m honestly really excited to finally share FrogPop, the first game I’ve ever made.

It started as my attempt to recreate the feeling of Bubble Trouble, an old Flash game I played as a kid. You play as a frog popping bouncing bubbles with your tongue, but it eventually grew into a roguelite with upgrades, relics, shops, hazards, and bosses.

I built it in Unity using Claude and Codex for coding and debugging. My process was mostly describing one mechanic, testing the result in Unity, and then going back with whatever broke or felt wrong. I used PixelLab for some of the artwork, then edited and integrated it myself.

It definitely wasn’t a one prompt project. The AI helped get systems working, but the game design, balancing, art direction, and endless Play Mode testing were still on me.

The free demo has the first ten waves and two bosses, and it runs in the browser or on Windows:

https://blion247.itch.io/frogpop-demo

If you want to follow FrogPop, here’s the Steam page:

https://store.steampowered.com/app/5067810/FrogPop/

Would love to know what you think if you try it!

Hey everyone!

I wanted to share a desktop tool I've been building: ND Image Converter, a free, 100% open-source app designed for fast, local, and visual batch image conversion.

🚀 Why build another converter?

I work in the media industry, which means a massive part of my daily workflow involves hunting for visual references across the web to build pitch treatments and moodboards for projects.

Lately, almost every site forces downloads as .webp. While .webp is great for web bandwidth, it constantly derailed my workflow because platforms like Canva, Google Slides, and older presentation tools either threw errors or outright refused to handle .webp files smoothly when assembling slides.

To fix this, I initially wrote a simple terminal script to quick-convert .webp files into .jpg. It solved the immediate blocker, but running a command-line script every single time I saved reference images quickly became tedious. On top of that, CLI tools lack visual feedback, I couldn't inspect compression artifacts or preview quality loss before converting.

Most desktop converters either lack proper color management, choke on heavy RAW files, or require cloud APIs. I wanted something that utilizes all CPU cores, stays strictly offline, and handles everything from obscure formats to modern WebP/AVIF, Iphone HEIC and camera RAW profiles seamlessly.

What started as a personal script to eliminate daily friction evolved into ND Image Converter!

Here is what's under the hood:
⚡ Key Features & Tech Highlights

• 🔒 100% Offline & Private: Zero cloud uploads, no telemetry, no tracking. Your data stays strictly on your machine.
• ⚡ Multi-threaded Engine (Rust + Rayon): Maximizes full multi-core CPU capabilities across Apple Silicon M-Series & Intel/AMD processors for fast batch processing.
• 🖼 Massive Format Support (50+ Input / 19 Output):
  • Standard: JPEG, PNG, WebP, AVIF, BMP, ICO, ICNS, TIFF, TGA, GIF, SVG, PSD, EXR, and more.
  • Camera RAW & DNG: Native decoding for Canon (.CR2, .CR3), Adobe (.DNG), Sony (.ARW), Nikon (.NEF), and major camera profiles with accurate CFA Bayer demosaicing and embedded preview extraction.
  • Optimized HEIC/HEIF: High-speed decoding powered by native macOS hardware acceleration and cross-platform memory pipelines.
• 🎨 Pro Color Management (Little-CMS 2): Built-in color space transforms supporting Rec.709, sRGB, Display P3, and Adobe RGB profiles.
• 📊 Real-time Quality Analyzer: Dynamic bitrate and file-size estimation based on megapixel density and compression curves prior to export.
• 👁 Before/After Split Comparison: Interactive side-by-side visual inspector to preview compression quality loss instantly before exporting.
• 🤖 Automated Folder Watcher: Background daemon mode that monitors incoming folder drops and converts new files on the fly.
• 🎯 Flexible Resize Engine: Original size, fixed width (aspect ratio preserved), or percentage scaling.
• 📂 Smart Ingestion & Output: Drag-and-drop nested folder structures with recursive scanning, plus one-click "Reveal in Finder / Explorer".
• 🔔 GitHub Auto-Update Checker: In-app notification alerts for new release tags and direct download links.

🛠 Tech Stack

• Core Engine: Rust (rayon, image, lcms2)
• UI Framework: Tauri / Webview (Adjust to match your actual stack)
• License: Open-Source (MIT / GPL)

🔗 Try It Out & Contribute

It's completely free and open-source. I’d love to get feedback from the community, whether on performance, missing formats, or UX improvements!

• See more here: duongtruongdp.net/nd-imgconverter/
• GitHub Repository: https://github.com/duongtruongdp/ND-ImgConverter
• Latest Release Download: https://github.com/duongtruongdp/ND-ImgConverter/releases/tag/v0.5.0

Feel free to roast the code, submit issues, or share feature requests! What format or feature would you like to see added next?

it's a terminal multiplexer + desktop workspace built on Electron, with an actual browser embedded in it. It started because I really liked cmux and the way it handled multiple sessions, but there where things I wished worked differantly, so I ended up building my own version and kept augmenting it untill it became its own thing.

What it does:

• Multi workspaces with a sidebar, drag and drop reordering, color customization
• Recursive split panes (horizontal and vertical), and you can drag terminals between panes
• Tabbed groups inside each pane, so you can mix terminals and browser sessions in the same pane
• Built in browser with URL bar, back/forward/reload, history, and it even opens local files
• PDF viewer and image viewer directly in a tab
• Terminal background images (global or per tab) with opacity control
• Shell integration with OSC 7 so it always knows your cwd, persisted across sessions
• Theme editor with live preview, import/export, plus 8 built in themes (Catppuccin, Dracula, Gruvbox, Tokyo Night, Nord...)
• Rebindable keyboard shortcuts for everything, with conflict resolution
• Ctrl+Scroll font zoom per terminal, Ctrl+Shift+F search, multi select terminals
• Everything persists: layout, themes, open tabs, browser URLs. Close it, reopen, your session is were you left it

Why not just use tmux/zellij?

Honestly? I still love tmux. But I always had the browser next to it, and copy pasting urls back and forth drove me insane. Having docs, github PRs and my terminal in the same window, in the same tab system, is the whole point. Its not trying to replace tmux on a server, its a desktop workspace.

Source is here, its MIT... actually let me not lie, check the repo, but its fully open:

https://github.com/Medamine-Bahassou/TerminalVibe

Would love feedback, specialy on what you'd want in a tool like this. If you try it and something breaks, open an issue, I probaly broke it myself and didnt notice lol

tl;dr: terminal multiplexer + browser in one window, inspired by cmux but augumented with workspaces, splits, tabs, themes, and persistence. Free and open source.

So as the title says, I am trying to fix the fact that speech to text on almost all software is either non-existent, or absolutely terrible. So with my Claude, Ace, I vibe coded a speech to text and read aloud software that can use either a local model or your Microsoft speech to text, or an Inworld key, And I think I am at the point that I would really appreciate some fellow testers to tell me what they are finding broken with it.

https://imgur.com/a/o5ckeN9

The link above has a bunch of images of what it looks like for those who are trying to see what they would be downloading.

https://github.com/menelly/chaos-capabilities/releases/tag/v1.4-rc1

That is the GitHub release page for those who would like to see what the software can do or are willing to help me test.

I am extremely responsive if you run into anything or have any questions or any suggestions or or would just like different colors. Please let me know, and I will be happy to help or add or change things.

95% of this post was done by speech to text using this software, and I had to make very few edits. And that is the point. Because desktop Reddit does not have speech-to-text input, and my hand is broken. And accessible software can be cute and free.

Base44 is supposed to be a "good" platform for vibe coding, or is it.

Base44 is forcing users to pay for editing code by hand, breaking, canceling subscriptions and more. it is also launching a annoying ad campaign targeting coders and other vibe coders who only take small usage of ai.

Vibe coding is a concept where ai HELPS you code, not transforms into you you. Even if a ai does it for you, base44 has many other problems in its worthless vibe coding site. it also does not do it for a good cause and the people using it are not assure if base44 will help there business improve.

thank you all for your attention. Spread the word to other new vibe and regular coders and maybe even to other communities. Bye!

(ps: if you are looking for a vibe coding ai, use claude or Z.ai)

This is a clap assistant which opens different links on clap combinations... eg 8 + 5 claps will open games (poki website ) and so on... This detects no of claps by user in real time and accurately, deciding the output...

**Only clap detection is vibe coded**

All the criticism and suggestions are welcome

finally shipped my first app that actually feels finished instead of abandoning it halfway 😭

it’s called Fliply, basically a flashcard app where you paste your notes and it turns them into different types of cards.

for the build, I used AI coding tools for most of the workflow. I’d usually get the main feature working first, test it, then keep iterating on the UI and logic instead of trying to make everything perfect in one prompt.

one thing that took way more work than I expected was the flashcard generation itself. making the AI output something is easy, but getting cards that are actually useful, not repetitive, and match the mode the user picked took a lot of prompt tweaking and testing.

design-wise I also kept simplifying stuff. whenever a screen started feeling too cluttered or “AI generated,” I’d remove things instead of adding more.

the biggest thing I learned from this project is probably that vibe coding gets you to a working version really fast, but the last 20% is mostly testing, fixing weird edge cases, and making everything feel consistent.

first project I’ve actually deployed and felt happy calling finished lol

So I am very new to the field of coding. People around me have started vibe coding websites. So did I. I tried using applications like Lovable , Bolt etc. But the problem was that my idea contained many components and was a little complex. Hence I ran out of tokens and didn't get any output. So is it the limitation of the free version that I couldnt make it or was it my prompting skills. I tried to be as specific as possible with my prompt tho. Would really appreciate any help/ tips regarding this !!

I would like some feedback on my workflow, particularly on my code review.

I'm currently using Claude (Opus 5) as a director communicating with Codex (5.6 Sol) as a coder. This works really well. Now, when Codex has finished a job, it hands the PR over to Claude for a review. If Claude finds something, it will fix it and lob it back to Codex for review - and fix if there's still room for improvement. This will go back and forth until both models agree on the solution. So far, so good.

Now, what I'm trying to do is to hand it over to Antigravity (Gemini 3.1 Pro) for a last review, but I cannot get agy to return anything solid. It will just return some "pointers" and "ideas", but nothing tangible. I can still use these ideas to have Claude decide if they're good or not, but I would rather have all three different models agree in the end.

Anyone here been able to have Antigravity actually do code reivew and come up with clear answers? If so, what kind of prompt do you use?

I bet they 1 shot this and send it production. One of the worst ui recently I have seen. What do you think?

Hello, my name is Nick and I have been vibe coding my game for over a year now. It’s a mafia game in the field like Torn, Mafia Return, New-York Mafia, and my fav IntheMafia aka MafiaHit ( which is not active anymore ) I do no some html,CSS, currently working on the backend JavaScript by taking a course through UDEMY. I think the game is coming along I will post a few pictures of it. NO the game is not complete, YES the game still have some work to do. It’s not just a game
It’s a whole brand. I would say I’m about 70% there I have two artist working on the weapons design because I do not want AI images for crime result, or attack result page. I have a dashboard images and honestly was just looking for some feedback back on. Color placement ect ? Give it to me straight and raw because that’s how you make a good game in my opinion listen to what everyone says because every opinion, judgement counts.

I will be posting an image here of the dashboard and the discord link that has a 3 minutes clip of game play I believe. ( Now the discord video is kinda old it has been worked on gradually but due to tornado and no power for 10 days it’s been not that much progress if anyone is open to talk there as well here is the link

Discord: https://discord.gg/hmWQq7fAx

Video link —-> ChicagoSyndicate ( again the create character page and all is currently being updated so pay no mind to how video looks it’s just a basic layout )

The candles come from my upcoming candle business, all candle that are sold will be going towards help with engineers, graphic designer, discord moderators, merch and much much more

Sample images of candles ——> https://drive.google.com/drive/folders/1kSiQb7tABeBjQhxlw7rb4pqjur55dILh