u/Ecstatic-Basil-4059 — reddlx

...a site that deals you a golf-excuse.

Link: https://excusecaddie.xyz

Drop your best one‑liner excuses, and i will add them :)

Got 3 apps to Play Store using this sub (latest was Slothy). Here’s what actually works:

#1 Create a Google Group
Don’t add testers manually. Use a group and share one link, saves a lot of time. Go to https://groups.google.com, click create group, add name and email, set it to email list, allow anyone with the link to join, then just share the link.

#2 Test properly and ask for screenshots
Don’t just install. Open the app, use it a bit, send a screenshot and give short real feedback. Ask for screenshots back, it filters out people who don’t actually test.

#3 Focus on real feedback, not fake reviews
A lot of my testers gave feedback I could actually improve from, that’s way more valuable than asking for 5-star reviews. Bugs, small issues and confusion points help you fix the app and make it better over time.

#4 Stay active and treat it seriously
Keep testing during all 14 days, don’t disappear after day 1. Treat it like a real exchange, not spam. Effort in = better testers back.

Worked for me multiple times.

reddit.com

u/Ecstatic-Basil-4059 — 16 days ago

▲ 4 r/vibeprinting

paste your GitHub username and get a full view of your entire profile, all your public repos, split into dead, struggling, and alive.

there’s also a live README badge you can copy and drop into your repo, so it shows your graveyard stats automatically.

site: https://commitmentissues.dev/
repo: https://github.com/dotsystemsdevs/commitmentissues

u/Ecstatic-Basil-4059 — 20 days ago

▲ 8 r/vibeprinting

Hey,

I’ve been spending way too many hours lately getting stuck in loops with Claude Code and Cursor, either over-engineering features before validating them, or losing context mid-build because I didn't have a solid PRD.

To fix my own workflow, I built VibePrompt. It’s a minimal site that breaks down the building process into 9 distinct stages (Research → PRD → Context → Build → Quality, etc.) with ~40 specific prompts I've battle-tested.

The Site: https://vibeprompt.tech
The Repo: https://github.com/dotsystemsdevs/VibePrompt

What’s inside:

Structured Stages: Instead of just "coding", it forces you to think about Agent Setup (CLAUDE.md/AGENTS.md) and Quality/Testing before you ship.
Zero Friction: No accounts, no "AI credits", no newsletter popups. Just markdown files rendered for easy copying.
Open Source: Built with Next.js 16 and Tailwind v4.

I’m curious how you guys are managing your "vibe" sessions.

Does a structured workflow like this make sense, or does it kill the speed?
What prompts are you using to keep your agents from hallucinating during deep refactors?

Would love some brutal feedback on the tool or the prompts. I’m trying to make this the "playbook" I wish I had when I started.

u/Ecstatic-Basil-4059 — 24 days ago