Example sponsored bundle — how a paid placement looks.
Free & open · no signup · read-only — every stage ends by asking · nothing leaves your machine
A worked example of a sponsored playbook: a curated performance sequence a sponsor's brand wraps — logo, name, and voice around shared content, with the placement paid. Swap in a real sponsor to ship one.
The conductor fetches each brief in turn and writes its report before moving on — later briefs can build on earlier findings. Or copy any single stage to run it alone.
3 reports in reports/, plus the run's own INDEX.md: PERF.md, LATENCY.md, BUNDLE.md. Feed them to the optional Studio to turn findings into commits, or run 28 · Roadmap Synthesis to merge them into one plan.
Copy the conductor into your agent inside the repo you want checked. It runs each Goal Prompt in sequence, honoring each one's ask-first rule.
This slot shows how a sponsored bundle appears — a sponsor's logo, name, and blurb wrap a curated sequence, and the placement is paid. Swap in a real sponsor to ship one.
Sponsor a bundleFormats & specs: /partners · Want this set up for your org, with your own briefs? Goal Prompts for Teams →
The broad latency pass — wasted renders, main-thread stalls, startup waterfalls — ranked by what the user actually feels on common paths.
Where the seconds go. Decomposes p50 and p95 of the runs users feel into stages — queue, retrieval, first token, tools — and names the stage worth attacking.
What the browser actually downloads — oversized bundles, unsplit code, heavy dependencies, and unoptimized assets that slow first paint.