Agent skill · stephenturner
brand-yml
Create a _brand.yml file for Quarto projects that captures brand colors, typography, and identity in a structured YAML format. Use this skill whenever the user mentions _brand.yml, brand.yml, Quarto branding, brand identity for Quarto, or wants consistent colors and fonts across Quarto documents, websites, presentations, or Shiny apps. Also trigger when the user asks to extract brand colors or fonts from a website, PDF brand guidelines, or style guide for use with Quarto. Even if the user just says "set up my brand" or "make my Quarto docs match our brand," this is the right skill.
What it needs
About 4k tokens when loaded.
What this skill does
brand-yml: Create Brand Identity Files for Quarto Generate a valid brand.yml file from brand guidelines, a website, a description, or an existing file that needs refinement. Before You Start Read the full specification: This reference contains every allowed field, syntax variants, and the complete annotated example. Consult it whenever you are unsure about field names, nesting, or allowed values. Workflow 1. Gather Brand Information Determine the input source. The user may provide one or more of these: Website URL -- Use webfetch to retrieve the page. Extract CSS custom properties, meta theme colors, prominent hex values, font-family declarations, and Open Graph metadata. If the page links to a CSS file, fetch that too. Look for Google Fonts or Bunny Fonts <link> tags. Uploaded brand guidelines (PDF, image, or document) -- Read the uploaded file. Extract named colors (with hex values), font families, usage rules (which font is for headings vs. body), and logo file references. Manual description -- The user describes their colors, fonts, and identity in plain text. Ask clarifying questions only if critical information is missing (primary color and at least one font are the minimum viable brand). Existing brand.yml -- The user uploads or pastes a file to fix, extend, or modernize. Validate it against the spec, identify issues, and propose corrections. If the source is ambiguous, ask which approach the user prefers. 2. Research and Resolve Use web search to fill gaps when helpful: Match proprietary or unknown fonts to the closest Google Fonts equivalent. Always note the substitution and the original font name in a YAML comment. Verify exact hex values for well-known brands if the user gives a name but not a code (e.g., "use UVA colors"). Check Google Fonts for available weights and styles when setting up typography.fonts entries. 3. Assemble the brand.yml Follow these rules strictly: Structure rules: Include only fields that apply. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills stephenturner/brand-yml