docs-brandinglisted

# docs-branding — Derive a brand, advise, then ask This skill exists because agents reach for `#3b82f6` and `Arial` the moment branding comes up. They invent. The whole point here is the opposite: **DERIVE → ADVISE → ASK DYNAMICALLY**. Find the brand signals that already exist, turn each one into a concrete, defensible recommendation, and put a real choice in front of the user before touching anything. ## Workflow 1. **Connect and read current state** — resolve which workspace you are operating on and read its existing branding (accent/muted colors for light + dark, `base_foreground`/`base_background`, `font_family`, `default_theme`, `logo_url`, `icon_url`, `custom_name`). Whatever is already set is a brand signal, not a blank slate — treat it as the starting point and the thing you must respect, not overwrite blindly. 2. **DERIVE — collect brand signals from what already exists. Never invent.** Gather evidence from every source available before forming an opinion: - **Source site** (if the docs came from a website or one is known): fetch its HTML and read `<meta name="theme-color">`, `<meta property="og:image">`, favicon, and any inline CSS custom properties / `--accent` style tokens. The site's `theme-color` is the single strongest signal of the intended accent. - **Logo / icon** (`logo_url`, `icon_url`, or a file the user provides): determine the dominant non-neutral color. This is the brand's anchor color — describe it by hex. - **Workspace** already-set valu