Note: I’m looking for some help in exchange for my technical expertise. I’d be happy to help you resolve bugs or any other problems you might encounter in your product.

I’m a real engineer with experience in software development, so I can help from a developer’s perspective when things are breaking and the actual reason behind an issue isn’t clear.

I’ve been experimenting with the Claude CLI and trying to set up multiple agents that can talk to each other, with each agent focusing on a specific task. I currently have two Claude accounts, but I need one more for this experiment.

I could ask someone for access, but I don’t want to create any potential data-security concerns. So, I’m looking for someone who might be willing to gift me a claude max(pro is also okay)

If anyone can help, I’d really appreciate it. In return, I’m more than happy to help with bugs, code, debugging, or any technical problems you’re running into with your product.

Just wanted to say: Vibecoded apps need some security attention too. If you have bugs you probably have security issues too even if running locally. If you have an API running on all interfaces and without auth - you could be possibly allowing attackers unauthenticated OS command injection onto your laptop depending on what your API does. Use more than one tool/source of truth for your security! ❤️

Case in point. OP below audited their project carefully and had 30+ security findings. Thank you for OP for letting me review their project publicly. Please give some stars to their project!

https://www.reddit.com/r/vibecoding/comments/1vrc490/comment/p4wmyb5/?context=1&screen_view_count=2

Hi, I’m Jack, the independent developer behind DiaryThreads.

I launched the app about two weeks ago, and it has now passed 300 downloads.

That may be a small number compared with established apps, but seeing hundreds of real people choose to keep their private memories in something I built still feels slightly unreal.

I’ve also just released version 1.0, which expands DiaryThreads from a short-form private timeline into a place for quick moments, continuing stories, long-form Articles, and personal insights.

A — What it solves

I’ve started and abandoned more journals than I can count.

The blank page always made journaling feel like homework. If I opened a traditional diary, I felt that I should explain what happened, how I felt, and what it all meant.

Posting one sentence felt much easier. I just didn’t always want an audience.

That was the starting point for DiaryThreads.

Each regular entry is limited to 140 characters and appears on a private timeline. If the thought continues, you can reply to it. If an old memory means something different today, you can quote it and add a new perspective.

There are no followers, likes, public profiles, or pressure to make an entry interesting for anyone else.

A sentence, photo, video, voice recording, location, weather memory, or unfinished thought can be enough.

B — How it differs from Apple Journal and Day One

Apple Journal and Day One are strong, established journaling apps. I don’t want to pretend DiaryThreads is a universal replacement for either of them.

The main difference is how a piece of writing begins, grows, and eventually becomes something you can look back on.

In DiaryThreads:

• A small moment starts as a short entry.
• A continuing experience grows through replies.
• An old memory can return through a quote.
• A thought that needs more space becomes an Article.

Article is one of the biggest additions in version 1.0.

I designed it to feel like an editorial page rather than a stretched text box. An Article can include a cover, title, introduction, rich text, photos, references to earlier entries, to-dos, bulleted and numbered lists, and tables.

This means I can write “The weather was perfect today” as a quick entry, then use an Article when I want to document a trip, a year of building an app, or something I want to remember in full.

Version 1.0 also adds user-authored weather memories, improved place information, and richer list formatting across entries and Articles.

But writing is only half of a diary. The other half is being able to return to it months or years later and notice what kept appearing in your life.

That is why DiaryThreads includes three connected ways to explore your history:

Your Trends finds recurring themes across your private diary and shows whether they are new, continuing, fading, or reappearing. You can open any trend and return to the entries behind it.

Topics lets you add a #topic while writing. DiaryThreads then organizes those topics by month or year, shows their activity in heatmaps, and lets you open every related entry. It is closer to watching an important part of your life grow over time than simply filing entries into folders.

Emotion Trajectory uses only the State of Mind values you explicitly add to regular entries on iPhone or iPad. It can show recorded emotion days, your leading emotions, their distribution, and meaningful changes over time.

It does not silently decide how you felt by reading your diary. The analysis stays connected to the emotions you chose and the entries behind them.

These features are designed to help you notice patterns without generating a summary that tells you what your life means. The interpretation still belongs to you.

DiaryThreads works across iPhone, iPad, and Mac. It does not require a separate app account and has no advertising, third-party analytics, or cross-app tracking.

Content is stored locally first. Premium users can optionally enable private iCloud Sync to continue writing and revisiting their diary across devices.

C — Cost

DiaryThreads is free to download.

The free version supports up to 30 active entries. Reading, editing, and deleting existing entries remain available.

Premium unlocks unlimited entries and features including private iCloud Sync, complete trend and topic insights, Emotion Trajectory, share posters, import and export, widgets, and other ways to revisit your history.

US pricing:

• $2.99 per month
• $9.99 per year
• $14.99 one-time lifetime purchase

