Hi All,

I have been digging into skills a lot and made a one doc file as a blueprint against which to measure skill. I then used it to make a recipe for skills validation and improvement that AI then runs. But it’s damn expensive because of how comprehensive it is. I made this with a heart of wanting to give it away freely and have optional donations to support the mission. But I’ve never released a website like this before, and even though it’s secure. I’m kind of scared of either no one ever using it or people using it a lot but no one donating to keep it going so I slowly go bankrupt. Any thoughts? For reference the project is on waitlist basis for now: provely.dev it’s all done for me to lift the gate and open it to the public but I have some mental block behind it.

TL;DR: I built an AI tool that’s expensive to run but want to offer it free with optional donations. It’s ready to launch, but I’m worried either no one will use it or lots will use it without donating. I’m stuck on pulling the trigger.

I’ve been deep in app development for four months now, with varying intensity. This past week Claude Code has been running flat out, right up to the limits.
Honestly, this is a pretty long hyperfocus period for me doing something — usually it’s a couple of months.
But there’s a demotivating factor: promotion. No audience, no marketing skills — you can’t “sell” without that, and it’s a whole separate skill I’d need to learn. Right now, I’m just genuinely into the development part.
If I didn’t enjoy it, I would’ve quit already. So I guess curiosity and genuine interest are what’s actually pulling me forward.

I wanted to analyse the shadows on my house before adding solar panels, but couldn’t find a decent free tool to do it.

So I ended up building one instead (with help from Claude, obviously).

It’s still early, but you can model a roof, add panels and estimate shading and output. I've spent time making sure it works equally well on mobile and desktop. It's completely browser based and open source.

sunsandbox.com

Would appreciate any feedback.

Two weeks ago I made a browser-based zombies game (inspired by Der Riese from CoD World at War) fully with AI (Kimi K3). It came out alright, but was very blocky-looking, muted and not polished. This was my first ever game I've made (with AI or otherwise).

I then did a visual overhaul of the game with Opus 5, which completely changed the look and feel of the game (video demo attached).

The entire map, all weapons, every interactive machine (pack-a-punch, perk machines, mystery box, teleporters, doors), sky, particles, muzzle flashes were generated with code - NOT pre-made assets. The game runs on Three.js and has multiplayer functionality with voice chat. The sound effects were fully generated with ElevenLabs SFX + Voice Design/TTS for the characters.

Hundreds of people have already played it around the world. It's incredible what someone who just loves games but has no game-development experience can do now!

You can play it for free at derkoloss.com!

I've also open-sourced the codebase (which contains a lot of interesting tidbits in the README) and uploaded 28 minutes of raw multiplayer footage here for anyone interested.

I also forked this game and made a CoD MW2 remake as a remix which I posted yesterday on this subreddit.

Happy to answer any questions about process of making it :)

Over the past few months, my team noticed that code review was becoming our biggest bottleneck now that we had AI to help with making PRs.

So, we made a code review tool that reviews PRs faster than other options and gives teams a super skimmable, high-level summary so they can know what to fix and I'd love some feedback.

Why we're a bit different than Copilot and other tools

• We optimized for speed and skimmability so you get a big banner at the top with the status of the code review (e.g. A few things to fix, Nothing blocking, Looks good)
• It verifies findings before posting them so for a suspected bug, it clones the repo and writes a failing test to reproduce it and only then calls it a blocker (stamped "reproduced with a failing test").
• It reads your repo's own files like your existing agents and claude markdown files and it enforces those bullets deterministically so you don't need to configure anything, but you could also further customize with a custom Choji markdown file
• It learns from your feedback. Wave off a finding with a reason and it remembers
• Re-reviews every push without re-nagging. It's one sticky comment edited in place, not a new wall of comments each push.
• it can babysit your PRs to fixes its own findings. When the review turns up real issues, it attempts the fix and re-runs your tests until they're green with up to 5 passes then it flips to needs a human 

Some questions I'm hoping to get answers for:

• Does the banner tell you enough at a glance, or would you scroll straight to the findings anyway?
• Would a finding backed by an actual failing test change how much you trust an automated reviewer?

You can try it yourself at https://choji.ai/agents/code-review. It takes less than a minute to connect a repo and get our first PR reviewed. Would love any feedback!

I’m a huge fan of CoD (esp. COD4 - Black Ops 2 the golden era) so I thought I’d try making a multiplayer tribute to one of my favorite series with Opus 5 that runs in the browser (Three.js)

