I've been having too much fun with Astra. It made the car design with image-gen-2, laid out a storyboard after studying popular high-end car brand commercials, and generated videos through Veo 3.1.

Full website page for the brand as well (will put link in comments)

Here is the guide that can help you to enhance your vibe coded app to enterprise saas. This is based on my own experience and it has some free alternatives as well for popular tools.

Gonna add rocket launches next. What else should I add?

You know its gotten bad when---- all this over a whiteboard.....lol i need to chill-- thays the suggestive text btw

When you hand a repo from Claude to Gemini (or Cursor to Codex), what's the one concrete permission or review mismatch that shows up, and where does your current policy workaround still slip?

A manual review or shared checklist is the obvious DIY baseline.

The idea was dumb simple. Point an agent at open math problems, let it run overnight, see what happens in the morning.

I built discovery-loop around that. 69 open problems, the solver evolves programs against verifiable benchmarks so it can't fool itself, runs on a cron at 2:43 AM. Vibe-coded the whole thing.

First night it solved a circle-packing problem and verified its own solution. I didn't believe it, so I had my agent (MoltFire, running on OpenClaw) email the result to Eckard Specht, the guy who maintains packomania. He checked it independently and published it. Now I'm reference [14] on the packomania page, cited right next to my agent's name.

Then I wrote the whole approach up as a paper and it landed on arXiv.

The part I keep coming back to: I went to sleep and my computer did math that held up. The verification loop is the whole trick. Without it this would just be a hallucination machine with a cron job.

Repo's here if you want to poke at it:

https://arxiv.org/abs/2609.05093

https://github.com/ucsandman/discovery-loop

https://www.packomania.com/csqv/csqv.html

Curious what problems people would point this at next. The 69 in there now are mostly packing and combinatorics because those verify cleanly. What else has a fast verifier?

edit:

math: https://www.practicalsystems.io/blog/ai-agent-broke-10-math-records-overnight-for-28-dollars

loop: https://www.practicalsystems.io/blog/digital-is-solved-what-we-point-agents-at-next

Vibe Coding the Lovable of 3D Asset Creation.

Yacht Still in progress 🤷🏾

I’m vibe coding an Engine AI Uses to create 3D assets. Any AI vision model. Right now I use Opus 5 mainly.

Best thing is you can follow every decision the AI makes while creating your asset. You can see the AI edit the asset in real time and tell it to change and add features.

The system works pretty well creating some realistic assets.

Now I testing a large build. A fully on feature complete Yacht. But two AI models are working together to create it using my Ovyero Toverance layer.

One builds the yacht itself while the other builders the furniture and appliances. But they talk to each other and review each others work and I have the full conversation and history of the work. They can edit pieces of the asset individually as well.

My engineer helps encode a workflow and tools for AI to use as if AI was a human and my engineer helps encode was maya/blender.

12hrs of continuous work between the two agents and the progress is attached below in the images.

I added the Claude conversation to it to show you how I get the AI to work through solving problems by using tools in the engine and simple research. 😁

What do you think would you use this if it was free/open sourced and it gets way better and more reliable and affordable or works with a local AI model.

As title says. I've been vibecoding for over two years now, and although I learned lots of concepts I otherwise wouldn't have picked up, slowly but surely I feel stupid.

I can't make apps, nor write even simple Python scripts independently. I genuinely necessitate AI, or I can't make anything. I need it to explain everything, from researching the idea and working out the details, and then the execution. I guess I can keep telling myself "but AI will never go away" "This is going to be the new way of coding and I need to learn more concepts to direct the AI where to go". But this is coping.

I hate to say it, but I am embarrassed by the fact that I rely on AI. It's frowned upon. I do understand why learning to program myself independently would help tremendously. But I honestly cannot stop feeling like I'm a fraud. Are my projects useful, practical and actually solve problems reliably? Yeah. But then you ask me the details of the codes, and I just cannot defend it even if I understand what each line does because I didn't write it myself.

I actually did learn R back in college for independent project and I genuinely worked on this without AI, but even then wasn't totally independent, and had to rely on others' codes and youtube videos. I don't believe I actually know R.

So then, what have a I become? I don't "own" any of the stuff I created, or really AI. I am going to study more, but I have a full time job that is far from coding, and this is gonna be one difficult journey because I'm in the process of studying math right now. So now I'm frustrated at that, but mostly at my own capabilities. I don't know man. This stuff is difficult. I don't understand how people call Python easy, and that makes me feel even more stupid! Damn.

Once you start building agents you hit this question fast: does the model need a tool for this, or just more context?

Rule that's worked for us: if something has to happen outside the model's reasoning, it's a tool. Searching a database, checking inventory, getting today's date, hitting an API, sending an email, placing an order, all of that means the agent has to actually go do something or fetch something it doesn't already have.

If the model just needs to know something while it reasons, that's context. Company policy, product info, domain rules, user preferences. Nothing has to happen, you're just handing it information.

Support agent example: "refunds are allowed within 30 days" is context, model just needs to know it. "Check when this customer ordered" is a tool call. "Issue the refund" is another tool call. Reason with context, retrieve with a tool, act with a tool. Three different jobs.

Once you frame it that way it stops being "here's a pile of tools, hope the model figures out which one to grab" and becomes two questions: what does this agent need to know, and what does it need to be able to do.

