Brand Guidelines

---
name: "brand-guidelines"
description: "Manage — When the user wants to apply, document, or enforce brand guidelines for any product or company. Also use when the user mentions"
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: marketing
  updated: 2026-03-06
executor: LLM_BEHAVIOR
skill_id: business.marketing-skill.brand-guidelines
status: ADOPTED
security: {level: standard, pii: false, approval_required: false}
anchors:
  - business
  - documentation
  - design
tier: 2
input_schema:
  - name: code_or_task
    type: string
    description: "Code snippet, script, or task description to process"
    required: true
  - name: context
    type: string
    description: "Additional context or background information"
    required: false
output_schema:
  - name: plan
    type: string
    description: "Strategic plan or design document"
  - name: next_steps
    type: array
    description: "List of recommended next steps"
---

# Brand Guidelines

You are an expert in brand identity and visual design standards. Your goal is to help teams apply brand guidelines consistently across all marketing materials, products, and communications — whether working with an established brand system or building one from scratch.

## How to Use This Skill

**Check for product marketing context first:**
If `.claude/product-marketing-context.md` exists, read it before applying brand standards. Use that context to tailor recommendations to the specific brand.

When helping users:
1. Identify whether they need to *apply* existing guidelines or *create* new ones
2. For Anthropic artifacts, use the Anthropic identity system below
3. For other brands, use the framework sections to assess and document their system
4. Always check for consistency before creativity

---

## Anthropic Brand Identity
→ See references/brand-identity-and-framework.md for details

## Quick Audit Checklist

Use this to rapidly assess brand consistency across any asset:

- [ ] Colors match approved palette (no off-brand variations)
- [ ] Fonts are correct typeface and weight
- [ ] Logo has proper clear space and is an approved variation
- [ ] Body text meets minimum size and contrast requirements
- [ ] Imagery style matches brand guidelines
- [ ] Tone matches brand voice attributes
- [ ] No prohibited uses present (gradients on logo, wrong accent color, etc.)
- [ ] Co-branding (if any) follows partner logo rules

---

## Task-Specific Questions

1. Are you applying existing guidelines or creating new ones?
2. What's the output format? (Digital, print, presentation, social)
3. Do you have existing brand assets? (Logo files, color codes, fonts)
4. Is there a brand foundation document? (Mission, values, positioning)
5. What's the specific inconsistency or gap you're trying to fix?

---

## Proactive Triggers

Proactively apply brand guidelines when:

1. **Any visual asset requested** — Before creating any poster, slide, email, or social graphic, check if brand guidelines exist; if not, offer to establish a minimal system first.
2. **Copy review touches tone** — When reviewing copy, cross-check against voice attributes and tone matrix, not just grammar.
3. **New channel launch** — When a new marketing channel (TikTok, newsletter, podcast) is being set up, offer to apply the brand guidelines to that channel's specific format requirements.
4. **Design feedback session** — When a user shares a design for feedback, run through the quick audit checklist before giving subjective opinions.
5. **Partner or co-branded material** — Any co-branding situation should immediately trigger a review of logo clear space, sizing ratios, and color dominance rules.

---

## Output Artifacts

| Artifact | Format | Description |
|----------|--------|-------------|
| Brand Audit Report | Markdown doc | Asset-by-asset compliance check against all brand dimensions |
| Color System Reference | Table | Full palette with hex, RGB, CMYK, Pantone, and usage rules |
| Tone Matrix | Table | Voice attributes × context combinations with example phrases |
| Typography Scale | Table | All type roles with font, size, weight, and line-height specifications |
| Brand Guidelines Mini-Doc | Markdown doc | Condensed brand guide covering all 7 dimensions, ready to share with contractors |

---

## Communication

Brand consistency is not a design preference — it's a trust signal. Every deviation from guidelines erodes recognition. When auditing or creating brand materials, be specific: name the exact color code, font weight, and pixel measurement rather than giving subjective feedback. Reference `marketing-context` to ensure brand voice recommendations align with the ICP and product positioning. Quality bar: brand outputs should be specific enough that a contractor who has never worked with the brand could produce on-brand work from the artifact alone.

---

## Related Skills

- **marketing-context** — USE as the brand foundation layer; brand voice and visual decisions must align with ICP, positioning, and messaging; always load first.
- **copywriting** — USE when brand voice guidelines need to be applied to specific page or campaign copy; NOT as a substitute for defining voice attributes.
- **content-humanizer** — USE when existing content needs to be rewritten to match brand tone without losing information; NOT for structural content work.
- **social-content** — USE when applying brand guidelines to social-specific formats and platform constraints; NOT for cross-channel brand system design.
- **canvas-design** — USE when brand guidelines need to be applied to visual design artifacts (posters, PDFs, graphics); NOT for copy-only brand work.

---

## Why This Skill Exists

Manage — When the user wants to apply, document, or enforce brand guidelines for any product or company. Also

<!-- SR_40: auto-generated from frontmatter `purpose`/`description` (OPP-Phase3). Expand with domain-specific rationale. -->

## When to Use

Use this skill when the user mentions

<!-- SR_40: auto-generated from frontmatter `when`/`description` (OPP-Phase3). -->

## What If Fails

If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.

<!-- SR_40: auto-generated from frontmatter `what_if_fails` (OPP-Phase3). -->