Ten minutes of video, and the best part is the failure.
He asks for a UI polish pass. He gets back a colour tweak and some animation changes. In his own words: "the polish wasn't really what I expected… what you get might not be what you like." Most walkthroughs cut that bit. This one keeps it, and then shows the second attempt.
The second attempt worked. Nothing was upgraded between them.
What changed on the second pass
Four things, and they are all narrowing.
He named three specific pages instead of "the site". He fixed the colour palette in advance and refused to reopen it. He switched to planning mode and demanded tell me exactly what we're going to do before we do it. And he stated the standard out loud: make it look like a serious, expensive edit, not something cheap.
That last one sounds like fluff and is not. "Polish" is not a target — the model has no idea what score it is being marked against. Naming the standard gives it one. It costs a sentence.
Result: one background shade, nudged. Nothing else moved.
- Palette swapped to the real tokens
- Spacing rhythm corrected on all three pages
- Plan reviewed before a line of CSS changed
"Make sure it looks like a $10 million plus edit" set a bar "polish" never did. Naming the pages and demanding a plan first is what actually moved the outcome.
Take the blindfolds off
The line worth keeping from the whole video is about letting the assistant actually see the reference sites rather than describing them:
"It could be like DaVinci for you, but if you put a blindfold on it, what good is DaVinci?"
This is the fourth independent arrival at the same idea in one batch of reading — render it and look at it, rather than reasoning about the source. We learned it the expensive way on our own site, twice, and it is now a standing rule here.
His method for the research phase is worth stealing whole: ask for around ten reference sites in the target industry, pick four or five, let the assistant look at them, then ask for three options rather than an answer. He got three named palette directions and chose one for a stated reason, rather than accepting the first thing produced.
Two things to know before you copy it
It was uploaded in January 2026, and it shows in one specific way: the install line for one of the tools points at a repository that has since moved. The redirect still works, the abandoned original still carries tens of thousands of stars, and someone following the walkthrough literally would install from a dead source. The same author has published two newer answers since.
Take the process from here, take the tooling from somewhere current. That is not a criticism of the video; it is what any technical walkthrough becomes with a few months on it.
The second thing is ours. His method depends on a browser extension that can see whatever page you are looking at. That is fine pointed at public reference sites. It is not fine on a machine where client material and credentials are reachable in the same browser session. If we ever use it, it is a clean profile pointed at public pages only — never at anything behind a login.
The half he skips
He clears context between phases, which is correct and which we also do. What he never mentions is the other half: write everything down before you clear. A cleared session that recorded nothing is indistinguishable from a session that died. We have paid for that distinction more than once.
What to do
Assume the first pass is a draft, and budget for the second. On that second pass name three pages rather than the site, fix what must not change, ask for the plan before the code, and say out loud what standard you are marking it against.