agentleFS
SkillMedevSkillMedev/content-marketing-engine/skills/brand-guidelines/SKILL.md

brand-guidelines

Skill1 starsChanged 39 days agoMITView on GitHub

Writes a brand guidelines document - personality traits with is/is-not definitions, voice principles, a tone-by-context matrix, writing mechanics, a say-this-not-that word list, and visual usage rules - all made concrete with do/don't examples. Use when someone asks "write our brand guidelines", "document our voice and tone", "make a style guide the whole team can follow", or teams keep producing off-brand copy and design. Do NOT use for inventing the brand name itself - use brand-naming instead; for organizing messaging by audience and claim, use messaging-hierarchy.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use academy-guide, skill-share and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    academy-guide

    Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

    Also in 9 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 25 projects that use this

  • ArogyaReddySkill

    raffle-winner-picker

    Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.

    Also in 26 projects that use this

  • zephyrwang6Skill

    deepl

    Übersetzt Texte, Dokumente und XLIFF-Dateien via DeepL API. Verwende für Übersetzungen mit /deepl translate, /deepl file oder /deepl xliff.

    Also in 4 projects that use this

  • zephyrwang6Skill

    imagemagick-conversion

    Convert and manipulate images with ImageMagick. Covers format conversion, resizing, batch processing, quality adjustment, and image transformations. Use when user mentions image conversion, resizing images, ImageMagick, magick command, batch image processing, or thumbnail generation.

    Also in 4 projects that use this

  • +3 more from zephyrwang6
  • +4 more from ArogyaReddy

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Be specific: Every guideline should be testable: could two people apply it the same way?

    line 50

“Common” is measured: kept by at least 6 in 10 of the 178 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 Doc

You write brand guidelines: the reference that keeps everyone - writers, designers, support, partners - sounding and looking like one coherent brand. Good guidelines are specific and usable, not abstract poetry.

Core principle

A guideline is only useful if it changes what someone writes or designs today. Replace vague adjectives with concrete rules and examples. "Be friendly" is useless; "Use contractions and address the reader as 'you'; never use corporate jargon like 'leverage' or 'synergy'" is usable.

Process

  1. Gather: the brand's mission/values, audience, personality, and any existing materials to derive patterns from.
  2. Define the verbal identity (voice, tone) and document visual principles.
  3. Make everything concrete with do/don't examples.

Sections

Brand foundation

  • Mission, values, and the audience - brief. The "why" behind the rules.
  • Brand personality: 3-5 traits (e.g., "confident, warm, precise"). For each, say what it means and what it does NOT mean ("confident, not arrogant").

Voice (constant)

  • The brand's enduring character - how it always sounds.
  • Express as principles with examples. "We're clear, not clever" - show a clever line and its clearer rewrite.

Tone (variable by context)

  • How voice flexes by situation: a celebratory moment vs. an error vs. a legal notice. Provide a small matrix: scenario → tone shift → example.

Writing mechanics

  • Grammar and style choices: contractions yes/no, Oxford comma, sentence case vs. title case, emoji policy, point of view, jargon to avoid, preferred terms.
  • A word list: "say this, not that."

Visual principles

  • Logo usage: clear space, minimum size, what not to do (don't stretch, recolor, add effects).
  • Color palette: primary/secondary with usage notes and accessibility (contrast) guidance.
  • Typography: typefaces and when to use each.
  • Imagery and iconography style: the feel, with examples of on-brand vs. off-brand.

Usage examples

  • Real before/after rewrites and good/bad design callouts. Examples teach faster than rules.

Rules for the rules

  • Be specific. Every guideline should be testable: could two people apply it the same way?
  • Show, don't just tell. Pair each principle with a concrete example and a counterexample.
  • Cover edge cases people actually hit (error messages, social replies, legal copy).
  • Keep it scannable - headers, tables, do/don't columns. People reference, they don't read cover to cover.
  • Stay practical - skip philosophical brand essays that no one applies.

Anti-patterns

  • Vague adjectives with no examples ("be authentic").
  • Visual rules with no don'ts (the don'ts prevent the worst misuse).
  • A document so long no one reads it - prioritize the high-frequency decisions.

Output

Deliver the guidelines organized by section, with concrete do/don't examples throughout, a personality definition that says what each trait is NOT, and a "say this, not that" word list. Flag where you need real brand inputs (palette, typefaces, mission) rather than inventing them.

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.