King Aguirre

Render settings

Look
Motion

E00 VibeBox · Engineering deep dive

What is verified, and what is not.

Everything here is read from the repository, stated on the public site, or clearly marked as an illustration. Three passes, three levels of proof.

Verified in the repository

  • pnpm and Turborepo monorepo: 4 apps, 9 packages
  • Next.js with Emotion in the site and admin; Tailwind CSS in the Motion app
  • Supabase client and server split with safe auth helpers and Google sign-in
  • A task prompt guard in the database package
  • Preview guards and sanitizing in the launchpad package
  • 231 unit test files and 8 end-to-end specs

Stated on the public site

  • A developer-led studio for business websites
  • A launch board of 18 builds
  • A brief wizard (Launchpad), whose availability the public pages disagree on

Illustrative on this page

  • The isometric blocks and the cylinder are diagrams of the structure above, not internal production diagrams
  • No traffic, revenue or uptime figures: none are published

E01 System boundaries

Four apps, nine packages.

The public site, the Admin Studio, the Motion showcase and a Mac helper, over shared packages for UI, motion, data, auth, the brief wizard, the dashboard, scaffolding and the agent runner.

Apps

Packages

Read from the repository tree, 2026-10-16.

E02 Automation with a gate

The runner waits for a person.

The Admin Studio's Agent Console pairs with a local runner on a Mac. Browsers and the host never run local shell commands, and risky stories stop at an approval.
  1. 01

    Goal in the Admin Studio

    A person writes the goal.

  2. 02

    Pair a local runner

    Short-lived pairing tokens, hidden after pairing.

  3. 03

    Scan and stories

    The runner scans the repo; stories are generated.

  4. 04

    Risky story?

    Waits for an explicit approval. Local Codex is not auto-run.

  5. 05

    Typecheck, test, build

    Every checkpoint lists the commands it ran.

From the Agent Console checkpoint in the VibeBox repository. The gate is the point: nothing risky runs on its own.

E03 Quality gates

231 test files, counted.

Vitest unit tests across the packages and 8 Playwright end-to-end specs, counted in the repository on 2026-10-16. Checkpoints record the exact typecheck, test and build commands they ran, including a build that needed a rerun.
Talk through the architecture