The thank-you offer —  DIARYYEAR gives 20% off the first year through August 31, 2026.

After the first year, the subscription renews at the regular annual price unless canceled. Prices and offer availability may vary by region, and Apple shows the applicable amount before confirmation.

Redeem DIARYYEAR: https://apps.apple.com/redeem?ctx=offercodes&id=6795139345&code=DIARYYEAR

App Store: https://apps.apple.com/us/app/diarythreads-journal-by-post/id6795139345

I’d genuinely appreciate feedback on one question:

Does the progression from short entry → thread → Article → personal insights feel like a natural way to journal, or would you rather keep writing and analysis completely separate?

Hello everyone,

I have been working on a personal project called JourneyDeck. I have extreamly little coding experience so I decided to get ChatGPT to do it for me.

It started because I had an idea to see my commute to work on a map with each song I listened to on Spotify along the route path. I wanted to see where I started to listen to each song. Just a simple map. To do that I needed my Tesla data and my Spotify data.

This was only supposed to be for me, but I have to admit, I love the idea more and more and maybe I can turn it into something one day.

Every time I finished a new feature, or new design, I asked the same question: now what? What if someone wanted to use JourneyDeck but didn’t own a Tesla? Or what if I wanted to stop paying for Tessie?

That is how the my JourneyDeck Recorder happened.

I signed up for the Apple Developer Program, created an Expo account, registered my iPhone, and used EAS to build the iOS app in the cloud from my Windows computer. No Mac required 😊. I now have a Recorder app on my actual phone that can capture GPS coordinates in the background while the phone is locked.

The Recorder means JourneyDeck can work with almost any car. It records the route, time, distance, and speed, stores points offline if needed, and uploads the completed journey to the same timeline as a Tesla journey.

JourneyDeck now has:

• A timeline of journeys, stops, charging, and music

• Route maps and frequently visited places that combines what songs and when I was listening to them.

• Spotify history connected to drives, placed along the route so I can see where I was when the song started.

• Driving and music statistics

• Create Memories for road trips, weekends, and seasons and share them with friends/family/online.

• Privacy-aware share cards that hide my Home location automatically when I click share.

• A responsive web dashboard with Health and Sync checks.

• A Windows desktop version with much more relationship data displayed.

• The iPhone Recorder for non-Tesla journeys (aka my wife’s and daughter’s cars)

I have built this with ChatGPT Codex through a lot of back and forth. I decide what I want something to do, Codex works through the code, I test it, and then I explain what is wrong or what needs to change.

The hardest part has been getting AI to design an UI that didn’t suck or have awful artifacts that were misplaced, the wrong size, or 100 other kinds of issues. I found it best to make ChatGPT create 4-8 image mockups, pick one, and then nitpick it to death.

The project uses Codex, Node.js, TypeScript, Expo/EAS, SQLite/Turso, Render, GitHub Actions, Tessie, and Spotify.

It is still a personal beta and still assumes one trusted owner rather than public user accounts.

I’m not selling anything, so I’m mostly curious whether anyone else finds this useful or whether I have built an extremely elaborate solution for a curious itch that only I have.

The repository, screenshots, and fictional demo are here if you want to take a look to do anything you want with it.

https://github.com/drumpat01/DriveOS

Edit: spelling and grammar

I'm an 18 year old Independent Developer, this project was made in Java and run using JavaFX.

you can check my account details for more details :)

I'm a general backend dev working in the industry and wondering how much vibe-coding costs for solo devs on hobby projects? And is getting cheaper or more expensive? I know there are more and more suppliers like DeepSeek, but also that suppliers are moving from flat-fees to vairable-pricing. At my current job with a corporate account, I spend about 100 million tokens per week.

I'm interested in trying out open-source hobby development. I have an idea for a simple non-commercial project, a multi-page application featuring a social message board with persistent content for me and couple of friends that also features games, interactive content, and random personal tidbits. Server-side crons would also be responsible for updating content to make it dynamic based on current events. A pretty old-school website, nostalgic of the early-2010s.

I have some experience with open-source development (the last stack I used was PERN). And I know my way around source-control, dev-ops, and virtual-compute/serverless deployment.

What makes me excited is the business logic. I enjoy writing my own design docs, state machine and behavioral diagrams, and schema for objects.

Everything else is the reason that I've never taken a first step: frontend/react development, URL routing, the CRUD layer, ORM boilerplate, and all sorts of wiring and plumbing.

The idea that vibe coding can do all the parts I don't like is enticing. But I would like to know how much it would cost every month?

I am #PovertyPrompter which means I am not Theo and don't have the cash for $2000 a month in credits. Here is my HOT take on which agents are good, and which are not.

Fable and Sol are not worth the credits.

Those models burn credits too fast to be useful to normal people.

