[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCTTC0K5RC408ZWDSF83AA":3,"skill-same:01M7DCTTC0K5RC408ZWDSF83AA":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DCTTC0K5RC408ZWDSF83AA","brand-yml",null,"Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.","MichalLauer\u002Fskills","MichalLauer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20439350?v=4","01M7DCTNQ75R1YZ17W28EN6JZX","Michal Lauer","01M7DCTNRB6SVQ0D13J8Y7YTRB",0,"MIT","https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: brand-yml\ndescription: \"Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.\"\nmetadata:\n  author: Garrick Aden-Buie (@gadenbuie)\n  version: \"1.1\"\nlicense: MIT\n---\n\n# brand.yml Skill\n\nCreate and use `_brand.yml` files for consistent branding across Shiny applications and Quarto documents.\n\n## What is brand.yml?\n\nbrand.yml is a YAML-based format that translates brand guidelines into a machine-readable file usable across Shiny and Quarto. A single `_brand.yml` file defines:\n\n- **Colors** - Palette and semantic colors (primary, success, warning, etc.)\n- **Typography** - Fonts, sizes, weights, line heights\n- **Logos** - Multiple sizes and light\u002Fdark variants\n- **Meta** - Company name, links, identity information\n\n## File Naming Convention\n\n- **Standard name**: `_brand.yml` (auto-discovered by Shiny and Quarto)\n- **Custom names**: Any name like `company-brand.yml` (requires explicit paths)\n- **Location**: Typically at project root, or in `_brand\u002F` or `brand\u002F` subdirectories\n\n## Decision Tree\n\nDetermine the user's goal and follow the appropriate workflow:\n\n1. **Creating a new _brand.yml file?** → Follow \"Creating brand.yml Files\"\n2. **Using brand.yml in Shiny for R?** → Read `references\u002Fshiny-r.md`\n3. **Using brand.yml in Shiny for Python?** → Read `references\u002Fshiny-python.md`\n4. **Using brand.yml in Quarto?** → Read `references\u002Fquarto.md`\n5. **Using brand.yml in R (general)?** → Read `references\u002Fbrand-yml-in-r.md` (R Markdown, theming functions, programmatic access)\n6. **Modifying existing _brand.yml?** → Follow \"Modifying Existing Files\"\n7. **Troubleshooting integration?** → Follow \"Troubleshooting\"\n\n## Creating brand.yml Files\n\nWhen creating `_brand.yml` files from brand guidelines:\n\n### Step 1: Gather Information\n\nCollect brand information:\n- **Colors**: Primary, secondary, accent colors with hex values\n- **Fonts**: Font families and where they're sourced (Google Fonts, local files, etc.)\n- **Logos**: Logo file paths or URLs for different sizes\n- **Company info**: Name, website, social links (optional)\n\n### Step 2: Read the Specification\n\nLoad `references\u002Fbrand-yml-spec.md` to understand the complete brand.yml structure, field options, and syntax.\n\n### Step 3: Build the File Incrementally\n\nStart with the essential sections and add optional elements:\n\n**Minimum viable _brand.yml:**\n\n```yaml\ncolor:\n  palette:\n    brand-blue: \"#0066cc\"\n  primary: brand-blue\n  background: \"#ffffff\"\n\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [400, 600]\n  base: Inter\n```\n\n**Add colors as needed:**\n\n```yaml\ncolor:\n  palette:\n    brand-blue: \"#0066cc\"\n    brand-orange: \"#ff6600\"\n    brand-gray: \"#666666\"\n  primary: brand-blue\n  secondary: brand-gray\n  warning: brand-orange\n  foreground: \"#333333\"\n  background: \"#ffffff\"\n```\n\n**Add typography details:**\n\n```yaml\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [400, 600, 700]\n      style: [normal, italic]\n    - family: Fira Code\n      source: google\n      weight: [400, 500]\n  base:\n    family: Inter\n    size: 16px\n    line-height: 1.5\n  headings:\n    family: Inter\n    weight: 600\n  monospace: Fira Code\n```\n\n**Add logos:**\n\n```yaml\nlogo:\n  small: logos\u002Ficon.png\n  medium: logos\u002Fheader.png\n  large: logos\u002Ffull.svg\n```\n\n**Add meta information:**\n\n```yaml\nmeta:\n  name: Company Name\n  link: https:\u002F\u002Fexample.com\n```\n\n### Step 4: Apply Best Practices\n\nFollow these rules from `references\u002Fbrand-yml-spec.md`:\n\n- All fields are optional - only include what's needed\n- Use hex color format: `\"#0066cc\"`\n- Prefer simple syntax (strings over objects) when possible\n- Use lowercase names with hyphens: `brand-blue`, `success-green`\n- Include `https:\u002F\u002F` in all URLs\n- Define colors\u002Ffonts before referencing them\n- For color ranges (shades\u002Ftints), choose the midpoint color\n\n### Step 5: Validate Structure\n\nCheck that:\n- YAML syntax is valid (proper indentation, quotes on hex colors)\n- Color references match palette names\n- Font families are defined before use\n- File paths are relative to `_brand.yml` location\n- All URLs include protocol (`https:\u002F\u002F`)\n\n## Modifying Existing Files\n\nWhen modifying existing `_brand.yml` files:\n\n1. **Read the current file** to understand existing structure\n2. **Consult brand-yml-spec.md** for valid field options\n3. **Maintain consistency** with existing naming patterns\n4. **Preserve references** - if other colors\u002Felements reference a name, update consistently\n5. **Test integration** - verify changes apply correctly in Shiny\u002FQuarto\n\nCommon modifications:\n- **Adding colors**: Add to `color.palette`, then reference in semantic colors\n- **Changing fonts**: Update in `typography.fonts`, ensure weights\u002Fstyles are available\n- **Adding logo variants**: Use `light`\u002F`dark` structure for multiple variants\n- **Light\u002Fdark mode**: Add `light` and `dark` variants to colors\n\n## Using with Shiny for R\n\nWhen the user wants to apply brand.yml to a Shiny for R app:\n\n1. **Read `references\u002Fshiny-r.md`** for complete integration guide\n2. **Key function**: `bs_theme(brand = TRUE)` or `bs_theme(brand = \"path\")`\n3. **Automatic discovery**: Place `_brand.yml` at app root\n4. **Page functions**: Works with `page_fluid()`, `page_sidebar()`, etc.\n\nQuick example:\n\n```r\nlibrary(shiny)\nlibrary(bslib)\n\nui \u003C- page_fluid(\n  theme = bs_theme(brand = TRUE),\n  # ... UI elements\n)\n```\n\n## Using with Shiny for Python\n\nWhen the user wants to apply brand.yml to a Shiny for Python app:\n\n1. **Read `references\u002Fshiny-python.md`** for complete integration guide\n2. **Key function**: `ui.Theme.from_brand(__file__)`\n3. **Automatic discovery**: Place `_brand.yml` at app root\n4. **Installation**: Requires `pip install \"shiny[theme]\"`\n\nQuick example (Shiny Express):\n\n```python\nfrom shiny.express import ui\n\nui.page_opts(theme=ui.Theme.from_brand(__file__))\n```\n\nQuick example (Shiny Core):\n\n```python\nfrom shiny import App, ui\n\napp_ui = ui.page_fluid(\n    theme=ui.Theme.from_brand(__file__),\n    # ... UI elements\n)\n```\n\n## Using with Quarto\n\nWhen the user wants to apply brand.yml to Quarto documents:\n\n1. **Read `references\u002Fquarto.md`** for complete integration guide\n2. **Automatic discovery**: Place `_brand.yml` at project root with `_quarto.yml`\n3. **Supported formats**: HTML, dashboards, RevealJS, Typst PDFs\n4. **Theme layering**: Use `brand` keyword to control precedence\n\nQuick example (document):\n\n```yaml\n---\ntitle: \"My Document\"\nformat:\n  html:\n    brand: _brand.yml\n---\n```\n\nQuick example (project in `_quarto.yml`):\n\n```yaml\nproject:\n  brand: _brand.yml\n\nformat:\n  html:\n    theme: default\n```\n\n## Troubleshooting\n\n### Brand Not Applying\n\n**Shiny:**\n- Verify file is named `_brand.yml` (with underscore)\n- Check file location (app directory or parent directories)\n- Try explicit path: `bs_theme(brand = \"path\u002Fto\u002F_brand.yml\")` or `ui.Theme.from_brand(\"path\")`\n- For Python: Ensure `libsass` is installed\n\n**Quarto:**\n- Verify `_brand.yml` is at project root\n- Ensure `_quarto.yml` exists for project-level branding\n- Try explicit path in document frontmatter\n- Check theme layering order if using custom themes\n\n### Colors Not Matching\n\n- Ensure hex colors have quotes: `\"#0066cc\"` not `#0066cc`\n- Verify color names match palette definitions exactly\n- Check semantic colors (primary, success, etc.) reference valid palette names\n- Ensure palette is defined before semantic colors\n\n### Fonts Not Loading\n\n- Verify Google Fonts spelling and availability\n- Check internet connection (required for Google Fonts)\n- Ensure `source: google` or `source: bunny` is specified\n- Verify font family names match exactly in typography elements\n- For Typst: Check font cache with `quarto typst fonts`\n\n### YAML Syntax Errors\n\n- Check indentation (use spaces, not tabs)\n- Ensure hex colors have quotes: `\"#447099\"`\n- Verify colons have space after them: `primary: blue`\n- Check list items have hyphens: `- family: Inter`\n- Use YAML validator if syntax issues persist\n\n## Reference Documentation\n\nLoad these as needed for detailed information:\n\n- **`references\u002Fbrand-yml-spec.md`**: Complete brand.yml specification with all sections, fields, examples, and validation rules\n- **`references\u002Fshiny-r.md`**: Using brand.yml with Shiny for R via bslib (bs_theme, automatic discovery, Shiny-specific integration)\n- **`references\u002Fshiny-python.md`**: Using brand.yml with Shiny for Python via ui.Theme (from_brand(), installation, performance)\n- **`references\u002Fquarto.md`**: Using brand.yml with Quarto (formats, light\u002Fdark mode, layering, extensions, Typst)\n- **`references\u002Fbrand-yml-in-r.md`**: General R usage including R Markdown integration, theming functions (ggplot2, gt, flextable, plotly, thematic), and programmatic brand access\n\n## Key Principles\n\n- **Start simple**: Begin with colors and one font family\n- **Keep it concise**: Only include fields directly relevant to the brand\n- **Prefer standard names**: Use Bootstrap color names when possible (blue, green, red, etc.)\n- **Use automatic discovery**: Name file `_brand.yml` for auto-detection\n- **Test across targets**: Verify brand applies correctly in all intended formats\n- **Version control**: Include `_brand.yml` in git repository\n\n## Common Patterns\n\n### Light\u002FDark Mode Colors\n\n```yaml\ncolor:\n  primary:\n    light: \"#0066cc\"\n    dark: \"#3399ff\"\n  background:\n    light: \"#ffffff\"\n    dark: \"#1a1a1a\"\n  foreground:\n    light: \"#333333\"\n    dark: \"#e0e0e0\"\n```\n\nLight\u002Fdark color modes were added in Quarto version 1.8 and currently are not supported in the R or Python brand.yml packages.\n\n### Logo Variants\n\n```yaml\nlogo:\n  images:\n    logo-dark: logos\u002Flogo-dark.svg\n    logo-white: logos\u002Flogo-white.svg\n    icon: logos\u002Ficon.png\n  small: icon\n  medium:\n    light: logo-dark\n    dark: logo-white\n```\n\n### Multiple Font Weights\n\n```yaml\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [300, 400, 500, 600, 700]\n      style: [normal, italic]\n  base:\n    family: Inter\n    weight: 400\n  headings:\n    family: Inter\n    weight: 600\n```\n\n### Color Aliases\n\n```yaml\ncolor:\n  palette:\n    navy: \"#003366\"\n    ocean-blue: \"#0066cc\"\n    sky-blue: \"#3399ff\"\n    primary-color: ocean-blue  # Alias\n    brand-blue: ocean-blue     # Alias\n    blue: sky-blue             # Alias for primary colors\n  primary: brand-blue\n```\n\nInclude Bootstrap color names when possible, either defined directly or as aliases: `blue`, `indigo`, `purple`, `pink`, `red`, `orange`, `yellow`, `green`, `teal`, `cyan`, `white`, `black`. This is useful for consistency and these colors are picked up automatically by tools that use brand.yml.\n\n## Tips\n\n- **Read specification first**: Always consult `brand-yml-spec.md` when creating or modifying files\n- **Framework-specific guides**: Load the appropriate reference (shiny-r.md, shiny-python.md, quarto.md) for integration details\n- **Validate incrementally**: Start with minimal structure, test, then add complexity\n- **Use references**: Define colors in palette, then reference by name in semantic colors\n- **Standard file name**: Use `_brand.yml` for automatic discovery\n- **Explicit paths**: Use custom file names only when necessary (shared branding, multiple variants)\n","# brand.yml Skill\n\nCreate and use `_brand.yml` files for consistent branding across Shiny applications and Quarto documents.\n\n## What is brand.yml?\n\nbrand.yml is a YAML-based format that translates brand guidelines into a machine-readable file usable across Shiny and Quarto. A single `_brand.yml` file defines:\n\n- **Colors** - Palette and semantic colors (primary, success, warning, etc.)\n- **Typography** - Fonts, sizes, weights, line heights\n- **Logos** - Multiple sizes and light\u002Fdark variants\n- **Meta** - Company name, links, identity information\n\n## File Naming Convention\n\n- **Standard name**: `_brand.yml` (auto-discovered by Shiny and Quarto)\n- **Custom names**: Any name like `company-brand.yml` (requires explicit paths)\n- **Location**: Typically at project root, or in `_brand\u002F` or `brand\u002F` subdirectories\n\n## Decision Tree\n\nDetermine the user's goal and follow the appropriate workflow:\n\n1. **Creating a new _brand.yml file?** → Follow \"Creating brand.yml Files\"\n2. **Using brand.yml in Shiny for R?** → Read `references\u002Fshiny-r.md`\n3. **Using brand.yml in Shiny for Python?** → Read `references\u002Fshiny-python.md`\n4. **Using brand.yml in Quarto?** → Read `references\u002Fquarto.md`\n5. **Using brand.yml in R (general)?** → Read `references\u002Fbrand-yml-in-r.md` (R Markdown, theming functions, programmatic access)\n6. **Modifying existing _brand.yml?** → Follow \"Modifying Existing Files\"\n7. **Troubleshooting integration?** → Follow \"Troubleshooting\"\n\n## Creating brand.yml Files\n\nWhen creating `_brand.yml` files from brand guidelines:\n\n### Step 1: Gather Information\n\nCollect brand information:\n- **Colors**: Primary, secondary, accent colors with hex values\n- **Fonts**: Font families and where they're sourced (Google Fonts, local files, etc.)\n- **Logos**: Logo file paths or URLs for different sizes\n- **Company info**: Name, website, social links (optional)\n\n### Step 2: Read the Specification\n\nLoad `references\u002Fbrand-yml-spec.md` to understand the complete brand.yml structure, field options, and syntax.\n\n### Step 3: Build the File Incrementally\n\nStart with the essential sections and add optional elements:\n\n**Minimum viable _brand.yml:**\n\n```yaml\ncolor:\n  palette:\n    brand-blue: \"#0066cc\"\n  primary: brand-blue\n  background: \"#ffffff\"\n\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [400, 600]\n  base: Inter\n```\n\n**Add colors as needed:**\n\n```yaml\ncolor:\n  palette:\n    brand-blue: \"#0066cc\"\n    brand-orange: \"#ff6600\"\n    brand-gray: \"#666666\"\n  primary: brand-blue\n  secondary: brand-gray\n  warning: brand-orange\n  foreground: \"#333333\"\n  background: \"#ffffff\"\n```\n\n**Add typography details:**\n\n```yaml\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [400, 600, 700]\n      style: [normal, italic]\n    - family: Fira Code\n      source: google\n      weight: [400, 500]\n  base:\n    family: Inter\n    size: 16px\n    line-height: 1.5\n  headings:\n    family: Inter\n    weight: 600\n  monospace: Fira Code\n```\n\n**Add logos:**\n\n```yaml\nlogo:\n  small: logos\u002Ficon.png\n  medium: logos\u002Fheader.png\n  large: logos\u002Ffull.svg\n```\n\n**Add meta information:**\n\n```yaml\nmeta:\n  name: Company Name\n  link: https:\u002F\u002Fexample.com\n```\n\n### Step 4: Apply Best Practices\n\nFollow these rules from `references\u002Fbrand-yml-spec.md`:\n\n- All fields are optional - only include what's needed\n- Use hex color format: `\"#0066cc\"`\n- Prefer simple syntax (strings over objects) when possible\n- Use lowercase names with hyphens: `brand-blue`, `success-green`\n- Include `https:\u002F\u002F` in all URLs\n- Define colors\u002Ffonts before referencing them\n- For color ranges (shades\u002Ftints), choose the midpoint color\n\n### Step 5: Validate Structure\n\nCheck that:\n- YAML syntax is valid (proper indentation, quotes on hex colors)\n- Color references match palette names\n- Font families are defined before use\n- File paths are relative to `_brand.yml` location\n- All URLs include protocol (`https:\u002F\u002F`)\n\n## Modifying Existing Files\n\nWhen modifying existing `_brand.yml` files:\n\n1. **Read the current file** to understand existing structure\n2. **Consult brand-yml-spec.md** for valid field options\n3. **Maintain consistency** with existing naming patterns\n4. **Preserve references** - if other colors\u002Felements reference a name, update consistently\n5. **Test integration** - verify changes apply correctly in Shiny\u002FQuarto\n\nCommon modifications:\n- **Adding colors**: Add to `color.palette`, then reference in semantic colors\n- **Changing fonts**: Update in `typography.fonts`, ensure weights\u002Fstyles are available\n- **Adding logo variants**: Use `light`\u002F`dark` structure for multiple variants\n- **Light\u002Fdark mode**: Add `light` and `dark` variants to colors\n\n## Using with Shiny for R\n\nWhen the user wants to apply brand.yml to a Shiny for R app:\n\n1. **Read `references\u002Fshiny-r.md`** for complete integration guide\n2. **Key function**: `bs_theme(brand = TRUE)` or `bs_theme(brand = \"path\")`\n3. **Automatic discovery**: Place `_brand.yml` at app root\n4. **Page functions**: Works with `page_fluid()`, `page_sidebar()`, etc.\n\nQuick example:\n\n```r\nlibrary(shiny)\nlibrary(bslib)\n\nui \u003C- page_fluid(\n  theme = bs_theme(brand = TRUE),\n  # ... UI elements\n)\n```\n\n## Using with Shiny for Python\n\nWhen the user wants to apply brand.yml to a Shiny for Python app:\n\n1. **Read `references\u002Fshiny-python.md`** for complete integration guide\n2. **Key function**: `ui.Theme.from_brand(__file__)`\n3. **Automatic discovery**: Place `_brand.yml` at app root\n4. **Installation**: Requires `pip install \"shiny[theme]\"`\n\nQuick example (Shiny Express):\n\n```python\nfrom shiny.express import ui\n\nui.page_opts(theme=ui.Theme.from_brand(__file__))\n```\n\nQuick example (Shiny Core):\n\n```python\nfrom shiny import App, ui\n\napp_ui = ui.page_fluid(\n    theme=ui.Theme.from_brand(__file__),\n    # ... UI elements\n)\n```\n\n## Using with Quarto\n\nWhen the user wants to apply brand.yml to Quarto documents:\n\n1. **Read `references\u002Fquarto.md`** for complete integration guide\n2. **Automatic discovery**: Place `_brand.yml` at project root with `_quarto.yml`\n3. **Supported formats**: HTML, dashboards, RevealJS, Typst PDFs\n4. **Theme layering**: Use `brand` keyword to control precedence\n\nQuick example (document):\n\n```yaml\n---\ntitle: \"My Document\"\nformat:\n  html:\n    brand: _brand.yml\n---\n```\n\nQuick example (project in `_quarto.yml`):\n\n```yaml\nproject:\n  brand: _brand.yml\n\nformat:\n  html:\n    theme: default\n```\n\n## Troubleshooting\n\n### Brand Not Applying\n\n**Shiny:**\n- Verify file is named `_brand.yml` (with underscore)\n- Check file location (app directory or parent directories)\n- Try explicit path: `bs_theme(brand = \"path\u002Fto\u002F_brand.yml\")` or `ui.Theme.from_brand(\"path\")`\n- For Python: Ensure `libsass` is installed\n\n**Quarto:**\n- Verify `_brand.yml` is at project root\n- Ensure `_quarto.yml` exists for project-level branding\n- Try explicit path in document frontmatter\n- Check theme layering order if using custom themes\n\n### Colors Not Matching\n\n- Ensure hex colors have quotes: `\"#0066cc\"` not `#0066cc`\n- Verify color names match palette definitions exactly\n- Check semantic colors (primary, success, etc.) reference valid palette names\n- Ensure palette is defined before semantic colors\n\n### Fonts Not Loading\n\n- Verify Google Fonts spelling and availability\n- Check internet connection (required for Google Fonts)\n- Ensure `source: google` or `source: bunny` is specified\n- Verify font family names match exactly in typography elements\n- For Typst: Check font cache with `quarto typst fonts`\n\n### YAML Syntax Errors\n\n- Check indentation (use spaces, not tabs)\n- Ensure hex colors have quotes: `\"#447099\"`\n- Verify colons have space after them: `primary: blue`\n- Check list items have hyphens: `- family: Inter`\n- Use YAML validator if syntax issues persist\n\n## Reference Documentation\n\nLoad these as needed for detailed information:\n\n- **`references\u002Fbrand-yml-spec.md`**: Complete brand.yml specification with all sections, fields, examples, and validation rules\n- **`references\u002Fshiny-r.md`**: Using brand.yml with Shiny for R via bslib (bs_theme, automatic discovery, Shiny-specific integration)\n- **`references\u002Fshiny-python.md`**: Using brand.yml with Shiny for Python via ui.Theme (from_brand(), installation, performance)\n- **`references\u002Fquarto.md`**: Using brand.yml with Quarto (formats, light\u002Fdark mode, layering, extensions, Typst)\n- **`references\u002Fbrand-yml-in-r.md`**: General R usage including R Markdown integration, theming functions (ggplot2, gt, flextable, plotly, thematic), and programmatic brand access\n\n## Key Principles\n\n- **Start simple**: Begin with colors and one font family\n- **Keep it concise**: Only include fields directly relevant to the brand\n- **Prefer standard names**: Use Bootstrap color names when possible (blue, green, red, etc.)\n- **Use automatic discovery**: Name file `_brand.yml` for auto-detection\n- **Test across targets**: Verify brand applies correctly in all intended formats\n- **Version control**: Include `_brand.yml` in git repository\n\n## Common Patterns\n\n### Light\u002FDark Mode Colors\n\n```yaml\ncolor:\n  primary:\n    light: \"#0066cc\"\n    dark: \"#3399ff\"\n  background:\n    light: \"#ffffff\"\n    dark: \"#1a1a1a\"\n  foreground:\n    light: \"#333333\"\n    dark: \"#e0e0e0\"\n```\n\nLight\u002Fdark color modes were added in Quarto version 1.8 and currently are not supported in the R or Python brand.yml packages.\n\n### Logo Variants\n\n```yaml\nlogo:\n  images:\n    logo-dark: logos\u002Flogo-dark.svg\n    logo-white: logos\u002Flogo-white.svg\n    icon: logos\u002Ficon.png\n  small: icon\n  medium:\n    light: logo-dark\n    dark: logo-white\n```\n\n### Multiple Font Weights\n\n```yaml\ntypography:\n  fonts:\n    - family: Inter\n      source: google\n      weight: [300, 400, 500, 600, 700]\n      style: [normal, italic]\n  base:\n    family: Inter\n    weight: 400\n  headings:\n    family: Inter\n    weight: 600\n```\n\n### Color Aliases\n\n```yaml\ncolor:\n  palette:\n    navy: \"#003366\"\n    ocean-blue: \"#0066cc\"\n    sky-blue: \"#3399ff\"\n    primary-color: ocean-blue  # Alias\n    brand-blue: ocean-blue     # Alias\n    blue: sky-blue             # Alias for primary colors\n  primary: brand-blue\n```\n\nInclude Bootstrap color names when possible, either defined directly or as aliases: `blue`, `indigo`, `purple`, `pink`, `red`, `orange`, `yellow`, `green`, `teal`, `cyan`, `white`, `black`. This is useful for consistency and these colors are picked up automatically by tools that use brand.yml.\n\n## Tips\n\n- **Read specification first**: Always consult `brand-yml-spec.md` when creating or modifying files\n- **Framework-specific guides**: Load the appropriate reference (shiny-r.md, shiny-python.md, quarto.md) for integration details\n- **Validate incrementally**: Start with minimal structure, test, then add complexity\n- **Use references**: Define colors in palette, then reference by name in semantic colors\n- **Standard file name**: Use `_brand.yml` for automatic discovery\n- **Explicit paths**: Use custom file names only when necessary (shared branding, multiple variants)\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Garrick Aden-Buie (@gadenbuie)","1.1","main","df90fb2d7e33c53913e26681d11b6e309d9b6879","plugins\u002Fr-shiny\u002Fbrand-yml","https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills","https:\u002F\u002Fgithub.com\u002FMichalLauer","https:\u002F\u002Flauer.cz","Data Scientist, Bayesian causality.","2026-11-06 20:11:05",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add MichalLauer\u002Fskills --skill brand-yml",{"tool":41,"command":42},"bunx","bunx skills add MichalLauer\u002Fskills --skill brand-yml",{"tool":44,"command":45},"pnpm","pnpm dlx skills add MichalLauer\u002Fskills --skill brand-yml","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fbrand-yml-in-r.md","REFERENCE","参考文档",9754,"https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002Freferences\u002Fbrand-yml-in-r.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fbrand-yml-spec.md",9652,"https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002Freferences\u002Fbrand-yml-spec.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fquarto.md",8844,"https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002Freferences\u002Fquarto.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fshiny-python.md",7929,"https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002Freferences\u002Fshiny-python.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fshiny-r.md",7928,"https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fbrand-yml\u002Freferences\u002Fshiny-r.md",[72,79,86],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DCVG6WPTMDVB6XW0S6G973","shiny-for-r","Building, styling, testing, debugging, or observing a Shiny for R app - library(shiny), shinyApp(), runApp(). Index skill: read this, then open the linked reference for the task. Covers reactivity (reactive\u002Fobserve\u002Freq\u002Fisolate\u002FbindEvent); modules; async promises and ExtendedTask; bslib layouts, navigation, cards, value boxes, and theming (incl. thematic and brand.yml); dynamic UI; plots with click\u002Fbrush interaction; tables, file upload\u002Fdownload; notifications, modals, progress, validation; bookmarking; custom JS components; testServer testing; debugging; OpenTelemetry; and when to reach for DT, plotly, leaflet, shinychat, or shinytest2. Use when writing or changing any Shiny for R app, especially a dashboard, or when tempted to hand-roll what the framework provides - custom HTML tables, fake tabs, polling loops, blocking reactive work, or print-debugging server state.","https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fshiny-for-r\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DCV92JJ2KW3MAQA5VKK8Y6","shiny-bslib","Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow\u002Fcolumn, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming, accordions, tooltips, popovers, toasts, or bslib inputs. Assumes familiarity with basic Shiny.","https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fshiny-bslib\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DCV2FVF4JYG9NA7A1NMQHH","shiny-bslib-theming","Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bs_theme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass\u002FCSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection, or making R plots match the app theme with thematic.","https:\u002F\u002Fgithub.com\u002FMichalLauer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fr-shiny\u002Fshiny-bslib-theming\u002FSKILL.md",[],[]]