---
name: brand-setup
description: "Logo, color, typography, preview, and the Brand Standards document. Use when a person asks to install or apply \"Brand Setup\" (FTR-16) in a project, or when working in a project that has it installed."
---

# Brand Setup (FTR-16, version 1.0)

> Generated from library record FTR-16 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

Logo, color, typography, preview, and the Brand Standards document

## When to use this skill

- A person asks to install, apply or update "Brand Setup" (FTR-16) in a project.
- A project's agent instructions list brand-setup as installed and the task touches what it covers.
- Requires first: FTR-07 (skill folder-structure).

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
Run the brand infrastructure check first — do not rebuild what works:
- Check Project Files for any file with "brand" or "standards" in the name (e.g., `[ProjectCode]_Brand_Standards.md`).
- Check the filesystem for `brand\Brand_Standards.md` or any file in a `brand\` folder containing "brand" or "standards".
- Check `admin\AGENT_INSTRUCTIONS.md` — is the BRAND STANDARDS section already populated with colors, fonts, and a named style?
- Confirm whether the logo (`[ProjectCode]_Logo.png`) is in Project Files.
- If brand infrastructure exists: read it, check for a complete color palette (all roles with hex), confirmed logo, both typography tiers, and at least one named document style. Fill only the specific gaps — do not rebuild from scratch.

### Ask, only if needed
Work through the stages, asking only what assessment can't determine:
- 7A Logo: "Have you uploaded your logo to Project Files? If yes, confirm the filename ([ProjectCode]_Logo.png). If not, upload now (PNG, white background, tightly cropped) — or tell me to proceed without it and we'll flag it."
- 7B Colors: either "Drop your logo and I'll extract the dominant colors and render swatches" or "Tell me your colors — describe them or give hex codes." Render swatches inline; colors aren't locked until the user confirms.
- 7C Typography: present the two-tier defaults for the project type; "Does this work, or do you have specific fonts in mind? If you have a document with your preferred fonts, drop it in and I'll pull the typography."
- 7D Preview: render 2-3 style variations inline; "Pick your default style. Flag any others to keep as alternates." Cap at 2 preview rounds, then redirect.

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### Confirm
Confirm: your brand is built — Brand Standards document (markdown + Word) generated and saved to brand\ and Project Files, and the brand rule is in your agent instructions so every formatted document matches automatically. Want to install another, or is that everything for now?

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.