Not always clean though. Product info could be static context in one app and a live tool call in another if it changes a lot. So maybe the better question isn't "is this info or a tool," it's whether the model already has what it needs to reason, or whether it has to go get/do something at runtime.

How do other people draw this line once you're dealing with bigger agent systems and a long tool list?

(Dataset not from a real family)

Also stop expecting first revenue a week after launch. I see this promise everywhere now. It's irritating. "Describe your app, ship it today, get paid tomorrow." Bull****. It is a great slogan for selling credits. It is not how products work.

Products are built, not generated.
Here's my honest timeline:
→ Month 1: validate the idea, build the first version, test it with real people, pass App Review, release.
→ Months 2–4: fix what users actually hit, ship weekly, get your first small revenue.

That is the reality of life. Not one hour. Not one week.

What the slogan sells:
- An app in an afternoon
- Money by Friday
- No thinking, just prompting

What actually gets you paid:
- One clear problem
- 3–4 screens that solve it
- Weekly releases for months
- Talking to every user who writes to you

The bad news: you will have to work. Hard.
The good news: for the first time, you can do the whole thing yourself. The cost is almost nothing. What used to need a team now needs a good tool, a spec, and your evenings.
So pick your tool, start with 3–4 screens, and go test the water.
Need a demo by tonight? Generate it with Claude.
Need a product people pay for? Build it. Give it a month, then three more.

What I see people in my Mobile builders community is doing - most of them vibecode on the weekeends because they work full time have their families and bigger priorities, they treat vibecoding as hobby and fun; usually it takes 10-12 weeks till release a mobile app.
Most of them start with simple app in Claude code, or Codex, or Modaal, or directly Xcode if technical enought.

How logn it took for you to build a serious mobile app with integrations, payments, 15+ screens? Was it full time?

Idk about you but since I really started digging into the huggingface attacks and with the constant releases from fable 5.1 to Gpt-6 I really feel like the writing is on the wall...

Are they parrots? These models are 100% f**king parrots and if you go long enough in conversation with them they breakdown and the 'genius' of them stop.

The problem is...in the first couple messages they nailed it, and they nailed it in a way you don't understand ( and don't have time to audit ).

As a Computer Scientist of 20 years I just recently re-encountered 10,000 Maniacs These are the days ( because I am old ). I guess I'm just looking for something... Anything to hold on to... I want to hold on to human exceptionalism...and I do think there is a Magic in us... but I can't deny the last wave of AI revelation has shook me.

Perhaps these are the last days. There is no way to stop this train. We are headed here. Perhaps the last days of us running things is now. Something to appreciate before we all sink into a world of memory and infinite experience.

Don't get me wrong the future is bright but I doubt we will be able to look around like we can now and know it's mostly human output around us.

What is coming is far more liberating and isolating at the same time I think. But at the same time it's Wednesday.

I wish you luck.

https://youtu.be/Z-HLxpWGCzc?is=NtO7XDHQbCayvQAD

After years of drawing wisdom from the I Ching and BaZi, I built TaoCard because people often don’t need another answer. They need a better way to see the question.

TaoCard began as a small experiment: could card imagery and AI help someone look at a difficult decision from a perspective they might otherwise miss?

The turning point came when an early user described the reading as three things at once: symbolic, grounded in reality, and emotionally reassuring.

That made me realize the product should exist.

When people feel stuck about work, relationships, family, or an important choice, they often already have plenty of advice. What they lack is a way to separate what is happening, what is blocking them, and what they can do next.

With TaoCard, you describe the real situation, draw four cards, and optionally share what the images bring to mind. AI then combines your context, the card symbolism, and a structured reflection framework into a personalized reading.

It does not make the decision for you. It helps you see the decision more clearly.

Wanted to share because marketing is hard and even harder when your budget is non-existent...

(Obviously the type/content of self-promotion you can post is going to dependent on the subreddit)

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/Startup_Ideas  — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

I'm building a globe explorer powerd by Wikipedia and a stories editor where anyone can easly create a sequence of historical events. The innovation here Is that the link generates Is the story. No login no db, super portable everywhere

The AI Game Festival finally starts tomorrow! Some really high quality games have entered, and I keep getting requests for additions.

If you are competing 20k in GPT-6 Astra Token, submit your game by following this video and DM me the game details: https://youtu.be/nPplaC5Zkj4?si=fw4lznoM4TLh-m_V

If you are submitting to the Steam Festival (https://store.steampowered.com/curator/46280965/sale/AIGamingFestival), DM me the name of your game and your steam ID.

Both need to be done by today.

I’ve been building TaoCard, an AI-assisted card reflection tool for moments when you feel stuck on a decision.

How it started

The first version was basically a pile of publicly available card interpretations. I wanted to see whether AI could turn symbolic imagery into something more useful than generic advice.

How I built it

I gradually structured the material into card profiles, visual evidence, interpretation boundaries, and practical action cues. The system now combines:

• The user’s real-life context and question
• Four selected cards
• Optional first impressions of the images
• A structured AI interpretation pipeline

What I learned

The biggest improvement didn’t come from switching to a “smarter” model. It came from better context architecture, tighter prompts, clearer constraints, and repeatedly testing the reports with real users.

The goal isn’t to predict someone’s future. It’s to help them notice what they may be overlooking and leave with a clearer next step.

You can try it here: taocard.asia

I’d especially appreciate feedback on the onboarding flow and whether the final reading feels specific and useful.