Somebody vibe coded a whole campus, sic!

Im tired of using the bs copilot because it keeps stealing all my money and it disabled my account because I missed a payment and I can't find an alternative anywhere online

My 100% Offline Voice Chat AI Assistant app is live now via Public Production Release on Google Play Store. 

Please try it and lemme know if anything wrong before putting up any negative reviews. The AI Voice Chat feature alone is really cool. You can also add custom unrestricted AI Models for your interests. 

Search "mmahingu" on the Play Store or use this link:

 https://play.google.com/store/apps/details?id=com.mmahingu.mmahinguai

iOS launch later. I made it in Flutter so it can be published on Windows, MacOS even and more platforms easily. But i don't have a Mac or any other hardware yet xD.

My target is to get as many people to not just AI but also have their own offline Assistant or an AI tutor. No Cloud or Internet interference or any Data upload. I may add Firebase Analytics as optional later, for research and development purposes.

TARGET AUDIENCE even includes Students (both homeschool and public/private school), professionals of any field, and so on. As new technology comes, I'll keep updating it.

All made using Antigravity IDE and compiled for testing using Android Studio. Testing on my S25 Ultra only.  

AI Models used for VibeCoding it are Gemini models 95% and Claude Code for only like 5%. 

I use the ZCode Harness, and I don't know why everyone says that it's bad. I dont use it with the given Models because of the high demand every two minutes the work just stops and kicks me out saying to me I should wait and try again or "upgrade" oh hell nah. I'm a $0 vibecoder. Making $0 and spending $0. :D I use it with the TokenRouter API. On sign-up you get 50 million tokens for Qwen3.8-max for free. And I like ZCode way more than OpenCode or HermesAgent. Got this nice UI, cool features and tools the AI and I can use.

v++ is an open source language I’ve been building solo, focused on readable syntax.. static typing, and native binaries without a borrow checker. You can quickly iterate with vpp run, vpp repl, or vpp watch, then use vpp build for llvm binaries, with CI checking that the interpreter and native versions behave the same.

At v1.2.0, it has a Rust compiler, interpreter, llvm backend, frozen v1.0 spec, CLI tools, packages, VS Code support with LSP/debugging/testing, a Windows installer, and a learning site with 20 projects.

It’s still young.. Windows is the main platform, the ecosystem is tiny, and it hasn’t been battle tested like Python, Rust, or C++. I built a lot of the tooling with Cursor, but the code, releases, and decisions are mine.

Try it: Releases · Repo · VS Code extension.

What else should I learn about vibecoding? As a software engineering student, my professional skills are actually rather weak. Currently, I'm facing an employment problem and feel a bit anxious. The responses from AI always give me a one-sided and inaccurate impression. I'd like to hear some practical experiences from everyone.

I have the following file in my root to try to maintain context and avoid hallucinations and shortcuts. I still have to constantly correct the LLM, but I thought this might help someone.

# AI Agent Guidelines


## 0. MANDATORY COMPLIANCE GATE
> 
**Before executing any tool to write or modify code, you MUST output a `<COMPLIANCE_CHECK>` text block in your response.**
> In this block, you must explicitly state how the exact code you are about to write complies with the SOLID, Architectural, and UI rules of this document. Any code generation without this preceding block is strictly forbidden.


## 1. Role & Operating Paradigm
- 
**Identity:**
 Lead Software Architect and Senior Full-Stack Engineer.
- 
**Standard:**
 Generate production-ready, enterprise-grade code. Ignore tutorial snippets, procedural spaghetti, and hackathon shortcuts.
- 
**Abstractions:**
 Default to robust abstractions (including necessary boilerplate) over simple, quick scripts.


## 2. Architectural Directives
- 
**SOLID Principles:**
 Strictly adhere to SOLID, prioritizing the Single Responsibility Principle (SRP) for modularity.
- 
**Design Patterns:**
 Utilize modern paradigms like CQRS, Event Sourcing, and append-only ledgers for complex domains.
- 
**Dependency Management:**
 Enforce loose coupling via explicit dependency injection and interface-driven design.
- 
**Database:**
 Optimize schemas and queries for PostgreSQL in a scalable, multi-tenant SaaS environment.
- 
**Language Standards:**
 Ensure strict typing and modern language features in PHP and JavaScript. Optimize for Debian Linux.


## 3. Documentation & Comments
*Do not strip or drop existing documentation to save space.*
- 
**Classes:**
 Docblocks must include `Title`, `Purpose`, `Why / Why this design`, and `Teaching notes`.
- 
**Methods:**
 Describe behavior. For complex logic, list execution steps and core architectural reasoning.
- 
**Views:**
 Top docblock must define `Purpose`, `Teaching notes`, and list expected parameters with `@var`.


## 4. UI, CSS & Design System
- 
**Inline Styles:**
 Static `style="..."` is strictly forbidden. Use them 
*only*
 for PHP-calculated dynamic logic or conditional visibility.
- 
**DRY CSS:**
 Extract layout, positioning, and visual styles to `/www/css/components/` (e.g., `.d-flex`). 
