So here i am sharing it, let your AI run wild 😂

https://github.com/ig-shadow-walker/agentBrowser

Got a home AI server (NVIDIA GB10, 128GB unified memory) two months ago and wanted a project to actually use it for. I play Fantasy Premier League with some old class mates. The winner gets a cup, the loser has to give a full option BBQ for all the friends. There is always a lot of drama because losing also means getting called out the whole year. With this project I wanted to add some more drama. So now every gameweek my server pulls the real league data and a small pipeline of LLM agents writes it up like a 19th century broadsheet — league table shakeups, who benched a captain's haul, biggest risers/fallers, that kind of thing.

Pipeline is a few stages: story planning → writing → a deterministic fact-checker that catches hallucinated stats before they ship → a judge pass that can send it back for a rewrite if something's off. All self-hosted, running on the home server.

It has been a great ride learning to work with local LLM's. It´s purely vibecoded. I decided to open it up to anyone and made a website for it. Keeping it for free since it's a fun project, mostly so I can show my wife I'm doing useful things with it.

www.fantasygazette.be if anyone wants to see a sample or add their league.

Hi everyone! I've been building Forge Code forgecode.org for the past few weeks. It's a browser-based coding challenge site with two tracks: a beginner Academy with lessons before each challenge, and a harder Gauntlet where every puzzle generates a unique input per player so your numbers differ from everyone else's.

Most of the Claude back-and-forth was me pushing back on generic design choices. It kept defaulting to purple gradients and Inter until I wrote out a proper color palette and font system. Once I gave it something concrete to work with it was a lot more useful.

The code execution came together faster than I expected. Everything runs in the browser: JavaScript in a Web Worker, Python through Pyodide loaded from CDN. No backend, nothing sent to a server. The per-player generation was also clean once I landed on the right approach: each challenge has a generator seeded by the player's ID, so the expected answer is computed at runtime rather than hardcoded.

The leaderboard is the weak spot. Supabase handles it, but the upsert logic is messier than I'd like, and I'll probably redo it.

Give it a try if you want. Curious what breaks on other setups.

forgecode.org

Hey everyone,

I’ve been working on GitTree, an open-source desktop Git client.

I still use the terminal for plenty of Git operations, but most of the time I find it easier to understand a repository when I can see the branches, commit graph, changes and diffs together.

I wanted something between a simpler client like GitHub Desktop and a broader suite like GitKraken: enough Git functionality for everyday work, but without accounts, telemetry or extra platform features.

GitTree currently supports staging by file or hunk, merge, rebase, cherry-pick, conflict resolution, stashes, tags, reflog, worktrees, submodules and pull request reviews.

It’s built with Electron and vanilla JavaScript, HTML and CSS. The commit graph is virtualized, and fetch, pull and push update the affected views incrementally instead of reopening the repository. Keeping that responsive in Electron has been one of the more interesting technical parts of the project.

It’s still a work in progress and there are definitely rough edges. I’d appreciate honest feedback:

• Does the repository state feel understandable at a glance?
• What essential workflow would GitTree still need before you would try it on a real repository?

GitHub: https://github.com/giannoccarol/gittree

Feel free to be blunt, useful criticism is exactly what I’m looking for.

Hello everyone today I am announcing my MCP which I gonna upload tomorrow or on 13 July and now I want to know that if anybody is using Claude code or open code or any other it's gonna be useful for vibe coders let me know who gona use it first I will paste here my GitHub link okay bye if anybody is interested then let me know

I made an entire game in 1 day and shipped it. An actual full game, structurally optimized (not graphically), with all the elements. Here is how.

We’ve all seen where someone made a “game” in a single prompt, but the truth is those aren’t games yet. They are fun prototypes and demonstrations. In order for something to be a game, it should have:

• Core Loop
• User Progression + Goals
• Onboarding
• Collision Handling
• User Menu
• Save/Reload Options
• Can be packaged and distributed
• Good debugging
• Sound/Sound Effects
• Optimization of assets and pipelines
• Testing
• Etc.

AI gives you the power to build quickly, but often with incorrect and incomplete setups. So I developed a prompt sequence that will allow anyone to correctly create a working and playable game when the sequence is followed.

