|
agent-browser tool.brand.html)brand.html as the active tab — a
self-contained brand-kit page (template:
brand-extract/templates/brand-kit.html) that the daemon renders from
brand.json. The daemon pre-seeds it with a deterministic first paint — a
harvested logo, an approximate palette, font families, and a few cover images —
so it is NOT all-skeleton when it opens. Your job is to replace that seed with
measured truth and fill in the rest, progressively, so the user watches it
complete module by module. You never hand-edit it: you write brand.json, then
run od brand preview <brandId> and the daemon re-renders the page (the page
soft-reloads itself while extracting). Optimize for fast first paint and
progressive fill-in — write a partial brand.json and preview it the moment
you have a name, a couple of colors, and a logo, then preview again after each
field group rather than batching the whole kit to the end.The trap to avoid: an LLM left alone regresses to the mean — Inter, an indigo accent, a purple gradient. That is off-brand for everyone. Every value you emit must trace to something you measured on the page.
brand.json is how off-brand,
hallucinated kits happen.agent-browser against the selected browser tab (its URL/title are in
your run context — treat "this page" / "the site" as that tab):agent-browser get url / get title to confirm the target.agent-browser snapshot before extracting anything.background, surface, foreground, muted, border, accent,
accent-secondary. The most frequent near-white/cream is usually the
background; the most frequent chromatic mid-saturation color is usually the
accent.@font-face names and font-family declarations for
display, body, and (if present) mono. Note weights actually used.logos/: the inline header/nav <svg> (write the
literal <svg>…</svg> markup verbatim to logos/header.svg — do not just
reference it), any <img> logo, apple-touch-icon, favicon, and
og:image. Fetch the asset URLs directly — never leave logo.primary
empty when the site has any mark. Set logo.primary to the best vector /
transparent lockup (SVG wordmark > apple-touch-icon > favicon > og:image)
and list the rest in logo.alternates; the kit page renders them as
switchable thumbnails. (The daemon auto-fetches a favicon/og:image fallback
into logos/ so the page is never logo-less, but that safety net is no
substitute for saving the real wordmark.)imagery/: the og:image/twitter:image social card, the
hero/banner art, the largest <img> (resolve the highest-res srcset /
<picture> source), CSS background-image hero blocks, product or app
screenshots, and illustration/photography samples. Filter by rendered
size — keep only big images (roughly ≥320px on the long edge) and drop
icons, sprites, logos, avatars, and tracking pixels. List them in
brand.json as imagery.samples (see shape below); the kit page renders
them as a clean labeled Images gallery (a thumbnail grid). Pick 6–8 varied,
on-brand images — never UI chrome or icons. (The daemon runs a deterministic
cover/hero-image fallback at finalize so the gallery is rarely empty, but
that safety net is no substitute for picking the real hero images.)fonts/.<question-form> asking
the user to clear it by hand in the Browser tab:<question-form id="cf-verify" title="Verify in the browser">
[
{
"id": "ready",
"type": "radio",
"label": "The site is behind a verification wall. Please complete the check in the Browser tab on the right, then choose Continue.",
"options": ["Continue — I cleared the wall", "Skip — extract from public knowledge instead"]
}
]
</question-form>
agent-browser snapshot on the now-unblocked tab and resume measuring. Never
attempt to solve CAPTCHAs or bypass the wall yourself. If the user picks
"Skip", fall back to your knowledge of the brand's public identity and clearly
mark each such value (from brand knowledge) in its usage/notes.brand.json into the project as soon as you have the name, a couple of
colors, and a logo candidate — do not wait for everything. Then run:od brand preview <brandId>
brand.html so the user immediately sees a real, on-brand page
forming. Then preview after each field group, do not batch to the end —
after you measure and add each of (a) colors, (b) typography/fonts, (c) logo
candidates, (d) cover/hero imagery samples, (e) voice & tone, (f) imagery /
layout posture, update brand.json and re-run od brand preview. Partial data
renders the filled modules with skeletons for the rest, which is exactly the
progressive "filling in" experience the user should watch.brand.json — must parse as JSON, with this exact shape:{
"name": "Acme",
"tagline": "one-line brand tagline",
"description": "2-3 sentences on what the company does",
"sourceUrl": "https://acme.com",
"logo": { "primary": "logos/<best candidate or null>", "alternates": ["logos/<others>"], "notes": "why this primary; usage" },
"colors": [
{ "role": "background", "hex": "#f5f4ed", "oklch": "oklch(96% 0.01 90)", "name": "Parchment", "usage": "page background" },
{ "role": "surface", "hex": "#ffffff", "oklch": "oklch(100% 0 0)", "name": "Card", "usage": "cards, panels" },
{ "role": "foreground", "hex": "#141413", "oklch": "oklch(17% 0.005 90)", "name": "Ink", "usage": "primary text" },
{ "role": "muted", "hex": "#87867f", "oklch": "oklch(60% 0.01 90)", "name": "Stone", "usage": "secondary text" },
{ "role": "border", "hex": "#e8e6dc", "oklch": "oklch(92% 0.01 90)", "name": "Hairline", "usage": "borders, dividers" },
{ "role": "accent", "hex": "#d97757", "oklch": "oklch(67% 0.13 40)", "name": "Terracotta", "usage": "CTAs, links" },
{ "role": "accent-secondary", "hex": "#3d7a4f", "oklch": "oklch(50% 0.09 150)", "name": "Moss", "usage": "success, secondary" }
],
"typography": {
"display": { "family": "Tiempos", "fallbacks": ["Georgia", "serif"], "weights": [400, 600], "notes": "headlines" },
"body": { "family": "Inter", "fallbacks": ["system-ui", "sans-serif"], "weights": [400, 500, 700], "googleFontsUrl": "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap" },
"mono": { "family": "JetBrains Mono", "fallbacks": ["monospace"], "weights": [400] }
},
"voice": { "adjectives": ["confident", "warm"], "tone": "how the brand speaks", "messagingPillars": ["pillar"], "vocabulary": { "use": ["words it uses"], "avoid": ["words it avoids"] } },
"imagery": {
"style": "one line", "subjects": ["typical subjects"], "treatment": "how images are treated", "avoid": ["clichés to avoid"],
"samples": [
{ "file": "imagery/hero.png", "kind": "hero", "caption": "Homepage hero" },
{ "file": "imagery/product.png", "kind": "product", "caption": "Product screenshot" }
]
},
"layout": { "radius": "12px", "borderWeight": "1px", "spacing": "8px baseline grid", "postureRules": ["3-5 observed posture rules"] }
}
oklch() and say so in usage.family, put the closest Google Font first
in fallbacks, set googleFontsUrl, and note "stand-in for ".logos/<file> paths you saved; never pick a photographic
og:image as primary unless nothing else exists. Never leave logo.primary
empty when the site has any mark.imagery/
and reference them by their imagery/<file> path in imagery.samples; 6–8
varied, on-brand images filtered by rendered size — never icons or chrome.BRAND.md — a prose brand guide an autonomous design agent can follow
(visual theme, logo usage, color roles, typography, voice & tone, imagery,
component stylings, layout & spacing, depth, dos & don'ts, agent prompt guide).brand.json, derives the
light/dark/compact design tokens and the brand-system artifacts (landing, deck,
poster, email, newsletter, form), and registers the brand as a reusable
user:<id> design system so it is selectable everywhere:od brand finalize <brandId> --json
imagery/ samples into the brand so the Images gallery resolves, and
re-renders brand.html one last time with the status flipped to "Brand ready",
a Design system module (the live component kit
with a Light/Dark toggle plus the derived token chips — colorPrimary, fontSize,
borderRadius, …), and the six Brand Assets tiles (landing, deck, poster,
email, newsletter, form) lit up as live previews that each link to their full
system/artifacts/<kind>.html page. If finalize reports a validation error, fix
brand.json and run it again. Finish by pointing the user at the completed brand.html — the logo,
palette, typography, voice, and the assets they can now preview — and confirm
the brand was registered.