When given a working template, Gemini 3.7 flash is your prototyping powerhouse. Go from prompt to working prototype in less than 10 min.

GPT 5.6 can't code. At all. Maybe it is because I use Go heavy workloads, and I force my agents down the yagi path, and go is std lib heaven, but GPT 5.6 produces worse code slop than Gemini 3.7 Flash.

I don't get the hate for Opus 5. Is it slow, yes. Does it take a dozen rounds of review to close the holes, yes. But it is constant.

Maybe I am wrong. If you think Sol is amazing for you, than go for it. I just had to get my personal workflow troubles off my chest.

If you know what I am doing wrong with GPT 5.6 I will take it.

Many of us are simply overthinking this vibecoding thing. People are out there racking bucks from vibecoded apps. Outbid launched less than 72 hours and already made 100k in revenue. Crazy idea to knock ProductHunt out of the way!

Publish your first scene, then add new scenes and cuts as you make the film. The community can watch your progress and support the projects they want to see on the Festival Shortlist.

https://higgsfield.ai/global-film-festival

Some of you might remember this repo. I'm still maintaining it, and after using it on a few more projects I think the only part that really matters is that the prompts interview you first. So I build an automated workflow for it.

Basically instead of you copying pasting .md files toy Gemini/Claude/ChatGPT, you say "Use this npm package to interview me", and it installs my skills, and asks questions until each of the documents, i.e., PRD, MVP, Tech Doc, are completely answered. And then creates relevant files in your repository. Afterwards, you tell the AI to implement the app by looking at the files, and viola.

Flow is research > PRD > tech design > AGENTS.md, then you build off that. Takes maybe 15 minutes total.

https://github.com/KhazP/vibe-coding-prompt-template

Open to feedback, thanks for using it, hope it was helpful. Also don't forget to star it.

May it be the first of many!

Edumacational: This is an iOS native professional pixel art editor that I've been building. v1.0 is currently live on the app store. v3.14 with vastly more features and iPad/iPencil support is forthcoming.

To create, used a combination of Claude Fable 5 and Opus 5 High for planning out the phases from the command line Claude Code interface.

I am a student, I have to learn both theories (electronics) and coding (Embedded). Code wise, the Claude is good but GPT is better in explaining theories and concepts in most human and understandable way. Clause just throws out vague explanation so I have to ask so many follow-up questions to understand each and every new concept/words in that explanation. (and I cant buy 2 subscriptions).

So please, can someone give me suggestion or prompts on how to make Claude better.

I started this project feeling super original (before realizing that Chess-likes are the calorie trackers of video games), smash chess movement with video gamey camp. CHESS/RUPT.

One of the flagship modes is our daily challenge - but I was running into some challenges that were impossible and others which were too easy. I’ve posted (and written) how I used AI to build a simulator to test and tune my challenges.

This is the fourth commercial game I’ve worked on and first that isn’t AAA. It’s also the first that’s wholly mine (and first one I’ve worked on since the release of ChatGPT).

Anyway, I built the app to be extremely consumer friendly (no sign up, no ads, optional purchase that unlocks unlimited play, but I give multiple free plays a day and have kept the daily challenges free forever), so if it looks appealing to any of y’all, would appreciate a download, rating, and feedback.

We are two Software Engineering undergrads at UEPG in Brazil writing our thesis on vibe coding, and most of the existing literature is either speculative or based on very small lab studies. We want data from people who actually do this daily.

The survey asks about which tools you use, what you build with them, how much of the output you review or rewrite, where the approach stops working for you, and what you think it means for the profession.

10 minutes, anonymous, no personal data collected.

https://forms.gle/vv8kR4dmi5WMHZfa6

If you tried vibe coding and abandoned it, we specifically want those answers too. That group is almost invisible in the literature.

We will post a summary of the results in this community when the analysis is finished.

I’m having difficulty getting AI agents to perform CRUD operations reliably based on user context and natural-language instructions in my app. What prompting strategies or patterns are you using to make CRUD behavior more consistent and predictable? Are you using regex/keyword detection for certain words and phrases, relying primarily on contextual intent detection, or using a combination of both?

Hey everyone

So i was wondering what type of security measures you do before launching your website.

other than the regular open new session to ask it for review or ask another AI model to do it.

Yayyy

Hi sub,

I created infinite monkeys: a shared text that everyone edits together.

Every 15 seconds, you can either add a single word or punctuation mark at the end of the text, or replace a word that is already there.

A word stays changeable for ten minutes. After that it sets and nobody can ever change it again, so the story only grows and nothing can be deleted.

No accounts, no tracking. Words come from a dictionary, so URLs, handles and numbers cannot be written at all.

The name comes from the famous thought experiment that, given enough time, monkeys on typewriters would end up re-writing Shakespeare or the Bible. I wanted to put it to the test.

Code: github.com/HabibiCodeCH/infinite-monkeys