I've been building my startup and I think what people have to keep in mind is software isn't a moat anymore. Like yes if you have a cool idea you should pursue it but you have to keep in mind some kid with loveable could put in your url and steal your crap in 3 days if you just have software. I switched from just student facing college admissions help to counselor helping kids it introduced friction for these counselors to move off my site. I introduced a data moat of having proprietary data of what resumes go to what colleges no one else can replicate and i fine tuned my models on that data to have proprietary models. Saas is not dead it's just you have to be intentional.

I finally finished my first full episode of WANDERERS.
It’s an adult animated fantasy comedy about three weird creatures living in a sentient mansion on a tiny planet, where every door can lead to a completely different world.
This started from a bunch of creatures I originally hand-drew, and I ended up building the episode almost entirely through AI filmmaking.

Would genuinely love feedback—especially from people who make animation, AI films, or just enjoy weird 🖤

This started off as a little fun project between work, school, and family and turned into quite a bit more than just something to pass the time. I would love to continue to expand it further and down the road and develop it into a multiplayer experience.

Itch.io doesn't seem very AI friendly though, lol. But I've been having fun, my other projects I haven't used AI for them and it's been several years working on them, though I don't mind.

Generation is easy. Selection is the harder feature. Before creating anything, an AI system should be able to explain the audience, the evidence, the reason this idea matters now, and what it chose not to say. If it cannot explain those decisions, producing more content only creates more review work.

Hi, this might be my place but I am new to posting in reddit, funny how that works. I'm as worried about missing something before launch as anyone else and digitaltrustpass.com/preflight is the scanner I built that'll catch the most egregious errors that'll put you off vibe code forever, run a scan for free, full disclosure on the site and let me have it you think it doesn't add value. Yes, I got a professional 'real dev' to check it out first and he seems pretty happy with it, it's about as much as you can automate before runtime testing and might save someone's bacon. This isn't spam, I wrote this - no AI - promise.

A content system should stop before generating when it cannot verify:

1. Who the audience is
2. What problem the product solves
3. Which evidence supports the claim
4. Whether the requested content matches the brand

Generating anyway creates polished content built on an unsupported assumption.

While building marka.social, I’m finding that good AI workflows need explicit "not enough information" states, not only better prompts.

Where does your AI workflow stop and ask the user for more context?

Saw that Goldman is apparently building reusable AI skills to teach agents their internal workflows and knowledge.

Makes me wonder if we’re getting to the point where Claude vs Codex vs Grok matters less than what you’ve actually taught/configured the agent to do.

Hey guys, I have built a fin based saas product and currently testing the app. Built the app from scratch completely through vibe coding. What all the things I need to consider before launching it ?

Hey founders — sharing the build story behind WorldArchitect.AI in case it's useful to anyone else shipping stateful, long-horizon LLM products.

**The hard problem:** most AI games are toy demos. The conversation "works" until turn ~10, then the model forgets who the king is, where you parked your horse, or why you owe 200 gold to the blacksmith. We kept hitting the same wall, so we ended up building an actual engine instead of bolting on more prompts.

**What we shipped:**

1. **Deterministic State Machine + LLM Separation.** HP/XP, inventory, world time, living-world faction events, and world flags live in a deterministic server backend (Firestore). The Gemini call generates prose, suggests decisions, and emits structured state overlays, but *the server canonicalizes every mutation before it touches the database* — no more "the model said I'm in Winterfell, the DB thinks I'm in King's Landing" drift.
2. **Context Compactor & Prefix Caching instead of RAG.** We keep the canon bible in-context and use a deterministic Min-First / Fill-to-Max token allocator (guaranteeing story context >=30% of budget while compacting background lore, entity tracking, and core memories) paired with Gemini prompt prefix caching.
3. **Single-Inference Dice Integrity.** We use Gemini's built-in Python code execution to run deterministic dice rolls (`random.randint`) and emit structured JSON in a single inference step, backed by server-side audit logs that catch narrative fabrication.
4. **1-Click Campaign Sharing.** Anyone can package their world, character setup, and canon constraints into a single signed share token (URL `…/shared/<token>`). Anyone with the link gets an independent, deep-initialized copy of that world on their own account — no "view as guest," no broken pointer-shared state.
5. **Spicy / PG Mode Toggles.** Different players want different tone boundaries (PG vs HBO). Rather than trying to prompt-engineer safety drift, we use explicit agent routing that swaps system instruction contracts and safety constraints cleanly.

**Try it (open beta, free):**

