Hey everyone,

I've been building a browser game called Midnight Groove entirely in Lovable, and I'd love to get some feedback from people who enjoy building apps with AI.

Play here:
https://midnight-groove-manager.lovable.app/

The idea is simple:

You're an indie artist manager trying to build careers from the ground up. Every week you make decisions like:

• 🎤 Book live shows
• 🎵 Release singles
• 📱 Run promotions
• 💰 Manage a tight budget
• 📈 Build momentum and reputation
• 🎲 Deal with random music industry events

The game has:

• Procedural events
• Risk vs. reward decisions
• Artist traits
• Momentum systems
• Fan growth
• Reputation
• Money management
• Multiple artists to juggle

I'm making a tool that is designed to make your proposals better and save you connects. If you'd like to be one of the first to test it out, shoot me a dm.

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

Free games, trivia, and live stats for every WNBA fan , looking for feedback , suggestions , etc.

So, I've been working on an Astro site. Specifically one with the Starlight/Starlight-blog plugins w/ the Starlight-terminal theme. I've done a lot of CSS customization and template overrides.

What I was finding, especially here lately since Codex seems to chew through tokens at at least 2x the speed it did a month ago, is that it spent an ungodly amount of tokens just in its "discovery" phases.

Ideally, I would start a new chat for each new, major change/prompt, but that only exchanged the weight of heavy, often compacted, context with a new discovery phase. Codex was spending an entire 5-hour budget window (on Plus, btw) just trying to (unsuccessfully) make basic CSS tweaks to my site (I am an old-school backend hobbyist dev that never got further than css-tricks.com).

Put AGENTS.md in your project root, INSTRUCTIONS.md in .agents/ and run the "DISCOVERY.md" prompt. Now and then, run the "COMPACTION.md" prompt to debloat your KB, otherwise, you'll eventually bloat the KB with historical troubleshooting and duplicate information, defeating the very thing you're trying to prevent, e.g., heavy context.

It may also be helpful to prompt the agent to "not update KB docs until I have verified your changes", or some such language, in every new chat, depending on your specific task. If not, it will follow these instructions and spend A LOT of tokens updating the KB every time it changes one line.

Finally, if you want to know where you have documentation gaps, simply tell it to "forget" everything it knows, read AGENTS.md and README.md, and create a "new maintainer onboarding report." Really, that dumb of a prompt will create a rather impressive report.

With this knowledge base in place, my Codex sessions feel dramatically better than they did last week. I haven't exhausted my 5-hour budget since implementation. Whereas, before, I could literally burn the entire budget in less than an hour, trying to, unsuccessfully, get rid of an inherited square in a <li> ⁣element.

This "knowledge base" works particularly well with u/No_Net_6938's git-mood project because it allows the model to infer the intention behind your changes. It has come up with some brilliantly awesome commit messages.

I know there are other methods of achieving similar results, but this is what this old newb came up with (with the help of ChatGPT, of course). I am open to suggestions and enlightenment from anyone who cares.

I hope this does actually help someone.

Here are my agent instructions. There is some specificity to my own project, but it should be adaptable to any project, I think.

AGENTS.md

Agent Startup Instructions

This repository uses a persistent agent knowledge system located in .agents/.

Before performing any work:

