shared-brand

Codify brand tokens, typography constraints, and anti-patterns for iOS, web, and apps.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill shared-brand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-brand
Source: https://github.com/edfenton/claude-skills/tree/main/shared/shared-brand
Command: npx skills add https://github.com/edfenton/claude-skills --skill shared-brand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brands across platforms often struggle with inconsistent visuals and messaging, leading to a fragmented identity.

Core Features & Use Cases

  • Centralized tokens and design rules for colors, typography, spacing, and anti-patterns to ensure consistent brand execution.
  • Platform-specific guidance that references core tokens to maintain visual coherence across iOS, web, and apps.
  • Use Case: A design team updates the core color palette once and all platform styleguides reflect the change automatically.

Quick Start

Centralize your brand tokens and anti-pattern guidelines in this shared resource and reference it from your platform-specific styleguides.

Frequently Asked Questions about shared-brand

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unify brand identity across iOS, web, and apps?

To unify brand identity across platforms, you codify centralized design tokens, typography philosophy, color usage rules, and anti-patterns as a formal specification. Platform-specific styleguides then reference this shared resource to maintain visual coherence and consistent messaging.

What are design tokens and how do they keep brand colors consistent?

Design tokens are centralized variables that define core brand colors, typography, and spacing. By updating a token once in a shared specification, all platform-specific styleguides automatically reflect the change, ensuring consistent brand execution across iOS and web.

How do I document brand anti-patterns in a styleguide?

Documenting brand anti-patterns involves defining requirements for token usage, color constraints, typography limits, and explicit avoidance rules within a formal specification. This centralized resource guides platform styleguides to prevent fragmented visual identity.

Can I use this brand identity specification for a design system team?

Yes, this specification is applicable to design systems teams, product studios, and platform-specific styleguides. It defines the requirements for tokens, color usage rules, typography constraints, and anti-pattern avoidance needed to maintain consistent visuals across platforms.

What is the best way to manage typography constraints across multiple platforms?

The best way to manage typography constraints is codifying a centralized typography philosophy and token specifications in a shared resource. Platform-specific styleguides reference these core tokens to maintain visual coherence across iOS, web, and apps.

Why does our brand identity look fragmented across different platforms?

Brand identity fragments across platforms when visuals and messaging lack centralized rules. Codifying shared design tokens, typography philosophy, color usage rules, and anti-patterns as a formal specification ensures platform styleguides maintain visual coherence.