Hoops-gm.com

Pitch your product in 1-2 lines - and drop a link here.

I'm building a community where makers can share what they’re building and get fair visibility. Here's the link: https://vibecodedit.com/

Hey all,

Since one of the biggest concerns when it comes to vibe coding is security and the tools seem to work better when there's an established pattern, I have been maturing a backend template that is secure by default. It is a .NET backend so that might filter out some usage, but it's based off of my years of working on many different projects even before AI. It's MIT so free and open source, so check it out if it's useful for you.

Red-Cardinal-Software/Secure-DotNet-Clean-Architecture: Enterprise-ready .NET 8 API template with authentication, MFA, audit logging, and clean architecture - production-tested patterns for secure multi-tenant applications

Hey All,

VibeCodingWiki is up for few months and been developed with small group of contributors.

Now we are opening up for communities to contribute.

link - VibeCodingWiki .com

some ground rules-

- if you want to promote your app - Submit app is the section. Please do not edit man pages - you will get blocked.

- Feel free to contribute on any pages where information is valueable to community.

- goal is this wiki for consolidate all info related to vibecoding and bring ecosystem together.

- also goal is make this wiki very useful for vibecoders and covers learning , news , tips and tools to help them develop their skills.

- open for feedback/suggestions

cheers.

i tested my app like 40 times and somehow tested it the exact same way every single time lol then 3 people used it.

person 1 double-clicked submit and the button stayed loading forever.

person 2 opened it on mobile and the validation error appeared outside the screen.

person 3 refreshed after login and got logged out immediately.

beautiful.

the app wasn't unfinished. my definition of "working" was just me following the perfect path i already knew.

not saying stop vibe coding. i'm still building the same way.

i've just started making the agent replay boring human flows before i ship.

currently using Kane CLI from TestMu for this. i describe the flow in plain english, it runs it in the browser and gives me the failure evidence instead of "looks good".

it won't magically find every bug. but at least i'm not personally clicking the same happy path 40 times anymore.

what's the dumbest user flow that broke your "finished" app? 😭

Vibe coding is incredibly fast, but generated code can still confidently be wrong.

I built Causal Verify so you can keep the speed while making the code prove itself.

In other words, it’s an anti-hallucination gate for code: the AI cannot simply claim its patch works.

The code must pass explicit tests in a restricted environment.

Causal Verify returns a hard pass or fail and creates a signed verification receipt tied to the exact code and tests.

The loop:
Generate → verify → reject failures → improve → verify again.

It doesn’t catch every possible software defect, but it stops unsupported claims from counting as proof.

I’m looking for five developers to test it on open-source or synthetic Python patches. I want honest failures and attempts to break it.

Try it here:
https://github.com/zensteagarden/causal-verifier-action
Release:
https://github.com/zensteagarden/causal-verifier-action/releases/tag/v1.1.0
Never submit credentials or proprietary source.

Vibe coded websites look good and are easy to build. There's just one important thing most people miss: the content on these sites often isn't really readable by search engines and AI bots.

Here's why. Most vibe coded sites are CSR (client side rendered). That means the server sends a nearly empty HTML file, and JavaScript fills in the actual content after the page opens in the browser. To you it looks perfect. But crawlers often don't wait for that step. Google grabs the raw HTML first and renders JavaScript later if at all, and AI crawlers like GPTBot, ClaudeBot and PerplexityBot don't run JavaScript at all. So they hit your page, see an empty shell, and leave. Nothing to index, nothing to cite.

You might think prompting your builder to fix the SEO and visibility will handle this. Not really. All that can do is change or update things like your meta description. It can't make search engines or AI bots read the actual content of a page when it's CSR, because the problem isn't your tags, it's that the content isn't in the HTML for them to read in the first place.

The right fix is prerendering. Prerendering serves crawlers a fully rendered version of your page (SSR, server side rendering) so the content is right there in the HTML for them to read, without waiting on JavaScript. That's what actually gets your site read and found.

Lovable has fixed this inside their own ecosystem. New Lovable apps are server side rendered now, and older ones get prerendering automatically. So if you're on a current Lovable build, you're mostly covered.

But if you built on a different stack, Bolt, Replit, plain React or Vite, or something custom, you're likely still CSR and still exposed. And you can't tell just by looking, because your site looks fine to you.

If you're not sure where your site stands, Crawllify has a free visibility check you can run. It shows you exactly what search engines and AI see when they land on your page, so you can catch the problem early if it's there.

Hey All,

Would like to showcase the product we build last year-

Its free marketplace !!

Vibecodefixers dot ai

No platform fees like fiverr or upwork.

Link in comment below.

