スキル一覧に戻る

brand-identity

rampstackco
更新日 2 days ago
3 閲覧
239
27
239
GitHubで表示
その他worddesign

について

このスキルは、ロゴ、カラー、タイポグラフィ、イメージを含む完全なブランドのビジュアル・アイデンティティ・システムのデザインや評価を支援します。ユーザーがこれらの視覚的要素を作成する必要がある場合や、既存のシステムの一貫性を評価する際に発動します。カラーパレットの構築、タイポグラフィの選択、ロゴシステムの開発などのタスクにご利用ください。

クイックインストール

Claude Code

推奨
メイン
npx skills add rampstackco/claude-skills -a claude-code
プラグインコマンド代替
/plugin add https://github.com/rampstackco/claude-skills
Git クローン代替
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/brand-identity

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

Brand Identity

Design or evaluate the visual artifacts that express a brand: logo system, color, typography, imagery, iconography, and motion. Stack-agnostic. Tool-agnostic.

This skill assumes a brand direction is already approved (positioning, mood, name). If not, run brand-ideation first.


When to use

  • Designing a logo system
  • Defining a brand color palette
  • Choosing brand typography
  • Developing iconography or illustration style
  • Defining imagery direction (photography, illustration)
  • Establishing motion principles
  • Auditing an existing identity for cohesion or gaps

When NOT to use

  • Brand direction is not yet defined (use brand-ideation)
  • Documenting a finished system (use brand-style-guide)
  • Defining voice and tone (use brand-voice)
  • Building UI components from an existing brand (use design-standards or design-system)

Required inputs

  • The brand name and approved positioning
  • The mood direction (from ideation, or supplied as references)
  • Audience and category context
  • Application contexts (web, print, packaging, motion - whatever applies)
  • Constraints (parent brand requirements, regulatory marks, accessibility minimums)

The framework: 5 elements

A complete identity has five elements. Each element should reinforce the others. Inconsistency between them is the most common identity failure.

1. Logo system

Most brands need not one logo but a system of marks for different contexts.

Components of a logo system:

  • Primary mark. The main logo. Used wherever there is room.
  • Wordmark. Just the typography, no symbol. Used in tight horizontal contexts.
  • Symbol or glyph. Just the symbol, no type. Used in app icons, favicons, social avatars.
  • Lockup variations. Horizontal, stacked, square - whichever apply.
  • Monogram. The initial(s) styled as a mark. Optional but useful for small contexts.

Design principles:

  • Legible at 16 pixels. Test the logo at favicon size. If it falls apart, redesign.
  • Reproducible in single-color. If the logo only works in full color, it cannot be screen-printed, embroidered, or rendered in browser favicons.
  • Distinctive silhouette. Squint at it. Can you still tell what it is? If it looks like every other logo in the category at silhouette, redesign.
  • Construction grid. Every curve and angle is intentional. Document the construction.

Common failure:

  • Designing only the primary mark and discovering at launch that the wordmark, glyph, and small-size variants do not exist.

2. Color system

A color system is more than a palette. It is the rules for how color carries meaning.

Components:

  • Primary color. The signature color most associated with the brand.
  • Secondary colors. 1 to 3 supporting colors that extend the palette.
  • Neutrals. The grays and tints that make up most of the surface area.
  • Semantic colors. Success, warning, error, info - if the brand operates in product UI.
  • Accent colors. Used sparingly for highlight and emphasis.

Per color, document:

  • Hex, RGB, HSL, CMYK (if print is in scope), and Pantone (if brand-critical print exists)
  • WCAG AA contrast against the other colors in the system
  • Allowed and disallowed pairings (some brand colors look terrible together)
  • Usage notes (when to use, when not to use)

Design principles:

  • Test for accessibility. WCAG AA requires 4.5:1 contrast for normal text, 3:1 for large text. If the brand color cannot pass either against white, you have a problem.
  • Test for color blindness. Around 8 percent of men have some form of color blindness. Critical UI signals should not rely on color alone.
  • Define neutrals carefully. Neutrals are 80 percent of the surface area in most brand applications. They carry more weight than the brand color.
  • Limit the palette. A 30-color palette is unmanageable. 5 to 8 carefully chosen colors beats a sprawling system.

3. Typography

Type is the second-most-recognizable element of a brand after the logo.

Components of a type system:

  • Display typeface. For headlines and brand moments.
  • Body typeface. For long-form reading. Often the same as display, sometimes different.
  • Monospace typeface (if applicable for technical brands).
  • Type scale. The set of sizes used across applications. Typically 5 to 8 steps.
  • Type weights and styles. Which weights and italics are part of the system.

Design principles:

  • Pairing. If using two typefaces, they must work together at body and display sizes. Common pattern: serif display + sans body, or geometric sans display + humanist sans body.
  • Web licensing. Confirm web licensing covers expected pageviews. Some popular typefaces have prohibitive web licenses.
  • Variable fonts are increasingly the right call for performance and flexibility.
  • Fallback stack. Specify system fallbacks for when the brand font fails to load. The fallback should be visually similar.
  • Open-source alternatives. Document open-source equivalents for situations where licensing is impractical (third-party tools, embedded contexts).

4. Imagery and illustration

Imagery direction is often underspecified, leading to brand drift over time.

Photography direction:

  • Subject matter. What does the brand show?
  • Composition style. Tight crops, wide environments, candid, posed?
  • Lighting. Bright and natural, dramatic and directional, soft and diffused?
  • Color treatment. True color, warm shifted, desaturated, high-contrast?
  • What to reject. Stock photo aesthetics, specific cliches in the category.

