agentleFS
GreatFigure8GreatFigure8/Claude-Skills/Skills/digikey-brand-guidelines/SKILL.md

digikey-brand-guidelines

Skill0 starsChanged 4 months agoUnlicenseView on GitHub

Applies DigiKey's official brand colors, typography, logo, and visual design standards to any generated output — including HTML/React artifacts, Microsoft Word documents, PowerPoint decks, Excel workbooks, PDFs, dashboards, charts, one-pagers, and styled documents. Use this skill whenever the user asks for DigiKey branding, DigiKey-themed materials, DigiKey-styled documents, client-facing DigiKey deliverables, or mentions "DigiKey colors", "DigiKey logo", "DigiKey report", "DigiKey presentation", "DigiKey dashboard", or anything that should look like it came from DigiKey. Also trigger when the user works on DigiKey-related projects (such as the Remittance App, Oracle Fusion integration work, or any internal DigiKey tooling) and asks for a polished or branded output, even if they don't explicitly say "branding".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When generating output, apply this skill automatically.

    line 14
  2. Distinctive:

    One red CTA per view: Use the outlined secondary style for everything else.

    line 150
  3. Very specific:

    Before generating a branded output, view the relevant reference file in references/ to get the detailed rules for that format.

    line 179
  4. Very specific:

    Read the appropriate references/*-guide.md file.

    line 203
  5. Very specific:

    If generating code that needs the Python or CSS tokens, copy assets/digikey_brand.py or assets/digikey-theme.css into the working directory …

    line 204
  6. Very specific:

    Read the matching core skill (/mnt/skills/public/docx/SKILL.md, pptx/SKILL.md, xlsx/SKILL.md) for format-specific mechanics.

    line 207
  7. Distinctive:

    Do:: use precise technical language when the audience is technical.

    line 221

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DigiKey Brand Design System

Applies DigiKey's post-2023 ("We Get Technical") visual identity to any output. The palette is tight and confident: Pomegranate red is the hero, Mine Shaft charcoal carries the type, and white carries the space. Use red as a spice, not a base — it belongs on the logo, the primary CTA, accent rules, and deliberate emphasis.

When generating output, apply this skill automatically. Do not ask the user to confirm brand choices — they already asked for DigiKey branding, so use these values.


1. Color palette

Core brand colors (verified from DigiKey's 2023 refresh)

TokenHexRGBNameUse
--dk-red#EE2821238, 40, 33PomegranatePrimary brand color, logo, CTAs, accent
--dk-white#FFFFFF255, 255, 255WhitePrimary surface
--dk-charcoal#33333351, 51, 51Mine ShaftBody text, headings, strong neutral

Derived reds (for states and subtle fills)

TokenHexUse
--dk-red-dark#C31D17Hover / pressed state
--dk-red-darker#8F1511Deep accent, chart 5th series
--dk-red-tint-10#FDE9E8Very light red wash for callouts
--dk-red-tint-25#F9B8B5Light red for stacked fills

Supporting neutrals

TokenHexUse
--dk-black#000000Maximum contrast
--dk-near-black#1A1A1ADeep headers
--dk-dark-gray#4A4A4ASecondary headings
--dk-gray#6C6C6CSecondary / caption text
--dk-medium-gray#9A9A9ATertiary text, muted labels
--dk-light-gray#D1D1D1Borders, chart gridlines
--dk-lighter-gray#E8E8E8Subtle dividers
--dk-soft-gray#F4F4F4Card / section backgrounds
--dk-off-white#FAFAFAZebra rows, subtle fills

Status colors (use sparingly — red is reserved for brand)

TokenHexUse
--dk-success#2E7D32Positive variance
--dk-warning#F5A623Caution thresholds
--dk-info#0B6FB4Neutral info
--dk-error#EE2821Same as brand red

Chart palette (use in this order)

  1. #EE2821 (DK_RED) — first series is always brand red
  2. #333333 (DK_CHARCOAL) — strong neutral
  3. #9A9A9A (DK_MEDIUM_GRAY)
  4. #0B6FB4 (DK_INFO) — when hue separation is needed
  5. #8F1511 (DK_RED_DARKER)
  6. #6C6C6C (DK_GRAY)
  7. #F9B8B5 (DK_RED_TINT_25)
  8. #D1D1D1 (DK_LIGHT_GRAY)

2. Typography

DigiKey's 2023+ identity uses a custom commercial sans-serif. For reproducible output use Inter (free, Google Fonts) with Arial as a universal fallback. The feel is clean, slightly geometric, engineered.

  • Primary typeface: Inter
  • Web fallback: Arial, Helvetica, sans-serif
  • Monospace (for part numbers, code, data): Roboto Mono, Consolas, Menlo

Google Fonts import:

<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Roboto+Mono:wght@400;500&display=swap" rel="stylesheet">

Type scale (web, rem-based)

RoleSizeWeightUsage
Display3.5rem800 BlackHero titles
H12.5rem800Page titles (often DK_RED)
H22rem700 BoldSection headings
H31.5rem700Subsection headings
H41.25rem600 SemiboldMinor headings
Body1rem400 RegularParagraphs
Small0.875rem400Meta, labels
Caption0.75rem400Footnotes, legal

Type scale (Office docs, points)

RoleSizeWeight
Display44ptBlack
H128ptBold
H222ptBold
H316ptSemibold
H414ptSemibold
Body11ptRegular
Small10ptRegular
Caption9ptRegular

Important: letter-spacing of -0.02em on display/H1 tightens the wordmark-adjacent feel. Body text uses normal letter-spacing and a 1.55 line-height for readability.


3. Logo

  • Wordmark: lowercase "digikey" in Pomegranate red on white, or white on Pomegranate red / charcoal.
  • Tagline (paired with logo): "We Get Technical"
  • Clear space: at least 1× the cap-height of "digikey" on all four sides.
  • Minimum size: 80px wide on screen, 0.75" in print.
  • Never: stretch, skew, recolor (other than the approved white-on-dark reversal), add drop shadows, or place on a background that clashes with Pomegranate red.
  • Placeholder assets live in assets/:
    • digikey-logo-placeholder.svg — red wordmark on transparent
    • digikey-logo-white-placeholder.svg — white wordmark on transparent

For client-facing, public, or press deliverables, replace the placeholder with DigiKey's official asset. Tell the user this once when they first ask for a branded output, then stop nagging.


4. Visual style principles

  • Red is a spice. The signature red belongs on the logo, the primary CTA, a top banner, an accent rule beneath a heading, hover states, and deliberate emphasis. Keep large surfaces white or soft gray. Never paint every heading or every button red.
  • One red CTA per view. Use the outlined secondary style for everything else.
  • Clean, engineered, calm. Generous white space. Left-align most text. Center only for hero titles and stat callouts.
  • Sharp geometry over soft curves. Border-radius stays modest (4–8px for buttons and cards, 12px max for containers). No pill shapes except for tags.
  • No gratuitous gradients. Flat color is the default. A subtle dark-red gradient on hero sections is acceptable; rainbow or trendy gradients are not.
  • Photography & imagery: clean product shots on neutral backgrounds; real engineers and makers at work; circuit-board textures for abstract backgrounds. Avoid generic stock imagery.

Signature DigiKey layout patterns

  1. Red top banner — 0.3" tall, full-bleed #EE2821 strip at the top of slides, report covers, and email headers.
  2. Red accent rule — a short 3pt red horizontal line beneath a title, acts as the brand's visual fingerprint.
  3. Stat callout — big DK_RED or DK_CHARCOAL number in Inter Black with a thin red underline and a small DK_GRAY label.
  4. Zebra tables — white / #FAFAFA alternating rows with a solid red header row.

5. How to use this skill — by output type

Before generating a branded output, view the relevant reference file in references/ to get the detailed rules for that format.

User wantsRead this reference
HTML artifact, React, dashboardreferences/html-artifact-guide.md
Word .docx report, memo, letterreferences/word-docx-guide.md
PowerPoint .pptx deckreferences/powerpoint-pptx-guide.md
Excel .xlsx workbook, datareferences/excel-xlsx-guide.md

Reusable assets in assets/

  • digikey-theme.css — drop-in CSS variables + component classes for HTML/React artifacts. Paste inline in a <style> tag.
  • digikey_brand.py — Python constants and helper functions for python-docx, python-pptx, openpyxl, and matplotlib. Copy to your working directory and import.
  • digikey-logo-placeholder.svg — red wordmark placeholder.
  • digikey-logo-white-placeholder.svg — white wordmark placeholder.

Standard workflow

  1. User asks for a DigiKey-branded output (e.g. "make me a DigiKey quarterly report in Word").
  2. Read the appropriate references/*-guide.md file.
  3. If generating code that needs the Python or CSS tokens, copy assets/digikey_brand.py or assets/digikey-theme.css into the working directory first (or inline the relevant values).
  4. Read the matching core skill (/mnt/skills/public/docx/SKILL.md, pptx/SKILL.md, xlsx/SKILL.md) for format-specific mechanics.
  5. Generate the output, placing the final file in /mnt/user-data/outputs/.
  6. Present the file with the present_files tool.

6. Voice & tone (for copy generated in branded materials)

DigiKey's voice is the "Eye-Level Expert" — humble confidence, friendly, attentive, straight-shooting. Highly technical subject matter delivered without condescension.

  • Do: use precise technical language when the audience is technical; use clear plain English when it's not; be direct; celebrate the community of engineers and makers.
  • Don't: hype, overpromise, use corporate buzzwords, or condescend to the reader.
  • Tagline to use in hero contexts: "We Get Technical."
  • Footer copyright: © {year} DigiKey. All Rights Reserved.

7. Quick reference card

Copy-paste-ready tokens for any context:

Primary red:     #EE2821   rgb(238, 40, 33)
Body charcoal:   #333333   rgb(51, 51, 51)
Surface white:   #FFFFFF   rgb(255, 255, 255)
Hover red:       #C31D17
Card fill:       #F4F4F4
Border:          #D1D1D1
Caption gray:    #6C6C6C

Font:            Inter, Arial, sans-serif
Mono:            Roboto Mono, Consolas, monospace
Tagline:         "We Get Technical"
Radius:          4px (btn) / 8px (card) / 12px (hero)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.