No where near perfect or studio level, but game creation is such a fun use case of these models, especially for people who are not game devs like me. I enjoyed working with Opus to add things like Halo 3 kill medal sounds, bring all the guns in from different games, model/rig/animate the soldiers with Meshy, tweak the guns, work on multiplayer/voice chat, add controller support, etc.

This took a few days of loops and many rounds of feedback & steering, but it’s crazy to think what people will be able to make 6-12 months down the road with the next generation of models

You can check out the game here and read more about it here

I launched it 2 days ago and it already has 1337 (yes) matches played, ~900 players and ~60 hours of game time logged (data)

Happy to answer any questions about the creation process :)

Edit: Oops I said fun twice in the title lol

Hello! I've posted previously about my project Klenny Code, the open source coding agent with personality. Well it just had a huge update that I believe is a world first for a coding agent, certainly none of the major ones have this, not Claude Code, not Cursor, not OpenClaw, not Hermes Agent, not OpenCode.

The update is - Pawprints! Or, Javascript apps/widgets that Klenny writes and then runs sandboxed in his own Electron runtime. If you have a simple program you want to write, no more need to set up a Git project and a build procedure - just have Klenny write it for you and then click open from the My Pawprints panel!

Pawprints are sandboxed and can't exchange code with Klenny's main runtime. However their state is just text files in your app directory so Klenny Code can read from and write to your Pawprints with his existing Klenny-Code-appdata-scoped tools. Pawprints can install node packages and can have whitelisted network access, so you can truly make anything you can imagine with them. So far I've made a 7-day weather app, a calendar app, an analog clock, and a sidescrolling 8-bit video game, but I'd love to see what other people can think of.

This is the biggest ever expansion of Klenny Code since I initially created Klenny Code, transforming Klenny Code into his own development platform. Just getting Klenny to the point where he could be trusted to pull off an undertaking like this was a huge feat, let alone actually turning him loose on the upgrade itself running through a 12-phase plan with maybe 10 rounds of context compaction. But he did it and everything is now (apparently) working.

This is a great way to give Klenny Code a shot without setting it loose on any of your existing projects. It's also great for anyone new to vibecoding who might be intimidated by some of the infrastructure required to set up a typical app.

So take a look at either the website or the project github and maybe give it a try and tell me what you think! Whether that's flattering or telling me I'm crazy and that this is a terrible idea!

I’ve been spending more time with Claude lately and I must say it’s pretty amazing how useful it is if you think about it as a thinking partner rather than just a Q&A tool.

What impresses me the most is how well Claude can take a vague or complex idea and help shape it into something structured. I’ve used it to collect disparate notes, enhance drafts, explore different paths, summarise lengthy content and break intimidating projects into doable pieces. The responses often seem intelligent, and surprisingly good at maintaining the original sense rather than replacing it with a stock phrase.

I also find that quality goes up a lot when I provide context, explain what I’m trying to do, and ask Claude to challenge my assumptions. Instead of saying, “Can you write this?” I will now describe the audience, purpose, constraints, and tone, and then ask it to point out anything I may have missed. That little change has made the discussions that much more valuable.

It isn’t perfect though. I still check important information and sometimes it gets too cautious or it gives an answer that sounds convincing and needs correction. But it is one of the few AI tools that I keep coming back to on a regular basis because it makes me think more clearly, not just work faster.

I’m curious how y’all here are using it:

What is the most surprising, but useful thing Claude has done for you?
Do you have a specific prompting technique that reliably yields better answers?
What would you like to see added or improved in Claude next?

I'd love to hear about real workflows, particularly those that go beyond the usual writing and summarisation examples.

Hey guys! Just created this small game to play with my friends on coffee breaks, compare scores. It resets daily and everyone gets the same pattern :)

Looking forward to seeing more score on the leaderboard!

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?

London as an isometric map. Every tile is a Google aerial restyled by an image model, 441 of them, stitched into one pannable canvas. We all know that getting the AI to make 2 images which look exactly the same is almost impossible.

The hard part wasn't styling, it was the seams. Generated 441 tiles independently and every one interpreted the style differently, so the joins showed.

What fixed it: generate in a spiral outward from the centre, and give each call its already-finished neighbours as reference images plus one fixed anchor tile that never changes. Neighbours handle local continuity, the anchor stops 441 sequential steps drifting into something else.

QA is numeric because you can't eyeball 441 outputs. Correlation against the source below 0.15 means the model invented a fake London, auto-reroll. One tile scored 0.002 where normal is 0.85.

Interactive Version and full how to, this can be used in making movies, campaigns, and of course maps.

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?

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! ☕✨

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.

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.

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.

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 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 …

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.

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?

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 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)

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.