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 "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
Best use case
domain-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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 "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
Teams using domain-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/domain-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How domain-architecture Compares
| Feature / Agent | domain-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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 "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
multi-domain-brand-seo
When the user wants to optimize brand search for a company with multiple domains (e.g. parent company.com vs product.ai). Ensure the parent/company domain ranks first for brand queries. Also use when the user mentions "brand search," "multi-domain SEO," "company domain first," "parent vs product domain," "hub-spoke domain," "brand SERP control," or "differentiate company and product domains." For domain structure, use domain-architecture.
domain-selection
When the user wants to choose an SEO-friendly domain for a new site—brand vs keyword domain, TLD selection, or domain best practices. Also use when the user mentions "domain choice," "pick domain," "SEO-friendly domain," "brand domain," "EMD," "PMD," "exact match domain," "partial match domain," "TLD," ".ai domain," ".com vs .io," "domain length," "domain history," or "defensive domain registration." For migration, use rebranding-strategy.
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
growth-funnel
When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.