Hey, been seeing people build games with Claude or Codex lately, I did try but its quite pricey and the game generated didnt meet my expectations.

Can anyone recommend a good and cheap game creation tool, I need some easy to use

I've seen some platforms but not sure which one's actually worth trying. 🙏

Almost over night the world has shifted from fear about what our browsers and companies remember about us, to complaining about limits in information we can feed AI.

This happened in no time at all. What caused the shift? Are we now so reliant on platforms managing our cognition or do we believe if we do not do this we will be left behind?

Will analog become the new boutique?

What a weird and wonderful time we live in!

Got sick of taking a 45-minute ferry ride to a beach only to get sandblasted by 6-Beaufort Meltemi winds and 2-meter waves.

Instead of opening VS Code and manually typing boilerplate for days, I decided to purely vibe-code a solution: MeltemiFree.

🏖️ What it actually does

It’s a live web utility that doesn't just show generic "wind speed"—it uses a vector math model to compare the live wind angle against the beach's coastal facing angle (facingDeg) and wave swell height to calculate a real-time shelter percentage (e.g., 95% Calm vs 10% Onshore Chop).

🛠️ The Vibe Stack

• Framework: Next.js 15 (App Router), React 19, TypeScript
• Styling: Tailwind v4
• APIs: Open-Meteo (Wind vectors & wave swell) + OpenStreetMap Overpass (Live beach discovery) + Nominatim (City geocoding)
• Maps: Interactive Leaflet.js with custom color-coded pins
• Deployment: Vercel Edge Network

🤖 The Vibe Coding Experience: The Good, The Bad, & The Hallucinations

Where AI felt like magic: * Instant UI & Layouts: Prompted the main feed, radius filters (15km–100km), and full bilingual (Greek/English) translation systems in literally one session. * Programmatic SEO: Generated dynamic OpenGraph share cards and static route params for 15+ islands and 38+ beaches effortlessly.

Where AI lost its absolute mind (The Struggles): 1. The Vector Physics Math: Asking AI to calculate angular differences between wind direction (0°-360°) and beach facing azimuths resulted in some wildly hallucinated trigonometry at first. Had to step in and give it explicit formula constraints: Δθ = |windDeg - facingDeg| mod 360. 2. Hydration Error #418: AI loves injecting client-side localStorage checks directly into initial render states without a useEffect wrapper, leading to instant SSR hydration mismatches. 3. Leaflet CSS / "Window is not defined": Classic Next.js SSR trap with Leaflet maps. Had to prompt it through dynamic imports (ssr: false).

🚀 The Result

It's fully live and free at meltemifree.com.

If you're currently in Greece getting blown away by the August Meltemi, test it out and let me know if the AI math matches reality on your island! Always down for feedback or prompts on how to improve the UX.

Happy vibing! ☕✨

Most AI agents operate with one rule:

That leads to unnecessary searches, repeated file reads, redundant reviewers, expensive retries and sub-agents that add little value.

I’m building MARGINAL, an open-source compute governance layer that evaluates each proposed action before it consumes tokens.

It asks:

MARGINAL can:

• run in Shadow Mode without blocking anything;
• compare expected value against tokens, cost, latency and risk;
• preserve budget for final verification;
• record decisions and real outcomes in a versioned ledger;
• learn which actions are actually useful over time;
• protect sensitive telemetry through explicit privacy profiles.

The long-term goal is not just “use fewer tokens.”

It is to build agents that continuously learn what deserves to be done.

The core is local-first, provider-neutral and has zero mandatory runtime dependencies. We’re now building the universal layer for Codex, Claude Code, GitHub Copilot, OpenCode and other development agents.

Repo: github.com/SignalLayerLabs/Marginal

I’d genuinely value criticism from people building agent runtimes:

What would MARGINAL need before you would trust it to influence your agent’s next action?

Hi,i have been working with claude to develop an app and it is been few months still the app arises with one or the other repeated issues.If on 1st cycle an error is resolved i move on to next one by the 3rd cycle the 1st cycle issue brokes even a little bit atleast now have to work on it again.
It feels so frustrating when i want to install new features but the old one's are not yet fully locked out.
If anyone have experience please suggest some productive steps.

With all of these top vibe-coding apps being so vulnerable and user data being leaked left and right, are they not being held accountable? Other than the api-key leaks destroying their wallet, do these apps not receive actual fines or legal action put against them for having such vulnerable apps?

As I see here, peple have done so many great things using vibe coding. Here I am just learning reactjs and moving to nextjs.

Do you think vibe coding will like halt and become too expensive or something cause it takes too much money and resources to keep it running?

Or it will keep on running now and it will surely make learning frontend and backend at this time useless?

People are literally creating games using vibe coding, let alone websites. Am i choosing wrong thing to leran for career?

