Wait, it can do that?

Asked: “Redesign our pricing page. Build five different versions and show me a screenshot of each so I can pick one.”

You get back: 5 screenshots, then 1 PR for your pick.

Asked: “People miss it when a background session finishes. Design this from first principles, create some designs, pick the best one, then repeat trying to make it simpler and cleaner, then share.”

You get back: 10 concepts in the thread, a simpler round after your feedback, then 1 PR.

Asked: “Get every dashboard frame under the 8.33 ms budget for 120 Hz. Measure first, fix what’s slow, and prove each fix with before and after numbers.”

You get back: A way to measure frame times, one sub-session per slow surface, and before and after numbers for each fix.

Asked: “This animation feels choppy.” Later: “Video proof before and after.”

You get back: 1 PR, plus a Proof recording of the same interaction on main and on the PR.

Asked: “Links in our emails open the homepage instead of the page they point to.”

You get back: The root cause, a fix confirmed in production, and a check that catches it next time.

Asked: “Connect our ClickHouse so you can query it.” Then: “Which API endpoints got slower this week?”

You get back: A connected ClickHouse server and the endpoints whose p95 latency rose since last week.

Asked: “Checkout got noticeably slower last week. Can you figure out why and show me?”

You get back: The change that caused it, plus a canvas with the daily trend, what the page waits on, and fixes ranked by savings.

Asked: “USAGE_METRICS_TABLE can only flip once the new table has 30 days of rows. Can you sleep until then?”

You get back: A run scheduled for when the data is ready, then a PR marked ready for review once Proof and CI pass.