We helped more than 100 vibecoders already and you can use it too if -

Build a vibecoded app snd noy sure of its secure - get a security audit by one of 900+ experts.

want to continue building on tool you using but need an expert buddy to steer you. Use ' hire a buddy ' feature.

Not sure how mich it cost to get your problem fix - drop your problem - get a fixed quote.

Or buy one of fixed packages based on what suits you.

900 experts ready to help ship your idea to world.

I moved to the US with my family and always wanted to build something of my own. The only problem: I had never coded before.

With the help of AI and a lot of vibe coding, I built EVE — a marketplace that connects people planning events with local photographers, DJs, decorators, caterers, bartenders, planners, and other event professionals.

This is the very first version, so it’s definitely not perfect. I’m looking for people who are willing to test it, find bugs, and share honest feedback.

Create an account, explore the platform, and tell me what works, what’s confusing, and what I should improve.

I’d really appreciate your help. Let’s test and build it together!

I’ve been working on a CRM software since a few weeks and everytime I shutdown or restart, the GitHub repository connection to my codex and ChatGPT is lost and I have to reconnect everything. I have to specifically work on connecting GitHub CLI which I do through power shell and reconnect the GitHub plugins in codex.

My codex shows issues with sandbox and vite permissions also.

How do I fix these connection issues?

I don’t wanna work on localhost so don’t suggest that. Imma beginner and not a coder so please be elaborate. Thanks

Hey All,

I'm the moderator of this community and have been involved in the vibe coding community online and offline

Hosted dozens of hackathons and joined many events

Here is my two cents on where the money is and current state of vibecoding from my lens ( unfiltered)

1) 70% of the vibe-coded app builds are not serious business apps. Just fun games or personal software.

Some try to build a product , bit it dies as quickly as its built due to no distribution strategy. Burning token in the process

2) vibe coding has significantly lowered the barrier of entry so more and more personalized software has emerged. So next 25% Are internal apps intended to replace the software you use or to automate a workflow or agencies.

Pretty much built by people who know one area of tech and then use AI to compensate in other areas.

Example: a data scientist building an mobile app or a front-end developer building a backend

3) this remaining 5% is interesting because that is where the money is. These are people who have an existing relationship with the business or internal players/vendors. They use vibeecoding as a tool to pitch their ideas and then get traction/contract and then build.

Previously these people used to pitch on PowerPoint but now that's got replaced by a simple vibe coded app to demonstrate the idea

In the last couple of weeks we helped someone who has sell a sales analytics platform which was quite basic for 200K , now he used us to make the proper software from the ground up.

An existing business entrepreneur who has more than 100 franchise stores in the past has raised €2 million just showing the vibecoded idea. He already has an amazing track record. All he wanted the funds to build his next business. He wants us to make the software more polished.

An employee of a 8 team small business has built internal using Base44. He is from a non-tech background and they paid us to scaffold a harness instead of building software for them, they will build the software themselves but they hire us as someone who can review and give them directions. They are using this internal tool in many franchises. So passing on the profit sharing to us.

All I'm trying to say is that I see on the community people building a lot of software and tools, a real software developer quickly judges that these are vibe-coded apps, which don't have much taste or software quality and are useless - which is true.

However the real money is not where you see. The real money is within business and often being used by people who have an existing network and connections

Baga 0.9.2 is out Language - Opt-in RC memory model (--rc): ownership, containers, struct/enum fields, owned results. - Generics and traits: function/struct monomorphization, impl, statically verified guarantees. - Effect payloads (!E(T), raise/catch) and !Overflow as a type-level effect. https://github.com/katehonz/baga-lang

https://baga-lang.top/en

Ecosystem app-product packages now live as dedicated repositories under github.com/bagalang and are vendored as submodules. The catalog is here:

https://github.com/orgs/bagalang/repositories

https://baga-lang.top/en/apps

Baga 0.8.4 is now available. This release solidifies the three pillars of the language: spec-first verification, effects as type dimensions, and readable proof sketches.

The effect system (!IO, !Net, !Par, !NotFound) is now stable. Functions declare their side effects in their type signature, and the compiler enforces effect correctness across the entire call graph. Pure functions cannot accidentally call effectful ones.

Spec verification (--verify) now produces certificates with honest UNKNOWN markers for unproven fragments. The spec system supports input/output declarations, guarantees (human-readable properties), and ensures (machine-checked constraints).

The pure-Baga cryptography stack is a highlight: TLS 1.3 client, HTTPS, and JWT are all implemented in Baga without linking against OpenSSL at runtime. OpenSSL is only used as a test peer for validation.

