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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondomain-architectureExecute the skills CLI command in your project's root directory to begin installation:
Fetches domain-architecture from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate domain-architecture. Access via /domain-architecture in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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.
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:
| 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 |
| 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.
| 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.
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:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
neolabhq/context-engineering-kit
domain-architecture has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: domain-architecture is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend domain-architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for domain-architecture matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: domain-architecture is focused, and the summary matches what you get after install.
Useful defaults in domain-architecture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: domain-architecture is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend domain-architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
domain-architecture reduced setup friction for our internal harness; good balance of opinion and flexibility.
domain-architecture has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 41