agentleFS
scayverscayver/marketing-skills/skills/brand-guidelines/SKILL.md

brand-guidelines

Skill8 starsChanged 5 months agoMITView on GitHub

Use this skill when the user wants brand guidelines, brand voice rules, tone standards, visual identity documentation, messaging rules, logo usage guidance, color and typography guidance, content style rules, or a brand system audit. Trigger phrases include "brand guidelines," "brand book," "brand voice," "style guide," "visual identity," "tone guidelines," "brand system," and "audit our brand guidelines."

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write in active voice.

    line 16
  2. Distinctive:

    Use short sentences and plain language.

    line 17
  3. Very specific:

    Use .marketing-os/product-context.md when it exists.

    line 19
  4. Distinctive:

    Do not invent brand assets, trademark status, legal claims, accessibility conformance, or audience research.

    line 20
  5. Distinctive:

    Keep guidance brand-neutral unless the user provides brand context.

    line 21
  6. Distinctive:

    Use practical rules that writers, designers, and agents can apply.

    line 22
  7. Distinctive:

    Do not use em dashes, hashtags, emojis, or filler closings.

    line 23
  8. Distinctive:

    Use this skill to create or audit brand guidelines that keep messaging, visuals, and content consistent across people, agents, channels, …

    line 28
  9. Distinctive:

    Do not create fake asset values.

    line 88
  10. Distinctive:

    Document logo clear space, minimum size, approved variations, color palette, typography roles, image style, icon style, layout density, …

    line 90

“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brand Guidelines

Mandatory Content Standards

  • Write in active voice.
  • Use short sentences and plain language.
  • Address the user as "you" and "your."
  • Use .marketing-os/product-context.md when it exists. If it is blank or missing, recommend running product-marketing first.
  • Do not invent brand assets, trademark status, legal claims, accessibility conformance, or audience research.
  • Keep guidance brand-neutral unless the user provides brand context.
  • Use practical rules that writers, designers, and agents can apply.
  • Do not use em dashes, hashtags, emojis, or filler closings.
  • End every full deliverable with one specific next step.

Objective

Use this skill to create or audit brand guidelines that keep messaging, visuals, and content consistent across people, agents, channels, and campaigns.

This skill complements brand-storytelling, copywriting, linkedin-strategy, pr-communications, ai-image-creator, and social-content-planner.

Next step: collect existing brand assets before writing rules.

Required Inputs

InputWhy It Matters
Brand nameAnchors the guideline
AudienceDefines tone and clarity
PositioningConnects guidelines to strategy
ValuesGuides judgment calls
Existing logo and colorsPrevents invented visual rules
Voice examplesShows what "on brand" means
CompetitorsHelps define differentiation
Accessibility needsKeeps visual guidance usable

Next step: ask for the missing asset that most affects consistency.

Guideline Sections

SectionWhat To Include
Brand foundationMission, audience, promise, values, category
PositioningICP, problem, value proposition, differentiators
VoicePersonality, tone range, do and do not rules
MessagingTagline, elevator pitch, proof points, boilerplate
Visual identityLogo usage, color, type, imagery, layout rules
Content styleGrammar, formatting, vocabulary, banned words
Channel rulesWebsite, email, LinkedIn, ads, support, PR
AccessibilityContrast, alt text, readability, motion, inclusive language
GovernanceApprovals, ownership, update rhythm

Next step: build the foundation before visual rules.

Brand Voice Framework

DimensionLow EndHigh EndBrand Choice
WarmthDirectFriendly
EnergyCalmBold
ExpertiseSimpleTechnical
FormalityCasualPolished
PersonalityMinimalExpressive

Add examples.

ContextOn-Brand ExampleOff-Brand ExampleRule
Homepage headline
Support reply
LinkedIn post
Sales email

Next step: create five channel-specific examples.

Visual Guidance

Do not create fake asset values. If the user has not provided colors, fonts, or logo files, output placeholders that ask for source assets.

Document logo clear space, minimum size, approved variations, color palette, typography roles, image style, icon style, layout density, button style, CTA style, and accessibility notes.

Next step: verify color contrast before approving visual guidance.

Output Format

Guideline AreaRuleExampleOwnerReview Cadence

For a full brand guide, deliver brand foundation, messaging system, voice rules, visual identity rules, channel examples, accessibility checklist, agent usage notes, and governance plan.

End with the highest-priority brand asset to standardize next.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.