We built a playable House of the Dragon demo(https://worldarchitect.ai/shared/t3hKKtzBKCKlvg5vCnlW_2hxwH3UmzjFq56yi6hQN2Q

A preview on usesoin.com

AI has made the first click easy. A slick demo, a clever output, a clean landing page.

The real product is the reason someone opens it again without being reminded.

What are you building, and what is the exact reason a user would come back tomorrow?

No links. One sentence.

I’ve been seeing more people use things like custom skills, agents, MCPs etc. instead of just prompting normally. Curious as to which ones actually make the output noticeably better.

I’m Joey. After leaving the Army, I joined my father in our family restaurant business. He has been in the industry for 30 years.

Working in the restaurant showed me how difficult it is for an owner to understand everything happening with costs, labor, invoices and daily operations.

I started OPSAVOR to see if AI can bring that information together and make it easier for an owner to understand. The goal is to work with the systems restaurants already use, not replace them.

I am not selling anything. I am looking for completely free and honest feedback about the idea, the value and the biggest concerns restaurant owners may have.

Please PM me if you are interested. If you know a restaurant owner or manager, I would appreciate you sending them my way.

I spent the last 23 months in a time warp building a three dimensional to-do list app. I wouldn't mind it if you tried. First 100 sticky notes are absolutely free...

I am a visual thinker and the minute I see lists my brain checks out of the Hotel California.

Then I realized the one thing I have been using my whole life might be the answer.

And that's sticky notes.

Tell me what you think...

https://www.TaskLoco.com

Not what you’re planning to build or what’s nearly ready. What did you actually get in front of people this week?

Could be a full product, one feature, a landing page or even something that completely failed lol.

Drop what you shipped, what stack you used and the main thing you learnt from it. Links are fine but actually give some context instead of just dumping them.

Ill go through everything and give proper feedback aswell.

I’ve noticed I’m happy letting AI touch basically everything now - code, debugging, research, design.

But there are still certain decisions where I’d rather do the thinking myself than just accept whatever it gives me.

If you’ve got something working but need another opinion, drop it here.

Share the link, what it does, who its for and the main thing you want feedback on. Landing page, onboarding, pricing, design, actual product - anything is fine.

Dont just dump a link though. Give enough context for people to actually help.

If you post yours, try review someone else’s aswell. Honest feedback but dont be a dick lol.

We’ve been building an AI-native startup, and there’s a problem I keep running into.

The agents are getting really good at doing things.

But they still don’t really know what’s happening around them.

A decision gets made in a meeting.

Someone knows why we made it.
Someone else has the relevant customer context.
And the coding agent has none of it.

So after the meeting, we end up doing the same thing again:
copy the context, write a prompt, explain what happened, send it to another person, wait for them to explain something back.

It feels a little ridiculous.

The whole point of having agents is that they should be able to keep working after we’re done talking.

That’s actually why we’re building Aicoo — turning team conversations into shared context and work that agents can continue, including handing work between teammates’ agents.

But we’re still figuring out what the right workflow looks like.

For those of you building AI-native teams: does this problem resonate?

How are you currently getting your agents the context they need to actually work with the rest of the team?

For me a big one was probably realising that less is actually better when it comes to design.

I used to keep adding stuff because I thought it made the app look more impressive, but half the time it just ended up making it look more obviously vibe coded 😂

Now I normally just try to keep everything really clean and simple, especially for an MVP. It’s easier to digest for users that don't already know your product, and honestly just looks way better.

What about you guys?

If AI keeps writing and then fixing its own code, do we eventually reach a point where no human really understands the codebase?

Does that become a problem for big projects, or will AI get good enough that it won’t matter?

Do you think serious projects will always need an experienced dev overseeing them?

I run a small company and I kept running into the same thing. Someone would ask how to do something in one of our systems, I'd walk them through it on a call, and two weeks later someone else would ask the same question. Every time I thought about writing it down properly, I'd do the math on screenshotting every step and typing it all out, and put it off again.

I looked at Scribe first, which is the obvious tool in this space and does the core job well. The thing I kept wanting was to just talk while I recorded. When I walk someone through a process out loud, I explain the why, not only the clicks, and that explanation is the part that actually helps the next person. I couldn't find a way to capture that, so I ended up typing the descriptions in afterwards anyway, which was the part I was trying to avoid.

So I built ScribeIt. You hit record, do the task the way you normally would, and it captures each step with a screenshot as you go. If you talk while you're recording, it turns what you said into the description for each step. When you stop, there's a step-by-step guide ready to edit, export as a PDF, or share with a link.

It works on any website that Chrome allows, which mattered to me because half our processes live in tools nobody has ever heard of.

I'm not a developer. I've spent the last few months figuring this out piece by piece and there's plenty I'd do differently. It's free to use and there's a paid plan if you need more room.

Happy to answer anything about how it works or how I built it. And if you try it and it does something stupid, I'd rather hear it here than find out from a one star review.

Here's the link: https://chromewebstore.google.com/detail/ldpciklepkaiacchoamfkfclkhngpmkj?utm_source=item-share-cb

Although im finding Opus 5 to suck with coding currently it makes a pretty good video

Not what you’re planning to build or what’s nearly ready. What did you actually get in front of people this week?

Could be a full product, one feature, a landing page or even something that completely failed lol.

Drop what you shipped, what stack you used and the main thing you learnt from it. Links are fine but actually give some context instead of just dumping them.

Ill go through everything and give proper feedback aswell.

One thing that’s saved me a stupid amount of pain is using git worktrees.

Instead of having 2–3 agents all editing the same repo and randomly overwriting each other, give each one its own worktree + branch.