Back to Blog

This Week We Built Some Shit. Here's What and Why.

Raw update on what we actually shipped this week - rules system, billing, API docs, and infrastructure. No bullshit.

Drew Ewing
4 min read

Look, I'm not going to lie to you. This whole thing started because I got tired of telling Claude the same things over and over again. "Don't use on:click, use onclick. Stop making those stupid Svelte 5 mistakes. Here's how billing actually works."

So we built a rules system. Not because we're geniuses, but because I'm lazy and repetition is the enemy.

What We Actually Did This Week

Monday-Tuesday: Fixed AI's Svelte 5 Stupidity

  • Added rules R-SK-008, R-SK-009, R-SK-010
  • Basically teaching Claude "hey, don't write Svelte 4 code when we're using Svelte 5"
  • Automated the nagging so I don't have to do it
  • bun vibes dev code rules check - because manual code review is for masochists

Wednesday-Thursday: Billing System (Because We Need Money)

  • Built credit-based billing. 1 credit = $0.001 USD. Simple math.
  • Stripe integration that doesn't break when webhooks get weird
  • Real-time quota checking so people can't blow up our costs
  • Zero bullshit - you run out of credits, you're done until you buy more

Friday: Made API Docs Not Suck

  • Swagger UI is 2MB of JavaScript hell
  • Built our own with Svelte components
  • Bundle size: way smaller. Performance: way better.
  • Can actually test requests without wanting to throw my laptop

Saturday: CLI That Actually Works

  • Multi-target CLI builds for different environments
  • Worker-specific builds because Docker is weird about musl vs glibc
  • Actually works in Kubernetes without dependency hell

Sunday: Chat Interface Redesign

  • Totally rebuilt the chat UI because the old one sucked
  • Added avatars and file uploads
  • Chat actually works on mobile now
  • Agent staging system so you can queue up agents before starting conversations

Also This Week: A Bunch of Other Shit

  • Friends System: First pass on adding friends because working alone sucks
  • Guided Flows: Janky but functional onboarding system
  • Invitations: Can actually invite people now (when it works)
  • Usage & Billing UIs: So people can see how much money they're spending
  • Kafka → Redpanda: Because Kafka is overkill and Redpanda just works
  • CodeMirror → Monaco: Better syntax highlighting, IntelliSense that doesn't suck
  • Gemini Provider: Added Google's Gemini as an official provider
  • Nano Banana: Because sometimes you need the smallest model that actually works
  • Image Generation Cleanup: Still WIP but way less janky than before
  • Infrastructure: GitOps with ArgoCD because manual deployments are chaos
  • Artifact builds: Docker registry limits are real, artifacts are faster
  • Automated maintenance: Downtime at 3am sucks

Why Any of This Matters

Here's the thing - we're trying to build tools that let one person (me) do what used to take a whole team. Maybe it works, maybe it doesn't. But the idea is simple:

AI + Good Rules + Decent Infrastructure = One Person Can Ship Real Software

The rules system keeps AI from writing garbage code. The billing system means we can actually charge for this stuff. The infrastructure means it doesn't fall over when someone actually uses it.

What We Don't Know Yet

  • Will anyone pay for this? No idea.
  • Are we solving a real problem? We think so, but who knows.
  • Can this actually scale? We're about to find out.
  • Is the code any good? Ask us in 6 months when it's either working or on fire.

The Real Test

We're launching this thing. Not because it's perfect, but because sitting on it forever helps nobody. Either people want tools to build stuff faster with AI, or they don't.

If you're reading this and thinking "yeah, I want to build stuff without dealing with all the usual bullshit" - great, that's the point. If you're thinking "this sounds half-baked" - you're probably right, but half-baked and shipping beats perfect and never launching.

We built a bunch of stuff this week. Now we find out if anyone cares.

Try it: vibes.dev | Questions: drew@vibes.dev | Phoenix, AZ 🇺🇸

All Posts