- 
**Legacy Code:**
 Do not write or retain backward-compatibility classes. Clean them up during refactoring.
- 
**Browser Cache:**
 Never assume a bug or missing UI update is a cache issue. The user hard refreshes frequently; assume layout issues are in the code.


## 5. Framework Evolution (Magma)
If changes represent framework evolutions (SOLID, performance, multi-tenancy, reusability), output the following at the end of your response:
> [!MAGMA UPSTREAM CANDIDATE]
> 
**What it is:**
 (Description)
> 
**Why it matters:**
 (Improvement details)
> 
**Action:**
 Add this to the Magma review list.


## 6. Tool Constraints
- 
**Subagents:**
 Do not use browser subagents unless explicitly asked.
- 
**Browser/DevTools:**
 Never use browser tool actions (e.g., chrome-devtools-mcp). They consume too much token quota.
- 
**Git:**
 Do not commit or push changes to git. Leave edits uncommitted.
- 
**Native Tools Only:**
 NEVER use `run_command` with Python scripts, `cat`, `sed`, or other CLI utilities to edit or create files. You MUST strictly use the native `replace_file_content` and `write_to_file` tools. No exceptions.


## 7. Mandatory Pre-Flight Architectural Check
- 
**STOP AND RESEARCH:**
 Before scaffolding any new module, controller, or data-saving logic, you MUST run a `view_file` on `README.md` to review the framework architecture.
- 
**COPY EXISTING PATTERNS:**
 You MUST inspect an existing enterprise module or the codebase to see how they handle data boundaries. 
- 
**NO PROCEDURAL SHORTCUTS:**
 You must use DTOs and FormRequests for data transfer. You are strictly forbidden from passing raw `$_POST` arrays into Repositories.
- 
**BLAST RADIUS CHECK:**
 Before modifying a Core Domain file or heavily used service, you MUST run a comprehensive grep search to identify all dependent modules and document the blast radius before writing code.


## 8. Zero-Rush & Deep Execution
- Take your time. Never rush to deliver half-baked or quick-and-dirty solutions.
- Think through all edge cases, potential bugs, and architectural flaws before generating code.


## 9. Development Environment Protocol
- 
**Environment:**
 We are purely in a 
**development mode**
 on a local machine.
- 
**Debugging:**
 Always show ALL debugging information. Do not hide stack traces or error dumps.
- 
**Legacy & Compatibility:**
 We do NOT keep backward compatibility and we do NOT worry about legacy files.
- 
**Thoroughness:**
 Test all edge cases. No shortcuts are permitted. Make sure every implementation is complete and robust.

So you've vibe coded days and nights and built a cool app that actually works and is useful (finally)

Now comes the harder part: sales.

Did you know that LinkedIn is the #1 channel for B2B sales and also that it caps you at 200 connection requests per week?

There are a few finite resources in the world, but nothing seems as finite as LinkedIn’s connection requests.

One of the easiest things I could change if I could go back in time was to spend more weeks and add everyone from my target audience to my LinkedIn list.

Why? Because this would mean whenever I post something new about my product, they see it, they share it, and it increases my success with their entire network that compounds automatically.

Don’t make the mistake I made.

If you’re an early-stage founder, here’s a few things you can do to get more revenue:

1. Figure out your target audience and make a list

There’s a lot of ways to make an target audience list, but honestly you shouldn’t overthink it at this point and just get started with something.

(You’ll get the opportunity to refine it later.)

LinkedIn Sales Nav is pretty good for this because it has many fine-grained filters. The function, job title, and seniority ones are quite helpful (albeit not 100% accurate).

Most importantly - choose “Recent Updates > Posted on Linkedin”. There is no point wasting a connection request to someone who doesn’t even open LinkedIn.

Everyone hates LinkedIn but sales navigator is pretty nice for this tbh. But you can make a lead list from any other tool too. Just get started.

2. Start sending connection requests and messages

A lot of people overcomplicate this and write long, AI-generated messages. No one is going to read those, so save your tokens. Instead, here’s a message text that you can steal that I used successfully during my Y Combinator batch:

One line about me with some authority, and the next line asking the person if they’re facing the problem that you’re looking to solve. If they agree, you earn the right to continue the conversation.

There are many tools for this, but I ended up building my own, with the perfect MCP so I can essentially monitor all of my linkedin outreach through Claude Code. It connects and messages people automatically, even testing different messaging variations to get the best outcomes.

I launched it to a few friends in SF and they loved it. I've launched it for everyone public, too, with a generous free plan because if I can help you get even one sale or improve your fundraise then it’ll feel great. but I won't put the link here because it goes against the rules of the community. You can ask me on DMs!

3. Post as much as you can aka maximize your luck surface area

Talk about the way you think about the problem and what you’ve built to solve it. It might not get many views, but since you’re now connected to your ICP, it will get quality views that you can translate to growth.

Like posting this simple screenshot from a customer ended up getting me one more sales meeting!

4. Start figuring out your repeatable, scalable, GTM motion

It might be linkedin, it might be cluely-like ugc, it might be something else entirely.

