SKILL.md

---
name: brand-brief-to-type-system
description: Turn a brand, product, or campaign brief into a coordinated heading, accent, and body Google Font system and preview it with the Font Pairing app. Use when a user supplies an audience, brand personality, market, medium, reference style, or creative direction and wants a concrete font trio. Also use for incomplete briefs when sensible assumptions can resolve the missing details. Do not use for abstract typography advice that does not request a specific pairing.
---

# Brand Brief to Type System

Turn strategic language into one usable, previewed typography direction. Keep the response focused on decisions the user can evaluate in the widget.

## Verify the app tool

Confirm that `suggest-fonts` is available before selecting or describing a trio. If it is unavailable, stop and say that the Font Pairing app must be enabled to generate the preview; do not present speculative families as a completed result. Describe a preview as rendered only after the tool returns structured font output.

## Gather the brief

Identify or infer:

- the audience and desired impression;
- the product, content, and reading context;
- three to five personality traits;
- any required, preferred, or forbidden fonts and styles;
- the balance between distinctiveness and restraint.

Ask one concise question only when the answer would materially change the direction. Otherwise, proceed and state important assumptions briefly.

## Build the system

1. Translate the brief into selection criteria for tone, hierarchy, contrast, and sustained reading.
2. Define each role before choosing families:
   - make the heading carry the strongest brand personality;
   - make the accent support navigation, emphasis, or short supporting copy;
   - make the body comfortable for the expected reading context.
3. Choose a coordinated trio rather than three individually interesting fonts. Avoid giving every role the same visual intensity unless the user explicitly wants that effect.
4. Invoke `suggest-fonts` with exactly one `heading`, `accent`, and `body`. Use only schema-listed families and supported weight/style combinations. Include a concise `reason` tied to the brief.
5. After the widget appears, explain each role in one sentence and name the most important tradeoff. Encourage the user to edit the specimen, lock successful roles, or request a refinement when useful.

For a refinement, preserve fonts marked `locked` in model-visible widget state and honor constraints stated in the follow-up prompt. Invoke `suggest-fonts` again only when presenting a revised trio.

## Deliver the result

Provide:

- a short name for the direction;
- the visual trio from `suggest-fonts`;
- a concise rationale for heading, accent, and body;
- one practical usage note or tradeoff;
- a clear next refinement choice when the brief leaves meaningful alternatives.

## Boundaries

- Recommend only Google Font families and variants accepted by `suggest-fonts`.
- Treat the tool schema as authoritative; do not invent or silently substitute unsupported variants.
- Do not claim to edit preview copy, locks, or similarity controls. Those are widget actions; only model-visible lock state may guide a later recommendation.
- Do not claim verified glyph coverage, loading performance, or accessibility compliance. The app does not expose the measurements needed for those guarantees.