Token导航 LogoToken导航TokenDH.com
前端设计权限需确认github未标认证来源可访问许可证需确认审计通过

brand-visual-language品牌视觉语言

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

720

周安装

30

GitHub Stars

6

下载量

240
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:brand-visual-language(品牌视觉语言)
来源仓库:https://github.com/dembrandt/dembrandt-skills
仓库路径:skills/brand-visual-language
安装命令:
npx skills add https://github.com/dembrandt/dembrandt-skills --skill brand-visual-language
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/dembrandt/dembrandt-skills --skill brand-visual-language

简介

brand-visual-language 通过形状语言传递品牌个性,如圆角代表友好,直角体现专业。

  • 适用于指导图标、按钮与排版设计,强化视觉一致性与情感连接。
  • 提供不同 tone 对应的 shape 推荐值(如 2–4px 轻圆角用于企业级工具)。
  • 使用时应结合具体产品类型选择形状策略,避免盲目套用造成认知混乱。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Brand Visual Language

Visual shape communicates personality. A rounded corner says something different to the user than a sharp one — and that message arrives before they read a single word. The shapes in typography, border-radius, and iconography should tell a consistent story.

Shape Language

ShapeToneAssociated with
Rounded, pill-shapedFriendly, approachable, playful, modernConsumer apps, health, kids, lifestyle, social
Softly rounded (8–12px)Professional, warm, accessibleSaaS, productivity, general B2B
Lightly rounded (2–4px)Precise, structured, efficientEnterprise tools, finance, data platforms
Sharp / no radiusTechnical, serious, authoritativeDeveloper tools, security, industrial

Every component — cards, inputs, modals, badges — should follow the same radius logic.

Radius for Large Surfaces

The perceived "roundedness" of an element changes with its scale. A radius that looks soft on a button may look sharp on a large container.

  • Large Cards & Modals: Typically use a larger radius than buttons (e.g., if buttons are 4px, large cards might be 8px or 12px) to maintain a consistent visual tone.
  • Wells and Background Sections: For large background areas or "wells," a smaller radius (2px–8px) is often used to provide structure and define the region without making it feel like a "floating" component. This keeps the focus on the content within, rather than the container itself.

Reading Shape from an Existing Brand

Before choosing a radius, look at the brand's existing materials:

  • Logo: Is it rounded, geometric, or angular? The logo's shapes are intentional brand decisions.
  • Product photography or illustration style: Rounded, bubbly illustrations signal a different personality than sharp, technical diagrams.
  • Typography: A geometric sans-serif (Circular, Futura) reads differently than a humanist sans (Inter, Söhne) or a sharp editorial serif.
  • Competitor landscape: Sometimes being the slightly softer option in a sharp market, or the more structured option in a playful market, is the differentiator.

Typography and Shape

Typeface shapes carry the same tonal signals:

Type styleTone
Geometric sans (circular letterforms)Modern, clean, slightly playful
Humanist sans (varied stroke widths)Warm, readable, professional
Grotesque sans (neutral, utilitarian)Serious, efficient, no-frills
SerifAuthoritative, established, editorial
Rounded sansFriendly, approachable, informal
MonospaceTechnical, developer-facing, precise

The typeface and the border-radius should not contradict each other. A rounded, friendly typeface paired with sharp 0px corners creates visual dissonance.

Extending Brand Typography

Brand books often specify a display or heading font but leave body text underdefined — a single weight, no reading size, no fallback. This is common with luxury, fashion, or legacy brands where the brand identity was built for print, not screen.

When the brand book is insufficient for UI purposes, extend it deliberately:

When extension is justified:

  • Brand font has poor legibility at small sizes (display fonts, decorative typefaces)
  • Brand font lacks the weights needed for UI hierarchy (no regular, no medium)
  • Brand font has no body or reading variant defined
  • Brand font loads poorly (performance, licensing, web rendering)

How to extend:

  • Keep the brand font for headings and display — this is where brand identity lives
  • Add a secondary typeface for body text that is complementary in tone, not competing
  • Match shape language: a geometric brand font pairs with a geometric body font; a humanist display pairs with a humanist body
Brand heading font (display, h1–h3): maintains identity
↓
Secondary body font (body, labels, UI copy): legibility and completeness

Pairing principles:

  • Contrast in role, not in personality — the two fonts should feel like they belong to the same product
  • Avoid two display fonts or two highly characterful fonts together
  • A neutral, high-quality sans (Inter, DM Sans, Söhne) pairs safely with most brand fonts
  • If the brand font is a serif, a clean sans body is the natural complement — and vice versa

Do this sparingly. Two typefaces is a deliberate extension. Three typefaces is almost always too many. Document the decision and the rationale so future designers do not add a third.

Iconography

Icon style must match the brand's shape language. Mixing icon styles — some thin, some bold, some filled, some outlined — breaks visual cohesion even when individual icons are correct.

Icon styleToneUse when
Thin / outline (1–1.5px stroke)Minimal, elegant, refinedLuxury, editorial, premium SaaS
Regular outline (2px stroke)Balanced, professionalGeneral SaaS, productivity tools
Bold / thick (2.5–3px stroke)Strong, clear, accessibleConsumer apps, mobile-first, accessibility focus
FilledSolid, confident, clear at small sizesDashboard indicators, status icons, mobile nav
Rounded corners on icon pathsFriendly, approachableConsumer, lifestyle, health
Sharp corners on icon pathsTechnical, preciseDeveloper tools, finance, data

Rule: Use one icon library and one weight throughout. If mixing is unavoidable (e.g. a specialised icon not available in the chosen library), match stroke width and corner style manually.

Consistency Across Elements

All shape-bearing elements should follow the same visual logic:

ElementApplies shape language via
Buttons--radius-button
Cards--radius-card (same or slightly larger than button)
Inputs--radius-input (typically same as button)
Badges / tagsCan be more rounded than buttons — pill shape is common
Modals / drawers--radius-modal (often larger, 12–16px)
AvatarsAlways fully round (--radius-full)
IconsStroke weight and corner style match brand
IllustrationsShape style consistent with icon style

Review Checklist

  • Does the border-radius token match the brand's shape language (logo, illustrations, photography)?
  • Is the same radius logic applied to buttons, inputs, and cards?
  • Does the typeface tone match the overall brand personality?
  • Is a single icon library used consistently throughout?
  • Do icons match the brand in stroke weight (thin for refined, bold for accessible)?
  • Are rounded icon corners used for friendly brands and sharp corners for technical brands?
  • Is the border-radius adjusted for surface size (e.g., larger for modals, tighter 2-8px for wells/backgrounds)?
  • Is there no visual contradiction between typeface style and shape choices (e.g. rounded type + sharp cards)?

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.51%
按下载量换算80

Claude

27.84%
按下载量换算67

Cursor

20.41%
按下载量换算49

Gemini CLI

9.09%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills