Token导航 LogoToken导航

Agent Skill · 前端设计

brand-visual-language(品牌视觉语言)

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

brand-visual-language 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 5,199。

总安装 720周安装 30GitHub Stars 6下载 240核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

brand-visual-language 通过形状语言传递品牌个性,如圆角代表友好,直角体现专业。适用于指导图标、按钮与排版设计,强化视觉一致性与情感连接。提供不同 tone 对应的 shape 推荐值(如 2–4px 轻圆角用于企业级工具)。使用时应结合具体产品类型选择形状策略,避免盲目套用造成认知混乱。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/brand-visual-language

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dembrandt/dembrandt-skills --skill brand-visua…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

brand-visual-language 怎么安装?

在终端执行 npx skills add https://github.com/dembrandt/dembrandt-skills --skill brand-visual-language。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

brand-visual-language 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

brand-visual-language 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

brand-visual-language 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

brand-visual-language 用的人多吗?

公开数据是累计安装 720 次,近一周安装 30 次,下载 240 次,GitHub 6 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

brand-visual-language 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
brand-visual-language

品牌视觉语言 · 本页

7206权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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)?

平台分布

Codex

33.51%
按下载量换算80

Claude

27.84%
按下载量换算67

Cursor

20.41%
按下载量换算49

Gemini CLI

9.09%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

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

安装前确认

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

继续浏览同类 Skills