← NEXUS case study
Download 1-pager PDF

DEVNOTES · GROK BUILD BETA

3 Months Work in 3 Days

A redacted case study for anyone building with an agent in one repo — brand system, multi-surface deploy, decks, editorial, and video — steered by taste, not tickets.

Redacted edition · names & URLs obscured

01

Session at a glance

Label: Public metrics · June 2026 · Grok Composer 2.5

Working sessions
2 linked arcs
Conversation depth
~293 events
Agent actions
~145 total
Your prompts
6 steering turns
Surfaces shipped
3 sites + 4 decks
Agency equivalent
8–12 wks → ~3 days
02

How the agent worked

ActivityCountMeaning
Reviewed files51Pages, CSS, skills, session history
Searched content33Copy, classes, config across repo
Ran builds23Deploy, ffmpeg, pip, preview servers
Applied edits13HTML, CSS, generators
Generated visuals8Runway keyframes + editorial frames
Created files4Video pipeline, PDF builders
03

What steering sounds like

"I don't want to answer any of that — just want the containers to not be overdone on mobile, chill out."Builder
"Generate a video — glitch models on a runway, landscape for hero, vertical for social."Builder
"image_to_video wasn't available — shipped motion video from keyframes instead."Agent
04

Build something similar

A repeatable pattern — not a product pitch.

  1. One repo, one deploy. Static HTML + CSS + a few Python generators. Agent edits in place; you review live URLs.
  2. Design system first. Tokens + components before pages. Agent reads a skill / style guide before visual work.
  3. Subdomain routing. One Vercel project, middleware rewrites per host — hub, portfolio, recruitment, devnotes.
  4. Codegen for repetition. Python overwrites deck HTML/PDF from one content source so copy stays aligned.
  5. Steer by slot. "Hero / break / contact" beats regenerating whole pages. Keep prev assets.
  6. Scoped calm-downs. One file, one breakpoint when mobile feels loud — not a 40-item audit.
  7. Honest tool limits. Missing ffmpeg or image_to_video? Adapt — keyframes + assembly still ships.
  8. Export the arc. Case study + redacted devnotes for the next person (this page).
05

Snippets

middleware · subdomain rewrite
import { rewrite } from "@vercel/functions";

const HOSTS = new Set(["devnotes.example.com"]);

export default function middleware(request) {
  const host = request.headers.get("host")?.split(":")[0];
  const { pathname } = new URL(request.url);
  if (HOSTS.has(host) && (pathname === "/" || pathname === "")) {
    return rewrite(new URL("/devnotes/grok-build-case-study", request.url));
  }
}
deploy
cd your-brand-repo && npx vercel --prod --yes .
agent skill · brand guardrail
---
name: your-brand
description: Use when editing anything in your-brand-repo.
---

Before visual or copy changes, read references/STYLE-GUIDE.md.
Logo: PNG lockups only. Deploy after HTML/CSS changes.
scoped mobile fix
@media (max-width: 899px) {
  .your-page .nx-panel {
    border-color: var(--nx-border);
    background: transparent;
  }
}
06

Grok learnings

07

Export

This page is the redacted source. Download the matching one-pager for email or print.

Download 1-pager PDF (redacted)

Hosted at