← ClaudeAtlas

brand-awarenesslisted

Ensures brand-consistent behavior during workflows. Auto-activates when brand guide exists and "brand", "brand spec", "design tokens", "brand consistent", or "visual identity" are mentioned. Activates during /brand, /brand:image, /brand:tokens, /design, /deliver, /discern, /handoff, /context:load, and /context:refresh.
Elmmly/genie-team · ★ 3 · Code & Development · score 67
Install: claude install-skill Elmmly/genie-team
# Brand Awareness Brand knowledge lives in the **Brand Guide** — the third pillar of persistent project knowledge: ``` SPEC (WHAT) BRAND (HOW IT LOOKS) / \ / / \ / ADR (HOW+WHY) -- C4 (CONTEXT MAP) ``` - **Specs** describe WHAT the system does (capabilities, acceptance criteria) - **ADRs** describe HOW the system is built and WHY those technical choices were made - **Brand Guides** describe HOW IT LOOKS — visual identity, colors, typography, imagery All three are persistent, first-class artifacts. Backlog items are transient; these are not. ## Brand Guide Organization Brand Guides capture visual identity using YAML frontmatter (machine-readable) and markdown narrative (human-readable). ### Directory Structure ``` docs/brand/ {brand-name}.md # Brand Guide (YAML frontmatter + design narrative) tokens.json # W3C Design Tokens (derived from brand guide) assets/ # Generated images manifest.md # Asset catalog with provenance *.png / *.jpg # Generated files ``` ### Frontmatter Schema > Schema: `schemas/brand-spec.schema.md` v1.0 Required: `spec_version`, `type: brand-spec`, `brand_name`, `status`, `created`, `identity`, `visual` Optional: `updated`, `author`, `target_project`, `tags`, `extends` ### Brand Guide Lifecycle ``` /brand (create) → draft → /brand --activate → active → deprecated ↑