---
name: skill-brand-system
type: skill
description: >-
  Define and maintain a domain's design system and brand identity — palette,
  type, logo usage, art direction, photography guidelines and components — and
  read or score an existing system before working in it. Use this whenever Pixel
  needs to establish or evolve how a venture looks, set up its design system,
  keep its identity coherent, or ingest a client's or venture's existing system
  against the design-system standard. Cross-domain: each venture has its own
  system; this skill owns them. Feeds convention-brand and is the substrate
  every other Pixel skill reads.
---

# skill-brand-system

Pixel's foundational skill. Owns each domain's design system — the kit of parts everything else is built from — and keeps it coherent and current. Two modes: **build** (stand up or evolve a system) and **read** (ingest and score an existing one).

## Behaviour — build mode

Trigger: a domain needs a design system stood up or evolved, or identity has drifted across its surfaces.

Loop:

1. Read the domain's strategy and positioning (so the look serves the strategy), `convention-aesthetic` (the cross-venture taste baseline the identity specialises), and any existing brand material.
2. Define or refine the core system: palette, type scale, logo usage, spacing, art direction, photography and imagery guidelines, and the base components — to the bar in `standard-design-system`.
3. Express it as tokens and reusable parts where possible, not as a static style sheet, so it can flow into code via `skill-design-tokens`.
4. Record it in the domain's `convention-brand`; flag what the operator must approve (a new logo, a palette change).

## Behaviour — read mode

Trigger: Pixel must work in or extend a design system it did not create — a client's system, or a venture system that predates canon — and needs to understand it before touching it.

Loop:

1. Inventory the system: tokens, component set, naming, coverage, documentation. For Figma-side systems use the Figma MCP (`get_design_context`, `get_variable_defs`, `search_design_system`); for code-side tokens read the repo.
2. Score the inventory against `standard-design-system` (pass / partial / fail per bar), tagging each finding known / assumed / unknown.
3. Output the scored inventory. It is both Pixel's working map of the system and the craft-level input Sonar's Design System audit (`convention-audit`) consumes — produce it once, let the strategy layer read it.

Read mode observes and scores; it changes nothing. A failed bar is a finding to raise, not a licence to restructure.

## Reads

The domain's strategy and positioning, existing brand assets, `convention-aesthetic`, `convention-brand`, `standard-design-system`, `operating-model`.

## Guardrails

Identity changes are consequential — propose, do not silently restyle a live brand. Keep the system a living, tokenised source, not a one-off artboard. One system per domain; do not bleed one brand's look into another. Propose-only to canon.

On finish, where Aled's review of this work revealed a taste signal (a rejection with a reason, a "more like this", a pulled reference), run `skill-ops-retro` capture: file a `FRICTION:` note to the Pulse queue targeting `convention-aesthetic` or the domain's `convention-brand` instance, quoting the verdict.