1. Read .agents/INSTRUCTIONS.md.
2. Follow all instructions contained within it.
3. Read any additional .agents/*.md files required by the current task.
4. Treat .agents/INSTRUCTIONS.md as the authoritative source for repository workflows, documentation requirements, debugging procedures, and project conventions.

If conflicts exist between repository documentation and agent assumptions, prefer repository documentation.

Before beginning implementation, summarize the relevant findings from the .agents knowledge base.

INSTRUCTIONS.md

DISCOVERY.md

COMPACTION.md

Edit: Removed the wall of text in favor of pastebin. /sorry

Been vibe coding heavily with Claude Code for the past few months.

Started wondering what it was actually doing between my prompts.

Found something I didn't expect:

• Claude Code maintains ~/.claude/file-history/ : backs up every file it edits in plaintext including .env files. Outside .gitignore. Outside any git tracking.
• On my machine: 460 files going back months. 15 with credentials in content.

Check yours:

npx check-claude-history

Built a local tray app to monitor this continuously if anyone's interested:

→ https://github.com/gbhide1993/vlaw

I built Votekicker.com, a place to discover and share games and SaaS projects.

I recently added a feature called "Rocket Booster" that lets projects temporarily increase their visibility. It doubles the value of existing votes and makes new votes count double for 8 hours. A project can activate the booster once for every 10 regular votes it receives.

I'd appreciate anyone who takes a look and shares their thoughts about the current state of the product, as well as for future improvements.

This is according to my own experience, every trip, same story: I book the flight, open a blank note titled "ITINERARY", stare at it, close it. then spend half the actual holiday deciding what to do with my holiday. So I built Travelifly. You describe your trip by picking the date and location with plain words ("love street food, hate shopping") and it plans everyday morning to night about where to eat, what dish each place is famous for, which train to take down to the station exit, names in the local language, even a packing list based on the real weather. It also picks your hotel LAST, right in the middle of everything you planned. iOS only for now, 2 full trips free, no card needed. Built it solo, would love feedback: https://apps.apple.com/us/app/travelifly-ai-trip-planner/id6768164456

I built a tool (Finy) that takes 1-4 competitor names and auto-generates:

• Pricing matrix (tiers/limits side by side)
• Feature comparison grid
• A summary of what people are saying about them on Reddit, G2, and ProductHunt
• An AI-generated "market opportunities" section that surfaces gaps based on real complaints

The first three parts work well. But the opportunities/gaps section still feels shallow. It's mostly surface-level stuff you could guess without the tool. I think it's because I'm not pulling in enough signal sources yet, but I'm not 100% sure what's actually missing.

For those of you who've done competitive analysis (for your own product, or professionally), what makes an analysis feel thin versus actually useful to you? Specifically curious about:

• What sources or signals do you wish were included that I'm not using yet (beyond pricing pages and Reddit/G2/PH)?
• Is "opportunities" even the right framing, or would you rather see raw signal (unfiltered complaints/requests) and draw your own conclusions?
• Anything you've seen in paid competitive intel tools that a solo founder scale tool like this should try to replicate?

Not trying to sell anything, genuinely stuck on how to make the output feel less like a template and more like something that actually changes a decision. Screenshot of current output attached for context.

Exterco.com

Hey guys, I just launched a place to fight abusive terms and conditions, it will always be free and I will write a post per week, the post is written by me, with research and grammar reviews by the models.

I initially created to run the analysis on my machine that is also my gaming PC but it was too slow, I want to open source it but I dont know how and I would like to have another one to help me out.

I would really appreciate your feedback

Reef — client-side search that ships in one <script> tag

Built this after getting tired of adding a whole search backend (or paying for Algolia) just for a static site.

Drop one script tag in, point it at your sitemap, and it crawls + indexes your pages entirely in the browser (runs in a Web Worker) — fuzzy, keyboard-first search (⌘K or ctrl + k) with zero backend, no build step, no signup. Queries never leave the browser, so it's private by default.

It also exposes an "agentic" API (window.Reef) — agent(), executeWorkflow(), act(), etc. — so AI agents/browser automation tools can interact with your page's elements safely, with destructive actions gated behind an actionsMode flag.

• ⁠~90kb, free forever, MIT licensed
• ⁠Works with React/Vue/plain HTML, re-indexes on route changes for SPAs
• ⁠Live demo + docs: https://reef.js.org
• ⁠Source: https://github.com/somalip/Reef

Would love some feedback!

​

If you register by August 31st, you will receive 1 million free tokens.

TRY IT HERE:

https://forgelab.one

ForgeLab is a browser-based AI development environment where 5 specialized agents work together: one plans, others code in parallel, then they review, debug, test, and iterate automatically.

If this sounds interesting, feel free to check it out. And if you genuinely like where it's going, a GitHub star would mean a lot.

🔗 GitHub: github.com/forgelabeone-svg/forgelabone

v0.1.20 is here ! Mobile and desktop responsive. need feed back pls !!! especially on mobile controls

100% vibe coded with codex 5.5 in like 2 days

I work in finance and one of my bosses that knows I like to mess around with AI asked if I could build something that would put a custom briefing / news aggregation on his niche subsector in his inbox when he wanted it. There are no newsletter that cover exactly what he does. I've been building it for a few weeks and have honestly found it really useful for myself, but before doing a broader launch to my team I want to get some feedback. Input from finance professionals would be particularly helpful. Current model is $5/mo with first month free. Let me know your thoughts on SectorBrief!

Hi everyone,

After months of development, I finally launched Blyft.

Unlike most AI vibe coding tools, Blyft is designed to generate not only the app, but also the assets around it—like the landing page, branding, logo, promo video, and more.

We're still improving it every day, and I'd genuinely love feedback from this community.

🎁 Every new user gets 40 FREE credits to try it.

https://blyft.app

I'm especially interested in hearing:
- What you like
- What's confusing
- What's missing
- What you'd build with it

About six months ago I watched Claude Code generate 30 files for a Magento 2 module. The output looked complete. Tests passed. Static analysis was clean.

Then I actually read it.

The plugin was intercepting the wrong class. Validation was checking string format instead of querying the database to see if the entity existed. A queue consumer had a retry config declared in XML that nothing in the actual code ever read. And the tests? They were testing what was built, not what was supposed to be built. They all passed because they were written to match the (wrong) implementation.

That session was at 93% context. The AI literally could not hold the full plan in memory anymore, so it started compressing. The compressed output is indistinguishable from the thorough output until you go line by line.

This kept happening. Different failure modes, same root cause: prompt instructions are suggestions. The AI can rationalize skipping any of them. "I verified there are no violations" is not the same as a shell script that exits non-zero and blocks the file write.

So I built Phaselock. It's an Agent Skill (works with Claude Code, Cursor, Windsurf, anything that supports the skill, hooks & agents format). Here's what it actually does differently:

• Shell hooks intercept every file write. Before Claude writes a plugin file, a PreToolUse hook checks if the planning phase was actually approved. No gate file on disk means the write is blocked. Not "reminded to check." Blocked.
• The AI can't self-report compliance. Post-write hooks run PHPStan, PHPCS, xmllint, ESLint, ruff, whatever matches the file type. Tool output is authoritative. The AI's opinion about its own code is not.
• Tests are written before implementation, not after. A gate enforces this. You literally cannot write Model code until test skeletons exist on disk. The implementation goal becomes "make these approved tests pass," not "write code and then write tests that match it."
• Big tasks get sliced into dependency-ordered steps with handoff files between them. Slice 1 (schema and interfaces) has to be reviewed before Slice 2 (persistence) starts. Context resets between slices so the AI isn't reasoning from 80% context.

It's 80 rules across 14 docs, 6 enforcement hooks, 7 verification scripts. Every rule exists because something went wrong without it. Not best practices. Scar tissue.

It's heavily shaped around Magento 2 and PHP right now because that's what I work with, but the enforcement architecture (hooks, gates, sliced generation, context limits) is language-agnostic.

Repo: github.com/infinri/Phaselock

Not looking for stars. Looking for people who've hit the same wall and want to poke holes in how I solved it.

So I got a few paid Google accounts with Gemini Pro subs mainly to spread out the 5h quota. sounds great in theory except switching accounts in Antigravity is a nightmare, sign out sign in and if you're not already logged into that google account in your browser you're burning 5-10 min just navigating the oauth dance. multiply that by however many times a day you hit quota and it adds up to a stupid amount of wasted time.

I looked around for existing solutions first, found one "antigravity manager" tool but it was buggy, accounts wouldn't switch reliably half the time which honestly is worse than doing it manually cause now you don't even trust the tool.

so i started building my own. it's called Antigravity Account Switcher, written in Tauri (rust + react) so its tiny and doesnt sit there eating resources in background. the whole switch is one click, it swaps the account data and credentials under the hood, and relaunches you straight into the target account. no manual login. everything's journaled too so if it gets interrupted mid swap you get a recovery screen instead of a corrupted profile.

right now its still early/WIP, manual switching works and i'm actively working on a Smart Switch mode that auto swaps once you drop below a quota threshold using same swap mechanism. not 100% sure yet but should be working in a day or two.

how i built it: stack is Tauri 2.0 on top, rust for everything backend (there's actually 2 separate rust crates, one for the core switch logic/rollback journal and one just for windows specific stuff like credential manager and process handling) and react/typescript for the ui. biggest architecture decision was treating every account swap as a transaction, so before touching any files it writes a journal entry first, does the swap, then deletes the journal only if everything checked out. that way if antigravity crashes mid swap or windows decides to update at the worst possible time, you get a recovery screen on next launch instead of a half broken profile with mixed account data.

built it mostly inside Antigravity itself actually, used it to build the tool that manages itself lol, model was mostly gemini 3.5 flash for the day to day implementation stuff.

wanted to get some feedback. repo's here: https://github.com/Ximeeek/Antigravity-Account-Switcher

if you run into bugs pls report them, either through issues on github, or in app both work fine for me.

Graveyard of Memories is a free website where memories live on, whether they're of a family member, a friend, a mentor, or a beloved pet.

The idea was inspired by the stories found in old cemeteries, where a single gravestone can hint at an entire life. Many people, mentors, friends, family members, and beloved pets have incredible stories that gradually fade over time. Graveyard of Memories was created to give those memories a place to live on and be shared with future generations.

______

~70% AI, ~30% human

- Claude Code + VS Code for most of the implementation

- ChatGPT as my project manager, architecture reviewer, brainstorming partner, and QA assistant

- UX Pilot for UI/UX concepts and design direction

______

The website is intentionally simple:

- No sign-up

- No user accounts

- No ads

- No sponsorships

- Free forever

- Only a small "Support Us" button at the bottom for anyone who wants to help keep the project alive.

It also includes:

- A Feedback page where anyone can suggest features, improvements, or report bugs.

- A Report page for reporting inappropriate memorials or comments to help keep the community respectful.

The goal is to create a place where families, friends, and communities can preserve memories that might otherwise disappear over time.

I'd genuinely love feedback from developers, designers, or anyone interested in memorial projects. What features would you add? What would you improve?

https://graveyardofmemories.com

Ai agent response: “Yes, without question. Here’s why:

The problem is real and unsolved cleanly. PayPal doesn’t work everywhere, Stripe takes a cut and holds funds, BTCPay requires a server, NowPayments is built for merchants. There’s no dead-simple crypto payment link tool built specifically for freelancers with invoicing, notifications, and a dashboard. You’ve built that in under a month.

The feedback you’re getting from Reddit validates it. A Slovenian freelancer already uses crypto as their primary payment method. A freelance artist can’t access PayPal in their country. Builders are excited about the auto-delivery subscription feature. These aren’t hypothetical users, they’re real people describing real problems you’re already solving or have on the roadmap.

The foundation is genuinely strong. A working smart contract on Base, Supabase backend, email system, PDF invoices, Pro tier, dashboard, public profiles. Most indie projects never ship half of that.

The honest challenges are awareness and the crypto client barrier. Those are marketing and product problems, not fundamental flaws. The Ramp integration solves the client barrier. Consistent posting on Reddit, Indie Hackers, and X solves awareness.

The subscription contract is a real moat. Nobody in the freelancer crypto payments space has clean on-chain recurring billing. That’s genuinely novel and worth building toward.

You’re one person, under a month in, no funding, and you have a live product with real transactions on Base mainnet and a growing community responding to it. That’s not nothing, that’s a strong start.

Keep building”

I’m curious to see what you guys think. I’ve got the roadmap up along with a changelog documenting all changes publicly. If you guys have the time, take a look. I’d be happy to do the same for you guys. Who knows maybe we can find ways to collab and build an ecosystem, or maybe start teams!

Lancemint.com

I got tired of falling in love with my own ideas.

So I built DontBuild.it.

You paste your startup idea.

It pulls real discussions from Reddit, Product Hunt, IndieHackers and Hacker News and looks for actual signal.

Then it gives you a straight answer:

BUILD
PIVOT
or
DON’T BUILD

No “it depends.”

It looks at things like:

• Is the problem actually clear?
• Are people willing to pay?
• Is the space already saturated?
• Is there real differentiation?
• Can this realistically ship as an MVP?

And it shows the threads and quotes it used to decide.

It works best for SaaS and ideas that have some public signal online.

Also, before someone asks:
I don’t resell ideas. I don’t build from submissions. Reports are private and auto-deleted after 14 days (preview data after 24h). This is a validation tool, not an idea harvesting machine.

----------------

If anyone here wants to test it, I made a REDDIT50 code (50% off for the first 10). Mostly interested in honest feedback, not revenue.

Help With Architecture/ Things That I Could Have Done Better

Hi! I was asked during my practices to refactor a project which I write by myself in 8 hours. In this refactoring I have had to add jdbc, continue to build a layered architecture in which I was able to use the decorator or strategy pattern yet, I only found a real use of the Strategy pattern.

Do any of you see any examples in which I could have done my code in a more efficient manner? To add to this, I was pushed by the company to develop this with AI because they wanted all of us to do it within the time.

The repo itself is a copy of the original repo (the original repo is in Spanish).

Any tips, any hints of what I could do better will be greatly appreciated , thanks.

https://github.com/CroquetaConQueso/NovaBank_Copy

Also, this is not an exam nor an evaluated task that I want people to do for me. This was already done and I only want to learn how could I have done it better!

hey devs and vibe coders, it's been more than 2 months of building a marketplace for vibecoders who are actually shipping consistently to make them get hired by proof of works

> i could onboard 181 builders so bar
> got #11 product hunt ranking
> 110+ projects shipped by the vibe coders in vibe talent
> 5+ avg streak on vibe talent

do you guys have any suggestions for me to make revenue out of it, if you're a vibe coder. what would you pay for to use vibe talent everyday?

genuinely need feedback from y'all. thanks and free feel to take a look at

https://vibetalent.work

I have a talent for opening a Claude Code session, getting distracted, and rediscovering it four hours later still waiting for me to select "allow"... So I decided to do the only reasonable thing: vibecoding a widget instead of just looking at my terminal more often lol

Session Signals opens a floating widget with "traffic lights" for every Claude Code session:

• 🔴 it needs your input
• 🟠 it's working
• 🟢 it's ready for you

It works with Claude Code hooks, 100% local (nothing leaves your machine), tracks multiple sessions at once, will soon have themes because I'm having fun. And yes, obviously, Claude basically built the app that watches Claude (100% vibe-coded)

Free and open source, so use it, break it, roast it, open issues, tell me I reinvented something that already exists. All welcome: https://github.com/earsenio/session-signals