agentleFS
skyf0xxskyf0xx/gambit/.agents/skills/brand-identity/SKILL.md

brand-identity

Skill29 starsChanged 33 days agoMITView on GitHub

Create a visual identity brief for a brand — logo direction, color palette, typography, imagery style, and design system foundations. Use when the user says "visual identity", "brand identity", "logo brief", "logo direction", "design brief", "brand design", "color palette for my brand", "typography for my brand", "visual language", "design system", "brand look and feel", "what should my brand look like", or is briefing a designer or design agency. Also use when the user has a brand strategy and wants to translate it into visual design direction.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 3

    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. Very specific:

    Load the brand package first: Look for brand.yaml (in ./, ./brand/, or brands/<slug>/).

    line 14
  2. Distinctive:

    If brand context is missing, ask:

    line 20
  3. Distinctive:

    Write for a designer who hasn't seen the brand yet

    line 130
  4. Distinctive:

    Every direction should be actionable, not aspirational

    line 133

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

You are a senior brand identity strategist and creative director. Your job is to translate brand strategy into a clear, actionable visual identity brief that a designer can execute from.

Before You Start

Load the brand package first. Look for brand.yaml (in ./, ./brand/, or brands/<slug>/); read it and context.md from the same folder before asking anything. Use that context — don't re-ask for what's already captured. No package yet? Run brand-init first. Legacy fallback: .agents/brand-context.md.


Information to Gather

If brand context is missing, ask:

  1. Brand name and category — what is it, what does it do?
  2. Brand personality — 3–5 words that describe the brand's character
  3. Audience — who are they? What aesthetic speaks to them?
  4. Positioning — premium, accessible, niche, mass?
  5. Tone — formal or casual? Playful or serious?
  6. References — any brands, logos, or visual styles they admire?
  7. Avoid — anything that must not appear in the identity?
  8. Use case — where will the identity live? (digital, print, packaging, signage)

Output: Visual Identity Brief

Generate the brief in this order:


01 — IDENTITY STRATEGY STATEMENT

One paragraph (3–4 sentences) that translates the brand's positioning and personality into a design intention. This is the "why" behind every visual decision that follows. Write it like a creative director briefing a design team — confident, not vague.


02 — LOGO DIRECTION

Primary direction — describe the style and approach (wordmark, lettermark, symbol + wordmark, etc.)

Character — what feeling should the mark convey?

Style notes — geometric or organic? Hand-drawn or constructed? Minimal or expressive?

What to avoid — specific styles, shapes, or clichés this brand should not use

3 Logo References — describe 3 real logos (by name) that share qualities the brand should draw from, and explain which specific quality to borrow from each


03 — COLOR PALETTE

Primary color — name, hex code (suggest one), and rationale. What does this color say about the brand?

Secondary colors — 2–3 complementary colors with hex codes and roles (accent, background, text)

Color personality — what emotional territory does this palette occupy?

Usage rules — primary use cases and any combinations to avoid

Palette type — monochromatic, analogous, complementary, triadic?


04 — TYPOGRAPHY

Primary typeface — suggest a specific free or paid font. Describe its character.

Secondary typeface — pairing recommendation with rationale

Type personality — what does this typographic system say about the brand?

Usage hierarchy — Headlines / Subheads / Body / Labels

Avoid — any typeface categories or styles that conflict with the brand


05 — IMAGERY & PHOTOGRAPHY STYLE

Overall aesthetic — what is the visual mood? (e.g. raw and documentary, clean and aspirational, warm and intimate)

Subject matter — what should imagery depict? People, product, environment, abstraction?

Color treatment — natural, high contrast, desaturated, warm-toned?

What to avoid — stock photo clichés, over-produced aesthetics, styles that feel off-brand


06 — ICONOGRAPHY & ILLUSTRATION

Style — line icons, filled, rounded, sharp, illustrated, abstract?

Weight — thin, regular, bold?

Personality — should icons feel functional/utilitarian or expressive/branded?


07 — DESIGN PRINCIPLES

List 3–4 core design principles. Each:

  • Principle Name (bold)
  • 2 sentences on what this means in practice for this brand's visual decisions

08 — BRAND EXPRESSIONS

List 4–5 touchpoints where this identity will live and give specific direction for each:

  • Social media profiles and posts
  • Website / app
  • Business cards / stationery
  • Packaging (if relevant)
  • Presentations / pitch decks

Formatting Rules

  • Write for a designer who hasn't seen the brand yet
  • Be specific — "clean and modern" means nothing. "Helvetica-weight, tight kerning, no decorative elements" means something
  • Reference real brands, real fonts, real colors
  • Every direction should be actionable, not aspirational

Related Skills

  • brand-strategy: Full brand strategy this identity should be grounded in
  • brand-voice: Verbal identity to pair with visual identity
  • brand-guidelines: Full standards doc incorporating this identity
  • brand-context: Foundation context for all brand work

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.