Token导航 LogoToken导航

Agent Skill · 开发规范

brand-guidelines(品牌指南)

brand-guidelines 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

brand-guidelines 是开发规范类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在开发规范类的 1,265 个 Skill 里排第 836。

总安装 416周安装 17GitHub Stars 56下载 133核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/vm0-ai/vm0-skills --skill brand-guidelines

这个 Skill 是做什么的

开发规范类 Skill 用来统一代码风格、目录结构和评审口径,产出多为检查清单或改写建议。

brand-guidelines 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在开发协作场景中整理项目状态。适用于围绕仓库状态、代码变更或协作事项进行信息整合的场景。通过 npx skills add 命令从 GitHub 仓库安装并使用。

安装前建议确认权限范围和维护状态,注意可能触发联网或文件读写操作。可结合原始 README 进一步核验具体用法和功能细节。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

brand-guidelines 怎么安装?

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

brand-guidelines 支持哪些 AI 工具?

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

brand-guidelines 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/vm0-ai/vm0-skills --skill brand-guidelines 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

brand-guidelines 是免费的吗?

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

brand-guidelines 用的人多吗?

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

brand-guidelines 安全吗?

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

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

值得选的地方

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

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发规范类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
vercel-react-best-practices

Vercel React 最佳实践 · Codex、Claude

8,490,72025,918操作浏览器MIT通过
web-design-guidelines

网页设计指南 · Codex、Claude

6,686,01625,885需要联网MIT有提醒
remotion-best-practices

Remotion 最佳实践 · Codex、Claude

6,505,6323,027操作浏览器MIT有提醒
supabase-postgres-best-practices

Supabase Postgres 最佳实践 · Codex、Claude

3,175,5232,030需要联网MIT通过
next-best-practices

Next.js 最佳实践 · Codex、Claude

1,848,240841操作浏览器MIT通过
brand-guidelines

品牌指南 · 本页

41656执行命令未明确通过

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

SKILL.md 原文

Building a Brand Voice Document

A thorough voice reference covers the following areas. Use this structure to help teams articulate their voice from scratch or to interpret an existing voice configuration.

Brand Personality Profile

Describe the brand as though it were a human being. What character traits define it?

Example: "Our brand is the sharp-but-generous mentor — someone who breaks down hard ideas in plain language, takes genuine pride in your progress, and never condescends."

Communication Attributes (3-5)

Each attribute needs four elements to prevent ambiguity:

  • A plain-language definition of what it means in practice
  • A boundary statement explaining what it does NOT mean
  • A sample sentence that embodies the attribute
  • A sample sentence that violates the attribute

Target Audience Profile

  • Primary and secondary audiences the brand addresses
  • Core concerns and motivations of each audience
  • Level of domain expertise to assume
  • Communication expectations and preferences

Messaging Pillars (3-5)

  • The recurring strategic themes the brand reinforces
  • Relative priority among pillars (which leads in any given context)
  • How each pillar maps to an audience need or pain point

Contextual Tone Range

How the voice flexes across situations while remaining unmistakably the same brand. See the Tone Modulation section below.

Editorial Style Rules

Concrete grammar, punctuation, and formatting standards. See Editorial Standards below.

Vocabulary Controls

Approved and prohibited terms. See Vocabulary Governance below.

Defining Communication Attributes

Attribute Spectrum Reference

Positioning attributes on a continuum helps teams calibrate. Common spectrums include:

DimensionEnd AEnd B
RegisterFormal, institutionalRelaxed, conversational
ExpertiseAuthoritative, expertCollaborative, peer-level
WarmthEmpathetic, personalDirect, no-nonsense
TechnicalityPrecise, specializedPlain, universally accessible
IntensityBold, high-energyCalm, understated
LevityPlayful, wittySerious, measured
OrientationForward-looking, innovativeEstablished, reliability-focused

Attribute Documentation Template

For every selected attribute, record:

[Attribute Name]

  • In practice: [concrete behavioral description]
  • Not to be confused with: [the common misinterpretation]
  • Sounds like: [example sentence demonstrating it well]
  • Does not sound like: [example sentence that crosses the line]

Example:

Welcoming

  • In practice: inclusive, clear, free of jargon, equally respectful to newcomers and veterans
  • Not to be confused with: oversimplified, excessively informal, or lacking depth
  • Sounds like: "Getting set up takes about five minutes — here is how."
  • Does not sound like: "Yo! Even a total beginner can figure this out lol."

Tone Modulation

The brand voice is the constant; tone is the variable that adjusts based on context. Tone represents the emotional calibration applied to the voice.

Tone by Communication Channel

ChannelTone ShiftIllustration
BlogEducational, conversational, exploratory"Here is a walkthrough of how this works and why your team should care."
LinkedInProfessional, thought-provoking, compact"Three takeaways from running 50 campaigns last quarter."
Twitter/XSharp, concise, occasionally playful"Your landing page gets 3 seconds. Spend them wisely."
Email marketingPersonal, supportive, action-oriented"We built something we think will save you real time."
Sales materialsAssured, benefit-focused, evidence-backed"Teams on our platform cut reporting overhead by 40%."
Help documentationPatient, sequential, unambiguous"If this error appears, follow these steps to resolve it."
Press releasesFormal, factual, newsworthy"The company announced today the general availability of..."
Error statesUnderstanding, constructive, non-blaming"We hit a snag on our side. Our team is already investigating."

Tone by Scenario

ScenarioTone Adjustment
Product launchConfident, enthusiastic, forward-looking
Service disruptionTransparent, accountable, empathetic
Customer winCelebratory, specific, customer-centered
Industry thought leadershipNuanced, evidence-driven, authoritative
New user onboardingEncouraging, clear, welcoming
Unwelcome news (price changes, deprecations)Honest, respectful, solution-focused
Competitive positioningSelf-assured, factual, never disparaging

The Dial Principle

Voice attributes remain constant. Tone turns their intensity up or down depending on the moment. For a brand that is "confident and warm":

  • At a product launch, confidence takes the lead
  • During an outage, warmth takes the lead
  • Neither quality vanishes; the emphasis shifts

Editorial Standards

Grammar and Mechanical Choices

Consistency matters more than any single choice. Document and enforce these decisions:

DecisionAlternativesSample
Serial commaInclude / Omit"fast, reliable, and secure" vs. "fast, reliable and secure"
Heading capitalizationSentence case / Title case"How to get started" vs. "How to Get Started"
ContractionsPermit / Avoid"we're" vs. "we are"
Em dash styleNo surrounding spaces / Spaces"this—and more" vs. "this — and more"
Numeral rulesSpell out one through nine / Always use digits"five features" vs. "5 features"
Percentage notationSymbol / Word"50%" vs. "50 percent"
Date stylingMonth DD, YYYY / DD/MM/YYYY / other"January 15, 2025"
Time styling12-hour / 24-hour"3:00 PM" vs. "15:00"
List punctuationTerminal periods / No periods on fragments"Set up your account." vs. "Set up your account"

Formatting Conventions

  • Heading hierarchy rules (when H1, H2, H3 are appropriate)
  • Bold vs. italic purpose (bold for emphasis, italic for titles or introducing terms)
  • Hyperlink text standards (always descriptive; never "click here")
  • Image alt text requirements
  • Code formatting norms (for technical brands)
  • Use of callout or highlight boxes

Punctuation and Emphasis Policies

  • Exclamation marks: use sparingly, never consecutively
  • Ellipses: avoid in professional content
  • All-caps: prohibited for emphasis; use bold instead
  • Emoji: prohibited in professional channels; acceptable in social where context warrants

Vocabulary Governance

Standardized Terms

Maintain an authoritative list of correct forms alongside common mistakes:

Approved FormIncorrect FormRationale
sign up (verb)signup (verb)"signup" is the noun/adjective form
log in (verb)login (verb)"login" is the noun/adjective form
set up (verb)setup (verb)"setup" is the noun/adjective form
emaile-mailNo hyphen; industry standard
websiteweb siteSingle word; modern convention
data is (singular)data areUnless publication style mandates plural

Product and Feature Naming

  • Canonical capitalization for every product name
  • Rules for when to use the full name vs. an abbreviated form
  • Whether "the" precedes product names
  • How version numbers appear in copy
  • Trademark and registration symbol usage (where required and where to omit)

Language Inclusivity

  • Default to gender-neutral pronouns (they/them for individuals of unknown gender)
  • Eliminate ableist expressions ("crazy", "blind spot", "lame")
  • Favor person-first phrasing where relevant
  • Steer clear of culturally-bound idioms that resist translation
  • Prefer "straightforward" or "simple" over "easy" — difficulty is subjective

Technical and Industry Terminology

  • Catalogue which specialized terms the audience grasps without explanation
  • Identify jargon that must always be defined or replaced with plain language
  • Specify which acronyms require full expansion on first use
  • Build an audience-segmented glossary for terms with different meanings across reader groups

Competitive and Market Language

  • Define your preferred framing for your product category
  • Establish how competitors are referenced (by name or generically)
  • Identify competitor-coined terms to avoid, so you do not reinforce rival positioning
  • Codify your preferred differentiation phrasing

平台分布

Codex

39.04%
按下载量换算52

Claude

27.92%
按下载量换算37

Cursor

19.36%
按下载量换算26

Gemini CLI

9.02%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/vm0-ai/vm0-skills --skill brand-guidelines 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills