From ea35fdfd260b1cab3697fb779f510500a84ae4b2 Mon Sep 17 00:00:00 2001 From: Maximilian Kaske Date: Tue, 13 Oct 2026 21:50:33 +0200 Subject: [PATCH] content(web): plainer screenshot loop and design system paragraphs in the timeline post --- .../pages/blog/four-iterations-of-an-incident-timeline.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx b/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx index 57374b936..9ad14be9f 100644 --- a/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx +++ b/apps/web/src/content/pages/blog/four-iterations-of-an-incident-timeline.mdx @@ -40,9 +40,9 @@ For deterministic tasks and fixes I use Claude Code remote. It spins up a VM and I am **obsessed** with proper `PLAN.md` files to `/loop` over once I'm afk. I keep plenty of Claude Code tabs open, grilling me on different ideas with Matt Pocock's goated grill-me skill. I rarely read those plans extensively, except when it's a collaboration with Thibault on a bigger-picture feature like incident response. We worked on that plan for a couple of days, with the idea spelled out for weeks before. Leave it, iterate the next day. -Claude Code has **eyes on the dashboard**. It drives a browser against the local dev server, logs in, and takes a screenshot after every change. My feedback is the same format in reverse: a screenshot with the offending part **boxed in red** and one sentence. While a loop runs I go bouldering or for a walk. When I'm back I test on my machine, not on a preview link. This is detail work, and localhost is where I can poke at it. +For dashboard work, Claude Code runs Playwright against my local dev server and screenshots the page after every change. That's how it checks its own work. I do the same from my side: a screenshot, the broken part **boxed in red**, one sentence. While a loop runs I go bouldering or for a walk. When I'm back I test on localhost, not on a preview link. The details only show up when you click through the real thing. -When it comes to UI/UX, I use Claude Design for a first feeling. Without steering it looks very *claudy*, gradients and italics, so most of the time it's purely for inspiration. I usually ask for three or four variations. For dashboard work we have our design system attached, so it can't go off the rails too much. But it stays rather plain if I don't give enough details. +When it comes to UI/UX, I use Claude Design for a first feeling. Without steering it looks very *claudy*, gradients and italics, so most of the time it's purely for inspiration. I usually ask for three or four variations. For dashboard work we have our design system attached to both. Claude Design gets it as a project asset, so the mocks come out in our tokens, fonts and spacing instead of the default look. Claude Code gets it from the repo: shadcn primitives in `@openstatus/ui`, our own blocks on top, and `AGENTS.md` files that say to compose from those and never fork a primitive into an app. Neither can go off the rails too much. But both stay rather plain if I don't give enough details. ## Phase 1: from the plan -- 2.51.2