AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Brand Architecture

skill-arnabbagxd-brand-building-skills-brand-architecture · by arnabbagxd

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 ex…

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-arnabbagxd-brand-building-skills-brand-architecture

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-arnabbagxd-brand-building-skills-brand-architecture)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Brand Architecture? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.