Platform
Platform

GitHub Enterprise Platform & vibe CLI

Role
Senior Design Technologist — led platform migration, authored governance proposal, built the CLI toolkit end-to-end
User Problem
UX Designers and Product Managers were locked out of prototyping workflows by Git-on-Borg's tooling complexity.
Business Problem
No shared infrastructure for 200+ engineers to scaffold, deploy, and collaborate on AI prototypes at scale.
Impact
200+ users, 1000+ commits, 300+ PRs. Agent Builder team deploying 5-10x daily. Multiple Google orgs forked it.

Why I did this

Git-on-Borg worked fine for production engineers but was a poor fit for UX Designers and Product Managers. No GitHub Actions, no Copilot, no modern CI/CD, no way to share component libraries across teams. They were effectively locked out of contributing to prototypes by the tooling complexity.

I wrote the formal proposal to Google’s “Future of Git” initiative — made the case for GitHub Enterprise adoption, addressed security and compliance concerns, proposed a governance model. Led the meeting with Dan (FoG team lead) and platform leadership. Secured approval for the pilot. Authored the Technical Migration Guide that unified engineering standards for the org: branching strategy, OWNERS files, permission structure, repo naming conventions.

The Agent Builder team (Soenke/Sasha) was the first on the platform. They’re now deploying 5-10x daily. The cloud-ai-ux organization scaled to 200+ users, 1000+ commits, 300+ PRs. Multiple Google orgs forked the structure. Director quote: “Leading here at Google.”

But the migration alone wasn’t enough — teams needed tooling to actually use the platform. That’s where the CLI came in.

What I built

vibe CLI (TypeScript, Commander.js, 189 commits):

  • vibe onboard — 6-step interactive wizard: Depot auth, Git identity, adaptive tier selection (Novice/Medium/Expert), SSH key generation + registration, feature selection, project scaffolding with Jetski IDE launch.
  • vibe scaffold [name] — copies the blueprint template, purges symlinks, injects environment config, initializes git.
  • vibe doctor — diagnostic checks: Gcert status, tool availability (gh, ggh, jetski, gcloud, node), dependency health, library integrity.

The full setup — from bare macOS to authenticated, scaffolded, IDE-launched project — is a single copy-paste command. New engineer onboarding went from days of manual configuration to a 10-minute guided wizard.

Services layer:

  • SkillService — feature registry with 11 features gated by adaptive tier. Novice gets scaffolding + visual sync + Zipline sharing. Medium adds comments, annotation, Cloud Run deploy. Expert adds PR review, sandbox reaper, copy auditor, VHS recording.
  • ProjectService — template scaffolding from the blueprint/ directory. Recursive symlink purging, .env injection, git init.
  • DoctorService — system health diagnostics across the full toolchain.

Physical copy architecture. Every scaffolded project gets its own copy of skills, workflows, and components — not symlinks, not a monorepo dependency. Each project is fully self-contained and portable. This was a deliberate choice after symlinks broke Jetski’s file watcher.

vibe CLI — automated onboarding wizard

Adaptive skill registry

The tier system gates complexity, not capability. A designer who’s never used a terminal gets a different experience than an engineer who wants raw CLI power.

TierFeatureSkillWhat it does
NoviceScaffoldinggm3-vibeMaterial 3 components and Vite HMR environment
NoviceVisual Syncvibe-applySync browser CSS/layout tweaks back to source files
NoviceSharingdeploy-ziplineOne-click public URL generation via Zipline
MediumFeedbackcommentsFirebase-backed commenting directly in the prototype
MediumAnnotationvisual-drawingDrawing overlay for visual walkthroughs
MediumDeploymentvibe-deployCloud Run service + Cloud Build trigger creation
ExpertPR Reviewpr-reviewerVisual diff video recording for Pull Requests
ExpertCleanupvibe-reaperDemocratic cleanup of stale sandbox branches
ExpertIdentitydepot-authSSH/Git machine registration
ExpertCopy Auditui-copy-auditor-vibeLLM-based audit against Cloud AI branding guidelines
ExpertRecordingvhsTerminal recording for technical walkthroughs

Automated deployment via Zipline + Jetski

13 IDE slash commands

Every blueprinted project ships with an .agent/ directory that Jetski auto-discovers. Designers get slash commands in the IDE chat panel without knowing they’re using an agentic system: /scaffold, /vibe-apply, /deploy, /deploy-zipline, /review-pr, /draw, /comments, /setup-ci, /setup-reaper, /setup-git, /audit-copy, /vhs.

What it enabled

  • First time UXE teams could share private component libraries across GCP product teams
  • Enabled AI-assisted coding tools (Gemini Code Reviewer) that weren’t available on Git-on-Borg
  • CoreUX, Corp Eng, and Google Material all adopted the blueprint for their own teams
  • The Gemini Enterprise Agent Builder runs on this infrastructure

Artifact Evidence

Project: cloud-ux-ai-blueprint

Access Restricted

Access Required

Enter the access key to view projects

Hint: See intro email for access key.