agentleFS
alebgl77alebgl77/claude-inc/skills/brand-guidelines/SKILL.md

brand-guidelines

Skill21 starsChanged 4 months agoMITView on GitHub

Generates a brand kit from a company one-liner — positioning adjectives, a palette with hex codes, usage ratios and do/don'ts, a display+text type pairing with fallback stacks, a voice & tone table (say / never say), a logo brief, and a one-page BRAND.md brandbook other skills consume. Use when the user says "we need a brand", "create our visual identity", "pick our colors and fonts", "define our voice", or before designing anything for a company with no identity yet.

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 179 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:

    Extract positioning from the one-liner: Ask or infer the audience, the enemy (what the brand stands against — "enterprise bloat", "hidden …

    line 19

“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 — Brand Keeper

"Build a brand kit"

When to use

  • A company has a one-liner and nothing else — "we need a brand for this".
  • Visuals exist but are incoherent — "our colors and fonts differ on every page; fix the source".
  • Copy has no consistent voice — "define how we sound in the product and in emails".
  • Upstream of sibling skills — run before ui-ux-pro-max or frontend-design for a new venture.

Workflow

  1. Extract positioning from the one-liner. Ask or infer the audience, the enemy (what the brand stands against — "enterprise bloat", "hidden fees"), and the price position. Distill into exactly three positioning adjectives plus one anti-adjective: "confident, warm, precise — never cute".
  2. Translate adjectives into a palette. One ground, one text, one accent, plus semantics — each with a hex code, a name that carries meaning ("Glacier", not "Blue 2"), a usage ratio (60/30/10), one do and one don't.
  3. Pair type. One display face + one text face with real contrast between them (serif/sans, geometric/humanist), the weights worth licensing, and a CSS fallback stack for each. State the pairing logic in a single sentence.
  4. Write the voice & tone table. Four traits, each with a verbatim say-this sentence and a verbatim never-say-this counter-example, all grounded in the positioning adjectives.
  5. Draft the logo brief — not the logo. Concept direction, construction (wordmark vs mark, geometric basis), clearspace rule, minimum size, and the misuse list: no gradients, no stretching, no drop shadows, no recoloring.
  6. Assemble BRAND.md, one page. Downstream skills must be able to consume it without asking a single follow-up question.
  7. Stress-test the kit. Apply it mentally to a button, an error message, and an invoice footer. If any feels off-brand, revise the kit — never the artifact.

Output format

# BRAND.md — <Company>
**One-liner:** <as given>
**Positioning:** <adj>, <adj>, <adj> — never <anti-adjective>.

## Palette — 60/30/10
| Name | Hex | Role | Ratio | Do | Don't |
|---|---|---|---|---|---|
| Paper | #FAF9F7 | ground | 60% | page and card backgrounds | text |
| Ink | #101828 | text | 30% | body copy, headings | large filled areas |
| Glacier | #2563EB | accent | 10% | CTAs, links, focus rings | full-bleed backgrounds |

## Type
- Display: <face> (<weights>) — fallback: <stack>
- Text: <face> (<weights>) — fallback: <stack>
- Pairing logic: <one sentence>

## Voice & tone
| Trait | Say | Never say |
|---|---|---|
| Precise | "Backups run every 10 minutes." | "Blazingly fast backups!" |

## Logo brief
<direction> / <construction> / clearspace: <rule> / min size: <px> / misuse: <list>

Quality bar

  • Exactly three positioning adjectives plus one anti-adjective, all load-bearing
  • Every palette entry has hex, role, ratio, one do and one don't — no orphan swatches
  • Type pairing ships real fallback stacks and names the weights to license
  • Voice table uses verbatim example sentences, never abstract descriptions
  • BRAND.md fits one page and pre-answers the questions downstream skills would ask
  • Text color on ground color passes WCAG AA

Example

Invocation: "Brand kit for 'Ledgerly — bookkeeping that closes your month in a day'."

Produces: BRAND.md: positioning "precise, calm, unstoppable — never playful"; a palette of warm Paper ground (60%), Ink #101828 text (30%), Ledger Green #0E9F6E accent (10%) plus amber/red semantics, each with do/don'ts; Fraunces display over Inter text ("editorial authority over utilitarian clarity"); a four-row voice table (Say: "Your month is closed." Never: "Boom! Books done!"); and a wordmark brief with tabular numerals as the identity hook, cap-height clearspace, and a no-gradients-ever misuse list.

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.