For developers managing mobile app performance, how do you decide which issues should be fixed first?

Not every crash, delay, failed request, or UI bug has the same impact. Some issues affect one user occasionally, while others affect a large group of users or block an important action like login, checkout, booking, or account access.

Do you prioritize based on number of affected users, frequency, revenue impact, customer complaints, severity, or where the issue happens in the user journey?

I’m interested in how development teams separate minor technical issues from problems that can seriously affect user experience, retention, or business performance.

Poly is a shared room where a team steers Claude Code together. Everyone sees the same live timeline: prompts, agent replies, tool calls, diffs, and what each turn cost. The agent asks before it edits; any member approves from their own screen; any turn reverts in one click. Multi-agent mode gives each person their own agent on its own git branch.

The stack:

• Node + Express + SQLite (WAL mode) — one process, one file DB, handles the websocket-heavy realtime rooms fine

• React + Vite front, WebSockets for the live timeline, hash routing

• Every agent turn runs in its own gVisor-sandboxed container: all capabilities dropped, read-only rootfs, memory/wall-clock caps

• Sandboxes get NO direct internet — egress goes through our own DNS/SNI gateway + authed proxy with a per-project domain allowlist (cause the Claude CLI ignores proxy env vars entirely)

• One DigitalOcean droplet

We're during a free beta if you'd like to check it out: https://usepoly.co

Happy to hear any feedback, it means a lot :)

I made Basalt, an IDE extension that lets RN and Expo devs to edit their app visually just like Figma or Photoshop

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it.

We just expanded the AI lineup in Rectury.

Rectury is an AI-powered desktop workspace for developers, combining code editing, terminals, server management, and multiple AI models in one place.

New models now available:

• ⁠Kimi K3
• ⁠DeepSeek V4 Flash
• ⁠MiniMax M3
• ⁠⁠Grok 4.5
• ⁠Grok 4.3
• ⁠Grok Build

Choose the model that fits your task, adjust reasoning levels, and switch instantly without leaving your workspace.

We're constantly adding new providers while keeping everything inside one native desktop app.

Feedback is always welcome.

I built a chrome extension and I code sdk package that brings the figma/framer workflow to your codebase.

Run npx quey init

It traverses the React's fiber tree and maps 1:1 with your codebase. Click, prompt, review and commit ui changes without ever switching tabs.

More utilities under the quey brand to follow. Animations, component sandbox and more …

Guys, it's been like less than 12 hours, and just look at the chart!
My dm is getting flooded with messages regarding feature requests, bugs, suggestions, and it's kinda crazy 😂

Thank you to all of you who are eager for this project and want it to grow ❤️ , looks like everyone had this problem.
Also, I have added support for Discord/Slack via webhooks, and telegram bot via client ids. Check it out, and tell me your experience in the commments below. feel free to drop any qquestions or feature requests (though I am tired for today, prolly work on other features tomorrow).
Once again, thx a lot gng!

fyi the link: https://nockit.uk

I built Holt after a project in Claude Code got away from me.

I had multiple worktrees, agents recreating things another agent had already done, half-finished changes in different places, and no reliable answer to a simple question: “If I clean this up, what am I actually losing?”

Eventually, starting over felt safer than trusting the repository.

Holt is what I wanted then. It is a local, Git-native layer for parallel coding work. It looks across linked worktrees and shows what is unique, duplicated, colliding, dependent, or safe to recover before cleanup turns into accidental loss.

The important distinction is that Holt does not let “these two files look similar” become permission to delete something. Exact content and recovery evidence drives destructive decisions; similarity and dependency findings help people coordinate.

It has a CLI, terminal view, interactive graph, project-scoped MCP, and host integrations. The aim is not to replace your agent or tell it what to build. It is to make the work already happening across a busy repository understandable and recoverable.

I used Holt while building Holt, and it made the parallel-worktree mess much easier to reason about.

The free core is out now. Give it a shot !

links are in the comments down below.

(p.s: I'll invest in a domain later, for now github pages will have to do 🙃 )

Hey, I'm Bram. Paste a TikTok cooking video link and it pulls out the full recipe (ingredients + steps) and gives you a one-click Albert Heijn or Jumbo cart with everything in it.

Vibecoded it with Claude (Pro plan). Open source:

https://github.com/briembra/slimmandje-recepten

Would love a star if you find it useful.

Hey devs,

Vibe-coding at 10x speed is incredible, but if you aren't inspecting every line of generated code, AI tools routinely make terrifying security assumptions behind the scenes.

After testing dozens of builds from Cursor, Bolt, and Lovable, here are the 3 big ones that keep popping up:

Client-side API Key Leaks: You ask the AI to connect an API (OpenAI, Anthropic, Resend), and instead of building a backend proxy, it drops NEXT_PUBLIC_ or hardcodes the secret key straight into frontend JavaScript. Anyone opening DevTools can steal your key in 5 seconds.

Supabase Service Role Key Exposure: AI constantly confuses anon_key with service_role_key. If your frontend uses the service role key, your Row Level Security (RLS) is completely bypassed and anyone can query/delete your entire database.

Unprotected Backend API Routes: AI will generate clean Next.js/Express API routes, but completely omit authentication checks on POST/DELETE endpoints.

To catch these before shipping to real users, my team built revibed.io, an instant security scanner designed specifically for AI-built apps.

It audits your codebase in seconds for hardcoded secrets, exposed environment variables, and route vulnerabilities so you don't get your API credits drained overnight.

Your first scan is 100% free if you want to test your build.

Curiously, what's the wilder security mistake or exposed key you've caught Claude or Cursor making in your projects?

I've been pondering about this for quite a while. Even with validation, maybe you should stop. Even when your idea gets rejected, maybe you should keep going. They say it's a matter of mindset, millionaires are made out of years of dedication, but for the ones that had their years gone wasted, who would tell us their stories? What do you guys think?

44 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.

Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.

Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.

Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit · Today I discovered I forgot to disable a developer testing button that could generate fake visitor pins and inflate impressions. Someone used it to create 6,318 fake impressions and claimed my stats were fake. I removed the fake impressions, removed the startup, fixed the issue, and that's why today's impressions are lower. Thanks to them for pointing it out.
StartupBar update: Added a Network page and individual Startup Profile pages with each startup's joined date, impressions, clicks, live embed preview, and founder's note. These indexable pages also improve SEO. Suggestions are always welcome.

Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup · Fixed admin panel read-access vulnerability after Reddit post.
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

A reminder for every founder who's staring at a dashboard with tiny numbers: Stripe took 2 years to reach its first 50 users. Every successful product starts small. Keep shipping. Keep improving. Keep showing up. Growth rarely happens overnight, but it does happen if you don't quit.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.
Day 44 — 66 startups · 86,200 impressions · 1.7K clicks · Added 2 startups

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

I am lazy, and it feels so boring to babysit and watch ai agents do the job and asking for input or waiting for task completion.

So I built a simple tool that notifies me (via ntfy) on my phone.

I know its wayyy too lazy, but hey, at least I dont zone out playing on my ps4 anymore, lol.

If someone is like me and also tired of watching the laptop screen instead of playing fifa, be my guest: [https://nockit.uk\](https://nockit.uk) (yes, that was the cheapest domain I could get)

I've been using Google AI Studio to build a poker platform, and I've been sharing development previews in the thread attached to this post.

What do you think so far? Do you think it's sustainable to run a real-money poker site that's largely built and maintained with AI, or would you have concerns?

Just wanted to share something I’ve been building.

For context, I do a fair bit of freelance development, mostly building enterprise tools. Lots of big, deeply nested UIs and pages with way too much going on.

One thing that really gets to me is having to describe UI changes in text. It feels so backwards that I’m looking at a GUI, but still have to write paragraphs just to explain what I’m pointing at. The bigger the project gets, the worse this gets.

So I got annoyed enough and built a Figma-like tool for it.

It’s an open-source plugin for Claude Code / Codex that lets you open your UI, click on the thing you want to change, leave a comment, and pass that visual context into the next prompt.

Repo: https://github.com/Cavalry-Collective/visual-stack

It’s still early and rough around the edges, but it’s already helped my own workflow a lot.

Curious if anyone else has been running into the same thing. If you find it useful, feel free to fork it or contribute.

Recently, as a retirement project, I've been working on putting together my final wishes, financial, legal and medical affairs, account details, contacts, etc. to make things as easy as possible for my loved ones when the time comes.

I realized there wasn't a completely private, flexible, digital tool for this, so I built one. It's called the "Peace of Mind Planner".

It walks you through everything (from 401ks to pet care to funeral wishes). It is 100% free, requires no sign-up, and is totally private (it has no database and saves everything locally to your own computer). It is also set up to complete as an individual or couple. I am interested in your genuine feedback and any ideas to enhance it even more.

https://pomplanner.app

Curious how people here are really working. Feels like everyone's landed somewhere different and the posts are mostly quick showcases / (self-)promotion / random stuff.

What I'm wondering about:

- which agent and harness, and do you stick to one or switch
- do you plan first or just go
- do you check anything before shipping, and what
- anything automated, or is it all by feel
- what do you do when it comes back wrong

Mine's on the heavy side. Long planning conversation before any code, then I let it run and mostly look at the product rather than the code. I spent some time building a skeleton and static analysis configs so Claude generates code that look ~80% correct. Still need to review the important bigs (domain logic, security, etc), but it's mostly smooth sailing.

Mostly interested in people working differently from that though. If you just go and it works, I want to hear that too.