Claude skills for branding

Claude skill

Brand identity system skill

Lesson 4 of 11 in Claude skills for branding.

Checked against the makers' documentation on 17 October 2026.

Lesson

A skill that makes Claude write a visual identity system the way a design director does, as a spec a designer can build from without guessing. It turns your strategy into a one-page identity brief with three to five principles that rule things out. Then it lists every place the brand will appear, with its size, how it is made and how far away it is read. From that list it decides which logos you need, writes a spec card for each mark with minimum sizes and clear space, gives every colour and typeface a job, sets photo rules with numbers, and ends with an applications list in launch waves.

Inside are five reference files: strategy to form, the logo suite and applications, the system elements (colour, type, imagery, devices and layout), dated standards and platform specs, and a fully worked example for a fictional veterinary group. Claude computes every contrast ratio instead of guessing. It quotes WCAG 2.2, favicon and app icon sizes, the rules for a logo in Gmail, typeface licences, US trademark fees and ADA sign rules from a file checked in October 2026, with sources. Ink, thread and vinyl colours stay marked "to match" until your vendor answers. It never invents facts about your business or your competitors.

Claude does not draw the logo. If you have none, it writes the brief for the designer who will. If you have one, it audits it at 16 pixels, in one colour and in silhouette before building around it, and never redesigns it unless you ask. It cannot take photographs or make images here, so it writes the imagery rules and prompts for your own tools. With code execution on, it renders your logo at small sizes, draws diagrams and delivers the spec as a Word, PDF or PowerPoint file, with the applications list as a spreadsheet. Bring the strategy, your logo files and five competitor screenshots.

Claude skill · version 1.0

Brand identity system

Checking your access.

In the download · 9 files

  • SKILL.mdThe method Claude follows: identity brief, applications and the suite, logo suite spec, colour and type, imagery and layout, and the build spec, one stage at a time.
  • README.mdHow to install it in claude.ai or Claude Code, how to start, and the licence.
  • references/strategy-to-form.mdTurning a strategy into the identity brief, a table that translates personality traits into form, principles that rule things out, the competitor convention map and red flags in strategy documents.
  • references/logo-suite.mdThe applications inventory, the six hard cases, which marks a brand needs, the mark spec card, minimum sizes and how to test them, clear space, misuse, file naming and the applications list in waves.
  • references/system-elements.mdColour roles and shares, colour values for screen, print, thread and vinyl, contrast pairs, type roles and scales, imagery rules, icons, graphic devices, layout principles, motion and the stress test.
  • references/standards-and-specs.mdWCAG 2.2 contrast and the logo exemption, favicon, app icon and social profile sizes, the logo in Gmail, typeface licences, protected symbols, US trademark fees and ADA sign rules, each with its source, checked October 2026.

Install it and begin

  1. 01Install it in Claude CodeTerminal
    mkdir -p ~/.claude/skillsunzip ~/Downloads/brand-identity-system.zip -d ~/.claude/skills/# Start it with /brand-identity-system. If this is your first skill, type /reload-skills once.

    On claude.ai there is nothing to unzip: upload the zip as it is. Every step is on Install and use a Claude skill.

  2. 02Your first message to ClaudeText
    Use the brand identity system skill. The brand is [BRAND NAME], a [WHAT IT IS AND SELLS] for [WHO IT IS FOR] in [COUNTRY AND CITY]. It will be built and maintained by [WHO, IN WHICH TOOLS]. Here is our strategy: [ATTACH OR PASTE IT]. Start with the identity brief and tell me what is missing.

    Attach the strategy or workshop notes, any logo files you have (SVG or PDF if possible) and screenshots of five or six competitors. Real customer quotes help Claude write principles that hold up.

the logothe smallest parttypecolourlayoutimagevoicemotionpeople can name the logo and nothing elsethe other six are what they actually recognise you by
What an identity system holds beyond the logo: type, colour, layout, image and voice.

Checklist

Before an identity spec goes to the designer

  • Every mark in the suite does a job for at least two real applications on the list.A mark nobody needs is a mark nobody maintains, and it drifts.
  • Each mark has a screen minimum in pixels and a print minimum in inches and millimetres, taken from a test strip and a printed proof.Guessed minimums fail first, on the favicon and the embroidered shirt.
  • Clear space and lockup gaps are written in x, a unit taken from the mark itself, never in fixed millimetres.Rules in x scale with the logo. Fixed measurements break at every new size.
  • Every colour has a job, a share of the surface and a value for each medium on the list, or "to match" with the vendor named.A screen hex code tells an embroiderer or a sign maker nothing.
  • Every text and background pair has a computed contrast ratio, at least 4.5:1 for body text, and the tempting forbidden pairs are named.WCAG exempts the logo, not the brand colours used for headlines, links and buttons.
  • Each typeface has a role, a licence that covers the logo, the web and the team's own tools, and a fallback for email.A face the team cannot use in Canva or Google Docs gets swapped for whatever is installed.
  • The rules were tested on the smallest, the roughest and one dense piece, and every rule that broke was changed.A system is only as strong as its hardest application.
  • Every application has a mark, a colour version, a method, an owner and a launch wave.Signs, uniforms and printed stock are slow and costly to change, so they are planned first.

What to do it with

  • ClaudeFree tier, paid above it

    A language model that writes, edits, reads long documents and runs tools, including agents that work inside a codebase.

    Bad at It is agreeable by default, so it will improve a bad idea instead of telling you it is bad. Ask it to argue against you and the quality of the answer changes.

  • Claude CodeSubscription

    An agent that reads a whole repository, edits files, runs the tests and explains what it changed.

    Bad at It is fast enough to make a large mistake quickly. Work on a branch, read the diff, and never let it push. Watch the starting mode: on Pro, Max and Team plans it opens in auto mode, which Anthropic's own list says may read a .env file and send the key in it to the API that key belongs to. Switch it off.

The whole tool directory

Why it matters

Ask a chat for a brand identity and you get a mood, five hex codes and two font names. Nothing says which logo goes on the embroidered shirt, which green may sit behind small text, or what the next designer should do when a case is not covered. This skill makes Claude start from the places the brand must work, test every rule on the hardest of them, and write numbers that a stranger can follow a year later.


Type
technique
Period
ongoing

Hear about new courses.

Leave an email and we will tell you when something new lands. We do not write often.