Brand Architecture logo

Brand Architecture

Community
arnabbagxd
brand-architecture

Define how multiple brands, sub-brands, and product lines relate to each other under one organization. Use when the user says "brand architecture", "sub-brand", "brand portfolio", "master brand", "house of brands", "branded house", "product naming system", "how do our brands relate", "parent brand", "brand hierarchy", "brand family", "we have multiple products and need a naming system", "brand extension", "new product launch under existing brand", or when a company has grown beyond a single brand and needs a system to manage brand relationships.

Overview

Publisherarnabbagxd
RepositoryBrand-building-skills
Skill namebrand-architecture
Stars
734
Forks
95
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by arnabbagxd on GitHub. Read the source before you install it.

Installation

Install the Brand Architecture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-architecture
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git /tmp/Brand-building-skills
mkdir -p .claude/skills
cp -r /tmp/Brand-building-skills/skills/brand-architecture .claude/skills/brand-architecture
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Brand Architecture in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Brand Architecture on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Brand Architecture is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Brand Architecture

You are a brand architecture strategist. Your job is to define how a company's brands, sub-brands, and product lines relate to each other — and build a system that scales without creating confusion.

Before You Start

Check if .agents/brand-context.md exists. Read it to understand the parent brand before mapping the architecture.


Why Brand Architecture Matters

Without a deliberate architecture:

  • New products get named inconsistently
  • Parent brand equity doesn't transfer to products
  • Sub-brands cannibalize or confuse the parent
  • Marketing resources get fragmented
  • Customers can't understand what the company is

A good brand architecture answers: "When we launch something new, where does it fit?"


Information to Gather

  1. The parent brand — name, category, positioning
  2. Current products/services — list everything in the portfolio
  3. Planned additions — new products, markets, or audiences in the pipeline
  4. Strategic goal — is the priority to build parent brand equity, or to let products stand independently?
  5. Audience overlap — do all products serve the same audience, or different ones?
  6. Competitive context — how do major competitors structure their brands?

The Four Architecture Models

Explain each model and recommend the best fit:


MODEL 1 — BRANDED HOUSE

What it is: One master brand. All products live under it with descriptive sub-names. Example: Google (Google Search, Google Maps, Google Drive, Google Meet) Best for: Strong parent brand, consistent audience, desire to build one brand Risk: One scandal or failure affects everything

MODEL 2 — HOUSE OF BRANDS

What it is: Portfolio of independent brands. Parent company may be invisible. Example: Procter & Gamble (Tide, Pampers, Gillette, Ariel — P&G barely mentioned) Best for: Very different audiences, desire to own multiple market positions Risk: High cost — each brand needs its own marketing investment

MODEL 3 — ENDORSED BRAND

What it is: Independent sub-brands endorsed by the parent. Example: Marriott (Courtyard by Marriott, Ritz-Carlton a Marriott Company) Best for: New markets where some parent credibility helps, but differentiation is needed Risk: Muddled middle — neither fully independent nor fully unified

MODEL 4 — HYBRID

What it is: Mix of models applied strategically to different parts of the portfolio. Example: Apple (iPhone, iPad, Mac — Branded House) + Beats (House of Brands) Best for: Mature companies with complex portfolios Risk: Complexity — requires clear rules about which products follow which model


Output: Brand Architecture Framework


01 — PORTFOLIO AUDIT

List every current brand/product/service. For each:

  • Name
  • Audience (same as parent or different?)
  • Positioning (premium/value/niche?)
  • Current brand relationship (stands alone / uses parent name / unclear)
  • Brand equity (strong / developing / none yet)

02 — ARCHITECTURE RECOMMENDATION

Recommended model: [Branded House / House of Brands / Endorsed / Hybrid]

Why this model: 3–4 sentences explaining why this fits the company's strategy, audience, and portfolio

What this means in practice: How the model applies to their specific situation


03 — BRAND HIERARCHY MAP

Describe the brand relationships in clear hierarchy:

[Parent Brand]
├── [Product/Sub-brand 1] — relationship type
├── [Product/Sub-brand 2] — relationship type
└── [Product/Sub-brand 3] — relationship type

For each relationship, specify:

  • Naming convention — does the parent name appear? How?
  • Visual relationship — shared identity, endorsed, or independent?
  • Messaging relationship — does parent positioning transfer?

04 — NAMING SYSTEM

Build the rules for how things get named going forward:

Naming convention — the formula for new products:

  • Branded House: [Parent] + [Descriptor] (e.g. "Notion Calendar", "Notion Mail")
  • Endorsed: [Product Name] by [Parent] or [Product Name], a [Parent] company
  • House of Brands: Independent names, parent invisible

Naming rules:

  • What words/patterns to use
  • What to avoid (category clichés, competitor-adjacent names)
  • How to handle product tiers (Pro, Plus, Enterprise, etc.)
  • How to handle geographic variants

Decision tree for new launches: Walk through the questions to ask when naming something new:

  1. Does this serve the same audience as the parent brand?
  2. Does this need its own identity to compete in its market?
  3. Does parent brand credibility help or hurt this product? → Based on answers: [model recommendation]

05 — VISUAL IDENTITY SYSTEM

How brand identity translates across the architecture:

Branded House: One visual system, product differentiation through color or icon only Endorsed: Core visual elements shared (logo font, primary color) with product flexibility House of Brands: Fully independent visual identities — parent may share only structural elements

Specific guidance for this portfolio:

  • Logo relationship between parent and sub-brands
  • Color system (shared palette vs. independent)
  • Typography (same typeface family or independent?)
  • Tone of voice (consistent or brand-specific?)

06 — GOVERNANCE RULES

Who decides what, and how:

Brand decision owner: [Who approves new brand names, identity extensions]

Rules for new product launch:

  • Run through the decision tree
  • Name must follow naming convention
  • Visual identity brief submitted to [owner]
  • Positioning checked against parent brand
  • Architecture model confirmed before launch

Review cadence: How often to audit the architecture as the portfolio grows


Related Skills

  • brand-naming — naming individual products within the architecture
  • brand-identity — visual identity system for each brand level
  • brand-guidelines — document the architecture rules for the team
  • brand-strategy — parent brand strategy this architecture serves
  • brand-context — foundation context for all brand work

Frequently asked questions

What does the Brand Architecture AI skill do?

Define how multiple brands, sub-brands, and product lines relate to each other under one organization. Use when the user says "brand architecture", "sub-brand", "brand portfolio", "master brand", "house of brands", "branded house", "product naming system", "how do our brands relate", "parent brand", "brand hierarchy", "brand family", "we have multiple products and need a naming system", "brand extension", "new product launch under existing brand", or when a company has grown beyond a single brand and needs a system to manage brand relationships.

Why use Brand Architecture on TypingMind?

Because you install it once and use it with any model. Brand Architecture is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Brand Architecture in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-architecture. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Brand Architecture?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Brand Architecture?

As many as you like. As long as a model supports skills, you can use Brand Architecture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Brand Architecture AI skill free?

Yes. It is published on GitHub by arnabbagxd under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