applying-bitwarden-branding

작성자: bitwarden

Bitwarden 브랜드 표준 적용 — 로고 사용법, 색상 팔레트, 타이포그래피, 아이콘 및 대문자 표기 규칙 — bitwarden.com/brand 및…에 기반

npx skills add https://github.com/bitwarden/ai-plugins --skill applying-bitwarden-branding

Applying Bitwarden Branding

This skill grounds brand-application decisions in Bitwarden's two canonical sources:

  • bitwarden.com/brand — the brand guidelines hub, including logo lockups, the radius system, social-post framing, product images, and B-roll.
  • github.com/bitwarden/brand — the source-of-truth repository for SVG logos, PNG product icons (multiple sizes), the shield mark, color palette in multiple formats (HEX, HSL, SCSS), screenshots, and media assets.

When applying brand in real work, treat the repo as canonical for assets and the brand site as canonical for usage rules. Detailed reference material lives in references/brand-assets.md (asset inventory and file paths) and references/color-palette.md (full palette with usage notes and SCSS variable names).

The five rules that catch the most mistakes

  1. Capitalize the B in Bitwarden. Always. The W is never capitalized. The only place "bitwarden" appears lowercase is inside the official logo lockup — not in body copy, not in headlines, not in handles or URLs.
  2. Primary palette before tertiary palette. Green, Yellow, and Red are tertiary — use them sparingly, primarily in product graphics and for success / warning / error communications. They are not headline colors.
  3. Inter for everything. Product and website. The available weights are 300 (light), 400 (regular), 500 (medium), 600 (semi-bold), and 700 (bold).
  4. Logo safe-area is non-negotiable. Horizontal lockup needs one Bitwarden-shield width of clear space on every side. Vertical lockup uses the height of the "X" in the logotype. Cramped logos break the lockup.
  5. 36px radius system, but buttons are the exception. Rounded corners follow a 36px radius across primary brand surfaces. Buttons sit outside that system — don't apply 36px to buttons.

