Update to Font Pairing: Design & Brands

{
  "name": "typography-direction-comparison",
  "description": "Develop, preview, and compare distinct Google Font directions for one brand or product brief. Use when a user asks for multiple typography concepts, alternatives, mood-based routes, or an A/B-style creative comparison before choosing a trio. Default to three clearly differentiated directions unless the user requests another manageable count; use a separate `suggest-fonts` call and widget for each direction.",
  "included_files": [],
  "skill_md_contents": "---\nname: typography-direction-comparison\ndescription: Develop, preview, and compare distinct Google Font directions for one brand or product brief. Use when a user asks for multiple typography concepts, alternatives, mood-based routes, or an A/B-style creative comparison before choosing a trio. Default to three clearly differentiated directions unless the user requests another manageable count; use a separate `suggest-fonts` call and widget for each direction.\n---\n\n# Typography Direction Comparison\n\nCreate alternatives that represent meaningful strategic choices, not minor substitutions within one idea.\n\n## Verify the app tool\n\nConfirm that `suggest-fonts` is available before defining or describing font directions. If it is unavailable, stop and say that the Font Pairing app must be enabled to generate the previews; do not present speculative families as completed directions. Describe a preview as rendered only after its tool call returns structured font output.\n\n## Frame the comparison\n\nIdentify the shared audience, context, brand traits, constraints, and evaluation criteria. Default to three directions. Honor an explicit smaller count, and keep a larger request manageable by grouping or narrowing it before generating excessive widgets.\n\nDefine and name every direction before selecting fonts. Make each direction differ on at least two useful dimensions, such as:\n\n- traditional versus contemporary;\n- expressive versus restrained;\n- serif-led versus sans-led;\n- high versus subtle role contrast;\n- editorial warmth versus product precision.\n\nKeep non-typographic constraints consistent so the comparison remains meaningful.\n\n## Generate the directions\n\nFor each direction:\n\n1. State its name and one-sentence intent.\n2. Select a coordinated heading, accent, and body trio that embodies that intent.\n3. Invoke `suggest-fonts` once for that direction. Use only schema-listed families and supported weight/style combinations, and identify the direction in the optional `reason`.\n4. Add one concise strength and one tradeoff after its widget.\n\nDo not reuse two of three families across directions unless a fixed or locked font is part of the brief. When a font is fixed, vary the surrounding roles enough to create genuinely different systems.\n\n## Compare and recommend\n\nAfter all requested widgets appear:\n\n- compare the directions against the same criteria;\n- identify the strongest context for each;\n- recommend one direction and explain the decisive tradeoff;\n- ask the user to choose a direction or name the element to preserve.\n\nOn the next refinement, work only from the chosen direction unless the user requests another comparison. Preserve model-visible locked fonts and invoke `suggest-fonts` again only for the revised trio.\n\n## Deliver the result\n\nProvide:\n\n- named and clearly differentiated directions;\n- one `suggest-fonts` widget per direction;\n- a compact strengths-and-tradeoffs comparison;\n- one reasoned recommendation;\n- a direct refinement choice.\n\n## Boundaries\n\n- The app renders one trio per tool call; do not claim the widgets form a single side-by-side canvas.\n- Treat the `suggest-fonts` schema as authoritative and correct any rejected variant instead of describing an unrendered preview as successful.\n- Do not claim that a subjective recommendation is an objective score or user-test result.\n- Do not claim to operate locks, similarity, or preview-text controls. Use only model-visible state and explicit follow-up instructions.\n"
}