Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Brand Identity

ASecurity

Build complete brand identity systems with strategy, visual language, voice, and usage guidelines.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreactgit

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill brand-identity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brand Identity?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Brand Identity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-brand-identity/badge)](https://www.skillsdirectory.com/skills/aicodedecode-brand-identity)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: brand-identity
description: Build complete brand identity systems with strategy, visual language, voice, and usage guidelines.
category: creative-design
---

## Overview

A brand identity is the complete system through which a company presents itself: strategy (who we
are, for whom, why), visual language (logo, color, typography, imagery), voice (how we sound), and
the rules that keep it all coherent. This skill builds identities from strategy down to deliverables
— because visuals without strategy are decoration, and strategy without visuals is a memo.

## When to use

- Creating a brand identity for a new company or product

- Rebranding an existing business

- Building brand guidelines from scratch

- Auditing an inconsistent brand across touchpoints

- Extending an identity to new products or markets

## Core concepts

- - **Strategy before visuals.** Positioning (what space do we own?), audience (who exactly?),
  personality (how would the brand act at a dinner party?), and differentiators. Every visual choice
  should trace back to strategy.
- - **The identity system, not just a logo.** Logo, color palette, typography scale, imagery style,
  iconography, patterns/textures, motion principles. The system matters more than any single element
  — it's what makes a brand recognizable with the logo removed.
- - **Voice and tone.** How the brand writes: 3-4 voice attributes (e.g., "confident, warm,
  plain-spoken") with do/don't examples. Voice is half the identity and the most neglected half.
- - **Flexibility within consistency.** A rigid identity breaks on new formats; a loose one
  dissolves. Define the non-negotiables (logo clearspace, core colors) and the playground
  (illustration styles, campaign treatments).
- - **Touchpoint audit.** List every place the brand appears — website, app, packaging, social,
  email, office, invoices. The identity must work across all of them, and the audit reveals which
  need the most help.
- - **Guidelines people actually use.** A 200-page brand book nobody opens is worse than a 20-page
  one everyone follows. Prioritize: logo rules, color, typography, voice examples, and common
  templates.

## Practical workflow

1. 1. **Discovery and strategy.** Stakeholder interviews, audience research, competitor audit.
   Output: positioning statement, personality attributes, and 3-5 brand pillars. Get sign-off before
   any visual work.
2. 2. **Moodboards and directions.** 2-3 distinct visual directions (not logos yet — overall feel:
   color, type, imagery). Present with strategy rationale; let stakeholders react to feelings before
   forms.
3. 3. **Design the core system.** Logo (see logo-designer), color palette (primary, secondary,
   neutrals with exact values), typography (display + text faces with scale), imagery direction
   (photography style or illustration style).
4. 4. **Build the supporting elements.** Iconography style, patterns or graphic devices, layout
   principles, motion/feel guidelines for digital. Test the system: can you design 5 different
   touchpoints that clearly belong together?
5. 5. **Define voice.** Voice attributes with examples, tone adjustments by context (marketing vs
   support vs legal), and a word list (we say X, not Y).
6. 6. **Apply to real touchpoints.** Design 5-8 key applications: homepage hero, social profile,
   business card or email signature, packaging or app icon, one campaign piece. Real applications
   prove the system works.
7. 7. **Write the guidelines.** Concise, visual, practical: the rules, the files, the templates, and
   who to ask. Include don'ts with visual examples — they prevent more damage than the do's create
   value.

## Common pitfalls

- - **Logo-first branding.** Designing the mark before strategy produces a pretty picture with no
  foundation. The logo is maybe 10% of an identity.
- - **Strategy nobody believes.** Positioning written to please the CEO rather than reflect reality.
  If employees roll their eyes, the identity is fiction.
- - **Inconsistent application.** The identity dies in a thousand small cuts: off-brand decks, rogue
  social posts, outdated templates. Governance (who approves what) matters as much as design.
- - **Designing for the launch, not the decade.** Trendy identities age fast. Test: will this still
  feel right in 5 years, across formats that don't exist yet?
- - **Ignoring internal brand.** Employees are the primary audience. If the team doesn't understand
  and embody the identity, no guideline document will save it.
- - **The guideline graveyard.** Over-detailed manuals that nobody reads. Keep it short, visual, and
  focused on the decisions people actually face weekly.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →