domain-architecture

When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions...

Security Scan

The skill's requests and instructions match its stated purpose (domain-architecture advice); it requires no installs, credentials, or unusual privileges and only suggests reading optional project-context files if present.

Purpose & Capability

Name/description align with the instructions: the SKILL.md contains guidance for choosing subfolder/subdomain/independent domain and related brand-architecture advice. The skill does not request unrelated binaries, env vars, or credentials.

Instruction Scope

Instructions are narrowly scoped to giving domain-architecture recommendations. They do instruct the agent to read .claude/project-context.md or .cursor/project-context.md if present to obtain product/portfolio context; that is relevant to the task but does mean the skill will look at those workspace files when available.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is written to disk or downloaded during install.

Credentials

The skill declares no environment variables, credentials, or config paths. It does not request secrets or unrelated service tokens.

Persistence & Privilege

always is false and the skill is user-invocable (normal). It does not request persistent/system-wide changes or modify other skills' configurations.

Assessment

This skill appears coherent and low-risk: it gives domain-architecture advice and doesn't ask for credentials or install software. Note it will attempt to read .claude/project-context.md or .cursor/project-context.md if those files exist in your workspace to get portfolio context — review those files first if they contain any sensitive information. If you prefer the skill not to access workspace files, remove or sanitize those project-context files before invoking the skill.

Strategy: Domain Architecture

Guides domain structure decisions for multiple products or brands: subfolder (subdirectory), subdomain, or independent domain. Covers brand architecture (Branded House vs House of Brands) and Hub-Spoke principles when multiple domains coexist. See domain-selection for initial domain choice (Brand/PMD/EMD, TLD); website-structure for single-domain page planning; rebranding-strategy for domain change and migration; multi-domain-brand-seo for brand search optimization.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product portfolio and growth goals.

Identify:

1. Product count: Single product vs multiple products/brands
2. Brand strategy: Unified brand vs distinct brands
3. Current state: Planning from scratch vs consolidating existing domains
4. Constraints: Tech stack, team, budget

Domain Structure Options

Structure	Example	SEO Authority	Brand Independence	Typical Use
Subfolder	company.com/product-a	Shared with main domain	Low	Products under one brand; SMB; content consolidation
Subdomain	product.company.com	Treated separately by Google	Medium	Separate product experience; tech isolation; support/docs
Independent domain	product.ai	None shared	High	Acquired brands; different markets; distinct brand identity

When to Use Each

Choose	When
Subfolder	Products share value proposition; want to strengthen main domain; SMB; blog, tools, features under one brand
Subdomain	Need separate tech stack (e.g., app vs marketing); support portal; docs; distinct UX but same brand
Independent domain	House of Brands; acquired company; different audience; different TLD (e.g., .ai for AI product)

SEO consensus: Subfolders typically outperform subdomains for most cases—authority flows to the main domain. Subdomains require separate SEO effort.

Brand Architecture

Model	Description	Domain Tendency	Examples
Branded House	One master brand; products use functional descriptors	Subfolder or subdomain	Google (google.com/search, google.com/maps), FedEx
House of Brands	Each brand independent; parent hidden	Independent domains	Unilever (dove.com, axe.com)
Sub-brands / Endorsed	Sub-brands with parent endorsement	Subdomain or independent	FedEx Express, Marriott Bonvoy

Decision factors: Business strategy, market positioning, product overlap, resource availability.

Hub-Spoke (Multiple Domains Coexist)

When company main site (company.com) and product site (product.ai) both exist:

Role	Domain	Focus
Hub	company.com	Brand, About, Research, product matrix; brand queries
Spoke	product.ai	Product features, pricing, signup; product queries

Principles:

• Hub links to Spoke (Products section); Spoke links back (About, Footer, "A [Company] product")
• Spoke avoids competing for brand queries in Title; Hub avoids competing for product keywords
• See multi-domain-brand-seo for brand search optimization.

Output Format

• Recommendation (subfolder / subdomain / independent) with rationale
• Brand architecture fit (Branded House / House of Brands / Sub-brands)
• Domain mapping (e.g., product A → company.com/product-a)
• Hub-Spoke guidance (if multiple domains)
• Related next steps (website-structure, rebranding-strategy)

Related Skills

• domain-selection: Initial domain choice (Brand/PMD/EMD, TLD); single-site use case
• website-structure: Plan pages within a domain; single-domain structure
• rebranding-strategy: Domain change, 301 redirects, migration
• multi-domain-brand-seo: Brand search control when Hub and Spoke coexist
• branding: Brand strategy, positioning; domain architecture implements brand structure