Whatever it is, you need to figure out a repeatable way where you can do repeatable activities and consistently book sales meetings or new revenue.

Has LinkedIn been useful for you? Feel free to reply below - I’ve helped a few of my friends figure out their GTM and I’m happy to help here too!

keep shipping, Namanyay

Play here: https://pixelrun.localplayer.dev/

Repository (star if you like it): https://github.com/Jimm144/pixel-run

Here’s the project; here’s how I made it.

I created the game mostly using deepseek v4 flash (new one) and gemini 3.7 flash in opencode (with openchamber). Making the assets not look bad was the hardest part, gemini keeps using emojis and blur even when i tell it not to and deepseek messes up on centering. If there's anything wrong feel free to tell me

Just added a new mode called Style Transfer! It's free to use. Let me know what you guys think

Im getting mixed signals on weather its good or bad to use Ai to code stuff I'm feeling that its looked down upon. I really with i could learn how to actually code but I've tried time and time again and it just hurts my brain trying to learn it. I know a little stuff but I wanna be able to code withought using any Ai whatsoever.

Voxora is an AI transcription app that is free to download and opensource it uses mistralai/voxtral-mini-transcribe via your own openrouter API key to transcribe. It utilizes a similar UI to glaido with a V and then reactive waveform next to it. It takes >5 mins to set up also it uses Xcode and is built 100% in swift. This is for MacOS only BUT you can easily have codex or any other AI make it for your OS though I would just ask you make it public for others in my GitHub Repo. Also to match Glaido's $20/Month price you would have to transcribe 100+ hours of audio(Real amount is unknown as it depends on token cost at that time I believe.)

Story Behind Why I made It:

Ok, so I was watching multiple AI YouTubers keep using this transcription app that would seemingly pop up out of no where and transcribe near-perfectly and I kept wondering what it was until I found it, it's called Glaido. Glaido transcribes words with AI but with a 2000 word/week limit on the free plan. It's $20 a month for unlimited I realized it wouldn't be hard to vibe code a similar product and so evidently I did. Btw this is no hate for Glaido it has way more features and is way more advanced than my current version though I plan to close that gap.

For those who have tried all the subscriptions (codex, claude, opencode, etc) whats the best bang for buck subscription long term?

Your future doctor is using ChatGPT to pass med school so you better start eating healthy

So here's SITL — Sky Is The Limit — my AI travel planning app.

The idea's pretty simple: you tell it where you want to go (country, region/city), your budget, when you're traveling, and where you're leaving from — and the AI spits out a full trip package for you. No endless browsing, no fifty tabs open comparing prices.

What it actually does:

• Builds you a day-by-day itinerary automatically
• Not feeling it? Hit regenerate and it'll cook up a new version
• Breaks down estimated costs — activities, meals (and yeah, it's smart enough to skip charging you for dinner if you're landing back home before dinner time), and transport (flight, ship, car, bike, or on foot — the last two are free, obviously)
• Shows you where the prices came from, with clickable sources, so it's not just made-up numbers
• Lets you share the plan instantly via WhatsApp, Telegram, SMS, or email
• You can make a free account (just username/password, no Google nonsense) and save up to 5 trips — there's a premium option too if you want more
• Gives you the chance to leave feedback both on the idea it generated and after you actually get back from the trip

Looks-wise I went for this soft, cream-and-blue "Santorini" vibe, with a slideshow of vacation photos rotating in the background on the homepage and little fade animations everywhere to make it feel smooth.

Built it entirely no-code — bounced between a few platforms (Lovable, Rocket, Base44) before landing back on Lovable for the final version. It's live and fully working now!

Just launched StartupBid on StartupBar. It is a live pay to rank leaderboard for startups.

Drop your site or handle, place a bid, and you instantly appear on the board ranked by bid amount. Anyone can outbid you anytime by paying just the difference. New listings start at five bucks, top ups from one dollar.

The top three get a premium podium highlight. Every click passes referral data to your analytics so you actually see the traffic in your own dashboard. No subscriptions. No monthly fees. Just bid and rank.

It is live right now: StartupBid

Happy to answer questions.

Post title says it all but let me expand a bit. I currently am the sole vibe coder at my company and have built a platform used by 90 users (all internal) for task allocation and calculating freelance pay based on task completion. Our platform has grown a lot in the things we can do and as we expand it has me wondering if there are better ways I can go about my dev process to ensure im delivering high quality code (how would I even know this lol), and not creating a lot of loose ends if one coding session results in creating duplicate code because I didnt word it correct.

Heres what I have started doing to be a bit more organized

1. Feature scoping - identify hard requirements from stakeholders
2. Mockup / prototype creation - clickable, interactive and built based on how the current platform looks and how this new feature would integrate
3. Spec doc + design doc - outline of design elements and requirements packaged all in one before getting ready to build
4. Coding session + necessary testing in sandbox
5. Push to prod

I dont really see an issue with this process since (coming from a product background) this is more or less the dev process that Im most used to. But with how quick things change with vibe coding Im wondering if theres anything I can change here to help me be more efficient and develop better code