Skip to main content

Vibe Code Cleanup Crew

warning

Work in progress - coming soon. Interested in being one of the first? Write to sandor@aerelontech.hu and describe your app.

You prompted your way to something that works. Users are on it. Money may even be coming in. And now every new feature breaks two old ones, nobody can say what the system actually does, and the model that wrote it has long since lost the thread.

That is not a failure. That is the moment the prototype has proven the idea and needs to become a product.

What this engagement is​

We come in, read what you have, and give it a spine: a Tech North Star — the one document that says what this system is, how it is put together, and which decisions are already settled so they stop being re-litigated every sprint.

Either we fit one of the off-the-shelf packages onto your app, or we write a custom one for your domain when nothing off the shelf is close enough.

What you get out of it​

  • A named architecture. C4 context and container diagrams of what you actually have, not what the prompt intended.
  • Decisions written down. Architecture Decision Records for the choices your codebase already made by accident — session handling, data store, payment coupling, secrets — with the alternatives marked where you still have a real choice.
  • A cleanup backlog, ordered by risk. What will hurt you first, what can wait, and what is fine to leave exactly as it is. Most vibe-coded apps need far less rewriting than their owners fear.
  • Guardrails your AI tooling can read. The same package doubles as context for your LLM of choice, so the next hundred prompts build on the architecture instead of drifting away from it.
  • A growth path. Where the seams are when traffic arrives, so scaling is a planned move rather than a rewrite.

What this is not​

We do not take your repository away and hand it back three months later. The point is that your team — or you and your model — keep building, only now with a target to build toward.

Who this is for​

  • Solo founders and small teams with a live, AI-assisted product and no architect.
  • Agencies that shipped a prototype fast and now have to support it.
  • Companies whose internal tool escaped its team and became load-bearing.

How it runs​

  1. Intake — you send the repository and a short description of what it does and who uses it.
  2. Read-out — we work through the code and the running system, and reverse engineer the architecture that is really there.
  3. North Star fit — off-the-shelf package matched, or a custom one drafted.
  4. Hand-over — the package, the backlog and at least two sessions where your team can ask anything about either.

Want to start earlier?​

You do not have to wait for us. Take an off-the-shelf Tech North Star today and point your LLM at it — that alone gets most vibe-coded apps a long way.