Logo usage

  • Default mark. /logos/logo-horizontal-blue.svg from the brand repo. Horizontal is the primary/preferred lockup.
  • Inverse (for dark backgrounds). /logos/logo-horizontal-white.svg.
  • Vertical lockup. Available for use cases where horizontal doesn't fit; the safe area uses the height of the "X" in the logotype.
  • Product icon (the shield). Available rounded and square, at 16/32/64/128/256 px PNG plus SVG (/logos/icon.svg, /logos/icon-inverse.svg, /icons/*.png). The shield itself lives at /shield/.
  • Product logos. Unique lockups exist for individual Bitwarden products (Password Manager, Secrets Manager, etc.). Use these "primarily for use in-product."

Don't recolor, distort, rotate, or recompose the logo. If the supplied SVG doesn't fit the need, reach out to the brand owners rather than improvising a variant.

Color palette quick reference

Full palette with all variable names is in references/color-palette.md. Five colors carry most of the work:

ColorHEXUse
Bitwarden Blue#175DDCPrimary brand color. Headlines, primary CTAs, accents.
Deep Blue#0C3276Secondary brand color. Dense surfaces, headers.
Off White#F3F6F9Default light surface.
True Black#000000Default text on light surfaces.
Teal Highlight#2CDDE9Accent and highlight — pair with the blues.

Tertiary palette (Green #7BF1A8, Yellow #FDC700, Red #FF6550) is sparingly applied for product graphics and success/warning/error states. The brand site is explicit on this.

SCSS variable names (from the brand repo's brand-colors/palette.scss):

  • $bitwarden-blue, $deep-blue, $off-white, $true-white, $true-black, $light-grey, $teal-highlight, $light-teal-highlight, $tertiary-green, $tertiary-yellow, $tertiary-red.

Typography

  • Typeface: Inter (open-source, Google Fonts).
  • Weights available: 300 (light), 400 (regular), 500 (medium), 600 (semi-bold), 700 (bold).
  • Use: product UI and website body / headline copy. The brand site doesn't enumerate weight-per-context rules; defer to product or marketing leads when an unusual case comes up.

Iconography

  • Web icons. Designed for a wide range of uses with more detail than the product icon.
  • Product icon (shield). Available rounded and square at multiple sizes from the brand repo's /icons/ directory.

Asset paths and full sizing tables are in references/brand-assets.md.

Capitalization and trademark

  • The "B" in Bitwarden is capitalized in all copy text.
  • The "W" is never capitalized — neither BITWARDEN (in body copy) nor bitWarden.
  • The only place "bitwarden" appears in lowercase is inside the official logo lockup itself.
  • "Bitwarden" is a registered trademark of Bitwarden Inc. — surface this when content is external-facing and trademark attribution is appropriate.

Composing with other skills

  • content-style-guide. Brand sits alongside content style. When reviewing user-visible surfaces, walk both: this skill catches color, logo, and capitalization issues; the content style guide catches voice, tone, sentence case, and accessibility.
  • using-figma. Use get_variable_defs to check whether a design's colors are library-bound and aligned to the brand palette; use get_libraries to confirm the right design library is loaded before claiming a design is on-brand.
  • preparing-design-handoff. Surface brand findings as part of the handoff gate — flag them as Figma annotations or as open questions in the Epic when something is off-brand at handoff time. Don't quietly fix.
  • evolving-design-system-components. New patterns must respect the brand palette and the 36px radius system (with the button exception). The Component Library governance review catches obvious violations, but raise them explicitly when sponsoring a pattern.

Output format for brand checks

When asked "is this on-brand?", structure the response as:

  1. What's checked — which brand surfaces this design touches (logo, color, typography, iconography, capitalization).
  2. What's on-brand — what's working and should stay.
  3. What's off-brand — each finding tied to the specific brand rule it violates (cite the section, e.g., "Tertiary palette overused — Green appears in three non-state surfaces, per the bitwarden.com/brand tertiary-usage rule").
  4. Proposed corrections — concrete swaps the designer can apply, sourced from the canonical palette or asset.

Keep findings specific. "The headline uses #7BF1A8 (tertiary green) where Bitwarden Blue (#175DDC) is the brand-primary color" beats "the color is wrong."

Additional resources

  • references/brand-assets.md — full inventory of brand repo assets with file paths (logos, icons, shield, screenshots, media assets).
  • references/color-palette.md — full palette with HEX, HSL, SCSS variable names, and per-color usage notes.

bitwarden의 다른 스킬

figma-to-angular
bitwarden
이 스킬은 Figma 디자인 스펙을 Bitwarden Clients 모노레포 내에서 Storybook 스토리와 함께 완전히 구현된 Angular 컴포넌트로 변환합니다. 출력물은 모든 코드베이스 규칙을 따르면서 시각적으로 디자인과 일치해야 합니다.
force-multiplier
bitwarden
하나의 의도를 여러 대상에 동시에 적용합니다 — Bitwarden 생태계 전반의 저장소 플릿, 또는 모노레포 내 많은 프로젝트 — N개의 일관된 작업으로, …
analyzing-git-sessions
bitwarden
특정 기간이나 커밋 범위 내의 Git 커밋과 변경 사항을 분석하여 코드 리뷰, 회고, 작업 로그 또는 세션을 위한 구조화된 요약을 제공합니다.
coordinating-cross-team-breakdown
bitwarden
크로스 팀 리뷰 및 Bitwarden 기술 분석에 대한 승인을 조정합니다. 영향을 받는 팀을 식별하고, 파트 3 승인 테이블을 작성하며, 후속 조치를 진행할 때 사용하세요.
assessing-jira-issue-relevance
bitwarden
사용자가 개별 Jira 이슈 키를 제공하고 그것이 여전히 관련이 있는지, 여전히 적용 가능한지, 여전히 보류 중인지, 여전히 버그인지, 수정되었는지, 또는 …인지 물을 때 사용합니다.
assessing-test-coverage
bitwarden
특정 변경(PR, Jira 키, Tech Breakdown 문서, Testmo CSV, 변경된 경로 또는 명명된 항목)에 대해 이미 존재하는 테스트 커버리지를 파악할 때 사용합니다.
retrospecting
bitwarden
Claude Code 세션에 대한 포괄적인 분석을 수행하며, git 히스토리, 대화 로그, 코드 변경 사항을 검토하고 사용자 피드백을 수집하여 생성합니다…
reviewing-incremental-changes
bitwarden
이미 코멘트가 달린 PR을 재검토하거나 초기 리뷰 후 개발자의 변경 사항에 응답할 때 이 스킬을 사용하세요. PR 스레드가 존재하거나...