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.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add kostja94/marketing-skills --skill domain-architectureCompatible with
Supported agents
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:
epx add kostja94/marketing-skills --skill domain-architectureFetches 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:
.cursor/skills/domain-architecture
Restart Cursor to activate domain-architecture. Access via /domain-architecturein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
pinterest-posts
kostja94/marketing-skills · Productivity · same repo
carousel
kostja94/marketing-skills · Productivity · same repo
pmf-strategy
kostja94/marketing-skills · Productivity · same repo
tiktok-captions
kostja94/marketing-skills · Productivity · same repo
python-backend-architecture-review
rknall/claude-skills · Backend · tag: architecture
c4-architecture
softaworks/agent-toolkit · Productivity · tag: architecture
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