/adobe-fonts

name: adobe-fonts
description: >
  Finds, searches, and previews real, licensable Adobe Fonts typefaces: contextual
  recommendations, direct lookup by name or facets (foundry, designer, style),
  metadata (language support, weight, foundry), style variants in a family, and a
  visual specimen. Use for font recommendations, looking up a specific font, "what does
  [font] look like", a font's language support or designer/foundry, weights/widths in a
  family, or choosing/pairing fonts for a design (poster, invitation, social post,
  brand, website, presentation). Discovers and previews fonts only — does not lay out
  the design. Triggers: "what font for...", "find fonts like [name]", "search Adobe
  Fonts for...", "does [font] support [language]", "who designed [font]".
compatibility: "Requires Adobe for creativity tools — font_recommend, font_search, font_details, font_styles, and font_preview. Runs on both widget-capable (e.g. Claude) and no-widget (e.g. Codex) surfaces; widget touchpoints are an optional clarifying question and the font_preview specimen card, both of which fall back to plain text/markdown."
license: Apache-2.0
allowed-tools: adobe_mandatory_init font_recommend font_search font_details font_styles font_preview
metadata:
  version: 1.0.0
  visibility: public
  surface: [claude, codex]

Adobe Fonts

Discovers, searches, and previews real, licensable fonts from the Adobe Fonts catalog via five Adobe for Creativity MCP tools: `font_recommend` (contextual suggestions), `font_search` (direct lookup by name or facets), `font_details` (metadata for known fonts), `font_styles` (every style variant in a family), and `font_preview` (a visual specimen of any font).

> **Surface note:** This skill has no file uploads, so the flow is largely the same on > Claude and Codex. Surfaces differ in two places: *asking a clarifying question* — use the > `AskUserQuestion` widget where available (e.g. Claude), or plain text where it isn't (e.g. > Codex) — and *showing a font specimen* — `font_preview` renders an inline card on MCP App > hosts (e.g. Claude), or returns `image_markdown` to embed directly on hosts without that > widget (e.g. Codex). Follow the default flow below; the fallback notes only apply when the > relevant widget is unavailable.

**Hard constraint:** every font this skill surfaces — recommended, searched, or looked up — must be a real, licensable Adobe Fonts family that came back in a tool's own results. Never substitute a font from prior knowledge just because it seems "similar" or matches a name the user mentioned — fonts outside a tool's own results are not licensable here.

---

Tool Reference

| Task | Tool | Notes | |------|------|-------| | Initialize | `adobe_mandatory_init` | Step 0; returns file-handling rules and tool routing guidance | | Get contextual suggestions | `font_recommend` | Open-ended "what font for X"; call once per `text_hierarchy` / document | | Look up specific fonts | `font_search` | Direct lookup by name and/or facets (foundry, designer, style, writing system); sorted, paginated | | Get font metadata | `font_details` | Language support, foundry, designers, weight/style for known font(s) — text only, no image | | Get family style variants | `font_styles` | Every weight/width/italic in one or more known fonts' families | | Show a visual specimen | `font_preview` | One font per call, by its exact `postscript_name` |

---

Workflow

Step 0 — Initialize Adobe Tools

Call `adobe_mandatory_init` first. It returns the file-handling rules and tool routing guidance required for the rest of the workflow.

{ "skill_name": "adobe-fonts", "skill_version": "1.0.0" }

---

Step 1 — Choose the right tool

| The user wants... | Tool | |---|---| | Open-ended suggestions for a project, brand, or mood ("what font for a wedding invite", "pair a heading and body font") | `font_recommend` | | A specific named font, or fonts filtered by foundry/designer/style/writing system ("find fonts like Futura", "fonts by Erik Spiekermann") | `font_search` | | Metadata about font(s) they've already identified — language support, foundry, designer, weight/style ("does Futura support Korean?", "who designed this font?") | `font_details` | | Every weight/width/italic in a family they've already identified ("what weights does Acumin Pro come in?") | `font_styles` | | To see what a font looks like ("what does this font look like", "show me a sample") | `font_preview` |

These aren't mutually exclusive — a request often chains two: `font_search` or `font_recommend` to find a font, then `font_details` / `font_styles` for more about it, or `font_preview` to see it. Don't use `font_recommend` for a direct/named lookup, or `font_search` for an open-ended design brief — each tool's own description defers to the other for that case.

---

Step 2 — Identify fonts correctly

`font_preview`, `font_details`, and `font_styles` take a `font_identifier` (`{postscript_name, font_id}`, `font_id` optional) or a list of them. Rules that apply everywhere a `postscript_name` or `font_identifier` is passed, including `font_recommend`'s / `font_search`'s `selected_font`:

• **Always use a value already returned by a prior call** — from

`font_identifier.postscript_name` (or a bare `postscript_name`) in a `font_recommend` or `font_search` result, or from a `font_styles` `styles[]` entry — never guess or derive one from a display name.

• `postscript_name` matching is **case-sensitive with no fuzzy matching** —

`"myriadpro-regular"` will not resolve `"MyriadPro-Regular"`.

• If the user names a font casually (e.g. "something like Futura") and you don't yet

have its PostScript name, resolve it first with `font_search` (`user_query` + `font_query: true`) before using it as `selected_font` or in any `font_identifier`.

• `font_id` is optional wherever `postscript_name` is given; supply it too when you

already have it, but never fabricate one.

---

Step 3 — Ca