Skip to content
ThorbisInterface Guidelines (opens in a new tab)

Sources

One focused chapter from the Thorbis interface research. 32 rules. Read the research index for every chapter and focused study.

Sources

I built this for the dispatcher at 7 a.m., the tech in a crawlspace, and the owner closing the books. Quiet chrome. Precise work. I’m still learning. These are the notes.

Applied bookmark research

Reviewed 2026-09-06. These examples reinforce the existing owners; they do not introduce another visual style or claim the product behavior is implemented. Read the 26-source review and access limits.

Close the loop with evidence, not the word polished

Vague design requests produce repeated subjective revisions and hide which parts of the result were actually checked.

A review records the person and task, the observed defect, the owning rule, the smallest correction, and its verification. Preserve source access limits. Turn repeated feedback into a better existing default rather than another detached instruction file.

Thorbis example. Instead of make the button premium, record that its pending state moves the label, identify the UI owner, compare the corrected state under the same content, and attach the relevant checks and remaining uncertainty.

Verify. Separate a source that was read from a demo that was exercised. Separate a passing content test from a browser check, and a committed branch from a deployed release. Report failed and skipped checks explicitly.

Do not import. No fabricated research, inferred paid lesson content, unmeasured uplift claim, or declaring work live because a commit exists.

Open the tracking skill · Evidence: Agents with Taste; Train Your Judgement; Developing Taste; How we think about design; Design Engineer Principles

Loading search…

Loading search. You can close this message and keep reading.