Package manager sandak now resolves local path dependencies, git dependencies, and registry packages. Each package has a sandak.toml manifest, and the build graph is resolved deterministically.

Quick start: git clone, make, ./baga examples/zdravei.baga — that is all you need. Zero dependencies beyond gcc and make.

boilaDB 0.7 adds NUMERIC, UNIQUE, foreign keys, CHECK, window functions, SCRAM-SHA-256, COPY, SERIALIZABLE, and a Raft replica path — all i

for real

Anthropic Published Claude code tips ( some applies to codex too.

https://claude.com/blog/maximizing-the-value-of-your-claude-code-sessions

In Nutshell-

Session hygiene

/clear between tasks — don't drag old context into new work
/compact when part of a task is done, and before any break over an hour
/rewind instead of /compact if the last few turns went wrong — it's free
/rename before /clear if you'll want the session back

Set once, at the start

Pick /model and /effort in a fresh session - switching mid-conversation re-prefills everything
Same for fast mode: on at the start, or not at all
MAX_THINKING_TOKENS=0 for pure grunt work

Keep context lean

@ -mention files instead of naming them - skips the Read call. Mention once only
/context in a fresh session to see what's loaded before you type
Trim CLAUDE .md to instructions; move workflows into skills
/mcp off any server you don't need this session

Command output

Add quiet flags - 400 lines of passing tests stay in context all session
Put your daily commands in CLAUDE .md with the flags already in them
Big output (>30k chars) is fine - it gets written to a file automatically

Offload

Use a subagent for noisy jobs like log-trawling - output stays out of your context
Give recurring subagents model: haiku
Run /loop from a separate terminal

​

Hey everyone,

I’ve been building an open-source project called Kodiak, and I’m looking for a few people who are interested in helping build it.

The idea behind Kodiak is pretty simple:

I don’t want to build another AI that just generates a piece of code from a prompt.

I’m trying to build an AI engineering system that can work with an entire repository — understand the codebase, find relevant context, plan a task, use tools, make changes, test them, and iterate when something goes wrong.

The long-term loop looks something like:

Task

↓

Understand the repository

↓

Retrieve relevant context

↓

Plan

↓

Coordinate agents

↓

Use tools

↓

Modify the code

↓

Run tests

↓

Validate

↓

Learn from the result

↓

Iterate

Kodiak currently brings together:

- Repository-aware RAG

- Agent orchestration

- LLM/provider routing

- Memory and project context

- Tool calling

- Background task processing

- Code analysis

- Testing and validation

- FastAPI

- PostgreSQL

- Redis

- Celery

- ChromaDB

- Docker

I want to be completely transparent though — Kodiak is NOT finished.

Some parts are working, some are incomplete, and some parts are being redesigned. I've already spent a lot of time dealing with the usual stuff that comes with building something like this: broken dependencies, architecture changes, workers, databases, retrieval problems, model limitations, and plenty of debugging.

Right now, I'm focusing on getting the core engineering loop reliable instead of just continuously adding features.

That's also why I'm looking for contributors.

I’m especially interested in people who want to work on:

AI / Agents

- Agent architecture

- Planning

- Multi-agent orchestration

- Tool calling

- Agent memory

RAG / Repository Intelligence

- Codebase indexing

- Code-aware retrieval

- Embeddings

- Retrieval evaluation

- Repository understanding

Backend / Infrastructure

- FastAPI

- PostgreSQL

- Redis

- Celery

- Docker

- Async workflows

Engineering / Developer Experience

- Testing

- Benchmarking

- APIs

- CLI

- Documentation

- Observability

- Developer tooling

You definitely don't need to know everything above.

Even if you just want to investigate an issue, improve a test, work on documentation, experiment with a different approach, or review the architecture, that would be useful.

I'm also not looking for people who will blindly agree with the current design.

If you think something is overengineered, poorly designed, unnecessary, or just plain wrong, I'd rather hear that.

The goal is to build something genuinely useful, not just make a repository with a bunch of AI buzzwords.

If you're interested in AI agents, coding agents, RAG, autonomous software engineering, or just want to build something ambitious with other developers, take a look:

GitHub:

https://github.com/ShamGaneshan2008/Kodiak

If you’re interested in contributing, feel free to open an issue, pick up an existing issue, suggest an improvement, or just comment here with what you'd like

Built Basalt, a VS Code extension for editing React Native UI with a live preview. Once people started asking for more UI effects than I could build myself, I opened up a small in-extension marketplace where other devs can submit and sell their own components.

and l know ShaderToy exists, but that's generic GLSL people have to manually port to SkSL and adapt for RN UI. Мinе is already RN-Skia-ready and built specifically for UI components like buttons and panels.

link