Illustration direction:

  • Style. Flat, dimensional, hand-drawn, geometric, abstract, representational?
  • Color use. Full palette, restricted palette, brand colors only?
  • Line treatment. Bold and outlined, soft and shaded, no outlines?
  • Subject matter. What gets illustrated and what does not?

Iconography:

  • Style. Filled or outline. Rounded or sharp. Single weight or variable.
  • Grid. Pixel-perfect grid (often 24x24 or 16x16 base).
  • Stroke weight. Consistent across the icon set.
  • Set. Which icons exist, and how new icons get added consistently.

5. Motion

If the brand lives in any digital product, marketing video, or animated touchpoint, motion is part of the identity.

Motion principles to define:

  • Easing curves. Default easings used across animations. Linear, ease-in-out, custom.
  • Duration scale. Fast (100ms), medium (200-300ms), slow (500ms+) and when each applies.
  • Choreography. How elements enter, exit, and respond to interaction.
  • Brand moments. Signature animations (logo build, page transitions, loaders).

Design principles:

  • Restraint. Most motion in product UI should be quick and subtle. Reserve dramatic motion for brand moments.
  • Reduced motion. Always provide a prefers-reduced-motion alternative for users with vestibular sensitivities.
  • Performance. Animations must be 60fps on the target devices. Profile before shipping.

Workflow

  1. Confirm brand direction. Positioning, mood, audience. If unclear, return to brand-ideation.
  2. Audit applications. List every place the brand will appear (web, print, packaging, app, social, signage, video). The application contexts drive what the system needs to handle.
  3. Element-by-element design. Start with logo and color, since these constrain typography. Then type. Then imagery, iconography, motion.
  4. Stress-test. Apply the system to 3 to 5 mock applications (homepage, social post, business card, product UI, signage). Where does it break? Iterate.
  5. Document. Each element with rules, examples, and dos/don'ts. This becomes the input to brand-style-guide.
  6. Get sign-off before broad rollout. Identity changes after rollout are 10x the cost of changes during design.

Failure patterns

  • Designing logos in isolation from application. A logo that looks great on a hi-res mockup but illegible at favicon size is a design failure.
  • Picking a brand color without contrast testing. A brand color that fails WCAG AA against white means UI built on the brand will be inaccessible by default.
  • Specifying typography without checking web licensing. Discovering at deploy that the foundry charges per-pageview for the chosen typeface is a budget-buster.
  • Skipping imagery direction. Without it, the brand becomes whatever stock photos the next person picks.
  • Treating motion as decoration. Inconsistent motion erodes brand cohesion as fast as inconsistent color.
  • Designing only primary states. What does the brand look like in error? In dark mode? In a localization where the wordmark needs to flip direction? These are not edge cases; they are the brand.

Output format

Default output is a structured set of files:

  • identity/logo/ - All logo variants (SVG primary, plus PNG/JPG exports at common sizes)
  • identity/colors.md - Color system with hex codes, contrast ratios, usage rules
  • identity/typography.md - Type system with scale, weights, fallbacks
  • identity/imagery.md - Imagery direction with reference examples
  • identity/iconography/ - Icon set or icon style spec
  • identity/motion.md - Motion principles
  • identity/applications/ - 3 to 5 application mockups stress-testing the system

These feed directly into brand-style-guide.


Reference files

GitHub リポジトリ

rampstackco/claude-skills
パス: skills/brand-identity
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code

関連スキル

brand-style-guide

その他

このClaudeスキルは、開発者が包括的なブランドスタイルガイドの作成や監査を支援し、ロゴ、カラー、タイポグラフィ、トーンボイスを含む完全なシステムを文書化します。ブランドブックの構築が必要な時、既存ガイドラインの監査を行う時、または引き継ぎ用の永続的な参照資料を作成する際に起動します。チームや外部ベンダー間で一貫したブランド適用を保証する規範文書を生成するためにご利用ください。

スキルを見る

brand-voice

その他

ブランドボイススキルは、開発者がブランドの完全な文章パーソナリティ(声の特性、トーンの変化、語彙ルールを含む)を定義し、文書化するのに役立ちます。ガイドラインの作成、コピーの監査、またはAIへのブランドボイスのトレーニング時に起動されます。ユーザーがブランドの文章表現を確立、洗練、または徹底させる必要がある際にご利用ください。

スキルを見る

brand-ideation

その他

このスキルは、ブランド開発における初期段階の創造的プロセスを支援し、名前、ポジショニング、ムードの方向性などのコンセプトを生成・洗練する手助けをします。初期探索、ブレインストーミング、あるいは複数の未完成なアイデアを一貫した方向性に収束させる際に起動されます。開発者は、ブランド命名、ポジショニング領域の設定、ナラティブな視点の構築に関連するタスクを支援するために、このスキルを活用すべきです。

スキルを見る

logo-design

その他

`logo-design`スキルは、ワードマークやシンボルなど複数のアーキテクチャにわたって、実用に耐えるロゴのバリエーションを生成し、詳細な理論的根拠と技術仕様を提供します。このスキルは特に、タイポグラフィの選定や、ファビコンや看板などの用途を想定した適用テストを含む、ロゴの詳細な実行に焦点を当てています。専用のロゴプロジェクトにはこのスキルを使用し、完全なアイデンティティシステムが必要な場合は`brand-identity`に切り替えてください。

スキルを見る