brand-identity

Centralize brand governance using design-tokens.json, tech-stack.md, and voice-tone.md.

3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/alunadev/ald_skills --skill brand-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-identity
Source: https://github.com/alunadev/ald_skills/tree/main/design/brand-design
Command: npx skills add https://github.com/alunadev/ald_skills --skill brand-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a centralized source of truth for brand guidelines, design tokens, technology choices, and voice/tonality to ensure consistent branding across all assets.

Core Features & Use Cases

  • Brand governance: Centralizes tokens, colors, typography, and voice guidelines to keep branding consistent across design and copy.
  • Guidelines for teams: Serves as a reference when creating UI components, marketing content, and developer docs.
  • Use Case: When starting a new product or campaign, consult these resources to align visuals and messaging.

Quick Start

To align all assets with brand guidelines, reference the tokens.json, tech-stack.md, and voice-tone.md in the resources directory and apply them to your design and content workflows.

Frequently Asked Questions about brand-identity

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

FAQPage Schema
How do I centralize brand guidelines for consistent design and development?

Centralize brand guidelines by packaging design tokens, typography, and voice guidelines into a single resource. This enforces consistent branding across UI components, developer docs, and marketing content by standardizing the source files.

What is a design tokens file used for in brand governance?

A design tokens file is used to centralize colors, typography, and visual attributes into a standardized format. It serves as a reference to maintain brand consistency across all product interfaces and marketing assets.

How do I keep voice and tone consistent across marketing content?

Keep voice and tone consistent by referencing a centralized voice-tone.md file during content creation. This enforces standardized messaging guidelines for all marketing copy and developer documentation.

Can I use this brand identity resource for both UI components and developer docs?

Yes, this brand identity resource applies to both UI components and developer docs. It provides a unified reference for design tokens and voice guidelines to align visuals and messaging across multiple workflows.

What's the best way to align new campaigns with existing brand standards?

The best way to align new campaigns is to consult centralized resources like tokens.json and voice-tone.md. Applying these standardized guidelines ensures all new campaign visuals and messaging match the established brand identity.

Do I need specific dependencies to maintain brand consistency across products?

No specific dependencies are required to maintain brand consistency. The skill operates independently by enforcing the usage of internal files like design-tokens.json, tech-stack.md, and voice-tone.md to govern branding across products.