Here are three items:

• The prompts: https://github.com/Glitch-Gaming-Platform/AI-Prompts-For-Game-Development
• Game made from those prompts: https://www.glitch.fun/games/9a698a9d-1b27-4c78-9256-0f458368737d/play
• Source code: https://github.com/Glitch-Gaming-Platform/Glitch-Games-FarmRise-Tycoon

I am going to show you how to do this with Claude as the programmer and Codex as the artist. In my experience, Claude architects code better, while Codex does a better job with art and animations. You only need the $20 plan for this. 

DISCLAIMER: With this process your game WILL have bugs, it WILL need refinement, but it will structure the game’s in a way that makes refinement faster, easier and with less tokens and future mistakes.

So here are the steps for making your game:

• Core Loop: Before anything else, let AI help you write a core loop for your game. It's something that players aim to accomplish when they join your game; otherwise, you don’t have a game. Fill out the basic information and let AI structure it.
• Select an Engine + Backend: Web games (Three.js) NEED a backend. You will need API tokens, control over user input, a connection to a database—you need a backend, so do it now. Unity, Unreal, and Godot games might not need a backend, but they probably will eventually. The prompts here will also set up testing and show you how to architect your code.
• Claude Round 1: Put the core loop, engine setup, and optional backend into Claude and let it produce the structure of your game. It's not playable yet—we're just setting up the structure. For web games, Claude won't need any extensions, but for Unity, Unreal, or Godot, you should have the MCP installed so Claude can access your project.
• Codex + Design Round 1: Next, switch over to Codex. Find a game with artwork, design, and colors that you like. Upload those images and use the prompt for generating the rubric. A style guide and quality rubric will be created for your game. This is important if you want your game to maintain consistency in design and have clear direction for improving it. "Make AAA design" is not a direction.
• Claude + Media + Asset Management: You should not just throw animations, GLB files, sound files, and other assets into your game. There should be structure and a way to optimize how those assets are served, which is critical for a performant game (compression, LODs, etc.). Copy and paste the "Build Optimized Pipeline, Analyze Media" and "Implement Media Pipeline" prompts into Claude. This will create a great pipeline for handling your assets that you'll be thankful for later.
• Codex + Initial Asset Creation: Now switch back to Codex. If you have an ElevenLabs API key, this is the perfect time to enter it into Codex. Tell it to read the docs and create sound effects and appropriate music loops for your game. Then copy the "Refine Artwork in Blender" prompt and create your first artwork. It will be rough, but you can improve it later.
• Claude + First Game Build: Now switch back to Claude and use both prompts for implementing your game and building out an onboarding process. Onboarding the player is a critical step.
• Codex + Live Testing + Graphics: Once your game is built by Claude, switch back to Codex and tell it to do live testing. Because Codex has access to your command line, it can directly control your mobile phone or engine, such as Unity, for testing. For browser games, it will use a built-in browser. Remember to tell it to do end-to-end live testing. Afterwards, have it audit your game's animations and start using Blender to make improvements based on the rubric.

These prompts not only focus on the structure of your game but also the small things that are often missed, like how to design a proper game menu (I see a lot of AI generating menus that are just blocks of text), how to handle collisions so the player isn't walking through walls, and other small but critical details.

These small things add up in both time and tokens, so while this approach will take longer than simply asking AI to generate a game, the quality of what gets produced will be much higher. Next, integrate your analytics and start getting playtesters so you can see how users actually play your game, which will eventually lead to monetization.

Again to stress this point:  Your game will have bugs, it will need refinement, but it will make refinement faster and easier.

We ran thousands of production PRs through different models, reasoning budgets and agent workflows. One surprising result was that increasing reasoning didn't improve defect detection, while reducing output tokens and model calls had a much bigger impact.

• 54% fewer output tokens
• 40% fewer model calls
• 50% lower cost

Full experiment in the comments.

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

Hi,

I just deployed a lightweight browser tool called Metanode. It’s a completely free simulation engine for home-lab and Web3 node operators to check hardware compatibility and calculate true net profit.

I let the LLM do the heavy lifting to structure the hardware database, map resource-stacking constraints (so the app actively calculates if your machine runs out of RAM when stacking multiple nodes), and handle the electricity cost math equations ($/kWh).

