How we derived itMeasured, not eyeballed.
A style guide written by looking at screenshots is a guess. These values came out of the browser itself, which is why they include things nobody would invent, like a 10.5px root unit.
01Ran it through /taste. A Claude Code skill built for this: it drives a real browser to the target, screenshots it, and walks the rendered DOM. behelfy.com was loaded at 1440×900 in a clean profile, so no cookie or login state could change what rendered.
02Sampled every rendered element. Computed styles from the whole page rather than the stylesheet: colours ranked by the share of visible surface they actually cover, type by frequency of use, spacing by what repeats. It also picks up the things nobody writes down — letter-spacing per role, line-height ratios, the exact geometry and tint of a drop shadow, whether :focus-visible and prefers-reduced-motion are authored.
03Treated the screenshot as ground truth. Where CSS and the eye disagreed, the eye won. A colour present in the DOM but covering under 5% of the page is decorative, not a brand colour. Imperceptible shadows are artefacts, not decisions.
04Cross-checked three pages. Home, a product listing and the blog. A value appearing on two or more pages is a system rule; one page only makes it local. That distinction is what stops a one-off being enshrined as a standard.
05Separated the platform from the brand. It read the site's own CSS custom properties, which is how we know these are Shopify pages on a Dawn-derived theme: --font-body-scale of 1.05, --page-width of 120rem, --spacing-sections-desktop of 36px. That is why the numbers carry odd fractions, and why some of them are theme settings rather than design decisions.
06Wrote down the trade-offs, not just the values. Tokens tell you spacing is 10.5px. They do not tell you why the accent never appears on a heading. The rules below are the part that lets someone design a new page that still belongs.