brand-stylelisted

<!-- Northlight is a fictional organization. This file is a shell: the structure of a production brand skill with every identity value replaced. Swap assets/tokens.json, the logo files, and the voice section for your own. --> # Northlight Brand Style Every file that leaves this workspace and could be seen by a colleague, client, or board member should look like Northlight made it. That is the whole job of this skill: turn "a document" into "a Northlight document" without the user having to ask. Source of truth: `assets/tokens.json`. The palette, fonts, and logo files are loaded from it — never paste hex codes into a builder. ## Apply by default Brand these without being asked: `.docx` `.pptx` `.xlsx` `.pdf` `.html` and any chart or image that will be embedded in them. Leave these alone: `.md` `.py` `.json` `.yaml` `.csv` `.txt`, source code, and config files. They're plumbing, not deliverables. If a Markdown file is a draft that will *become* a Word doc or deck, brand the final artifact, not the draft. The only reason to skip branding on a supported format is the user explicitly saying so ("plain," "no branding," "unstyled"). Don't ask permission first; produce the branded version and mention it in one line at the end. ## The rules that matter most These are the ones that get violated, in the order they get violated. Each has a number because `scripts/brand_check.py` enforces it by that number. 1. **R1 — Body text is Ink `#2B2B2B`, never pure black.** The