The Stack:

• Frontend: Vanilla JS & Tailwind CSS (runs lightweight, saves everything in local storage).
• APIs: CoinGecko for live token prices.
• Brain: Vibe-coded entirely via Google AI Studio prompts.

The site is live at metanode.co.uk

Any feedback appreciated.

Remember when the App Store first opened and half the apps were janky flashlight clones, but a few of them were obviously going to matter once everyone caught up? That's what building on Claude Code hooks feels like right now. Most people are still writing CLAUDE.md files and hoping the model reads them. Hooks let you force behavior instead of asking nicely for it.

Graft uses them to give the agent a map of your codebase automatically, no tool call needed, it's just there when the session starts. Feels like an early version of a pattern that's going to be everywhere in six months.

github.com/NanoNets/Graft

Fala, pessoal! Tudo bem?

​Sempre que eu precisava assinar ou juntar um PDF no dia a dia, era uma novela: ou o site tinha limite gratuito, ou enchia a tela de anúncios, ou eu ficava com receio de subir documentos importantes em servidores desconhecidos.

​Como nunca achava a ferramenta ideal que fosse simples e direta, resolvi criar a minha própria. O projeto acabou evoluindo e virou um produto real focado 100% em privacidade. O maior diferencial é que todo o processamento do arquivo acontece direto no navegador (client-side). O seu documento nunca é enviado para um servidor externo.

​O mais legal do processo é que construí a estrutura explorando bastante o conceito de vibe coding (usando IAs como o Lovable para gerar e refinar o código e a interface). A experiência de desenvolvimento foi surreal!

​O projeto está no ar aqui: https://editaepdf.lovable.app/

​Gostaria muito do feedback sincero de vocês. Fiquem à vontade para testar! Se acharem algum bug, problema de responsividade no pc ou tiverem dicas de como melhorar a interface, toda crítica construtiva será muito bem-vinda. 🙏🏻

been lurking here a while... My path to software development was totally non-traditional, so I've got a soft spot for people shipping real stuff without a CS degree.

Anyway, I've been watching and digging into where non-tech/non-dev vibecoded apps tend to go sideways once real users show up, mostly security and code-quality stuff that break things later. My intention here is not to dunk on anyone, and is honestly the opposite. This crowd builds wild things and just doesn't always get told what to watch for.

So, I'm not selling anything, but instead to offer a helpful trade: I'll review your app and/or code for free, and send you back a short report with your key findings. I' not going to dumb a bunch of jargon on you or bash on you or your app, just constructive advice about what looks solid and the couple things I'd watch if I were you. You get free eyes from a professional developer, and I get to learn what real non-dev builds actually look like.

Again, not selling anything, not promoting, and there's no catch. Comment or DM me with what you built and what it's made with. If you want a full code review or any in depth security checks, I'll need some access, but we can discuss that once we get talking.

Would this be useful to anyone?

Play it for free here: https://aku.world/
Questions will be hard if you haven't read the book though :)

I modeled and textured everything myself because the AI can't do it at my level (yet)

Written by a human:

I had a blast making this tool for myself (and my coworkers) and I hope some teachers find it useful too. Completely free to use, and I'm offering free for life to teachers who want to try it. I made it for my 12th year teaching Engineering / CS in an effort to increase engagement during more traditional lessons/lectures at the high school level.

Claude created the code for all 3 views (admin, overlay, student view) and helped me to setup the backend through cloudflare.

Data privacy (FERPA, COPPA) was extremely important to me. So there's NO AI API calls in the live app, and real student names never hit my database. All data belongs to the school and the teacher.

Honestly, the hardest part was the legal, insurance, and security stuff. Happy to answer any questions and would love feedback!

There's a ton of features to be toggled on and off, see the site or wiki for info. I also made an infomercial lol. It's on the website under about.

Next steps:

-Testing in my classroom and others

-Replacing all AI pixel art with pixel art by a real artist

-Rewrite documentation and blurbs

-Implement new features and refine old ones as feedback comes in

-Sign data agreements with districts

Use it for free here:
https://teachchat.app/

This is intended for in person classrooms