add-domain

Add a new domain to a knowledge system with templates and hub links.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hellofrommorgan/intent-computer --skill add-domain-hellofrommorgan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-domain
Source: https://github.com/hellofrommorgan/intent-computer/tree/main/packages/plugin/src/plugin-skills/add-domain
Command: npx skills add https://github.com/hellofrommorgan/intent-computer --skill add-domain-hellofrommorgan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add-domain enables teams to extend an existing knowledge system by introducing a new domain that coexists with current domains while preserving distinct vocabulary, schema, and processing patterns.

Core Features & Use Cases

  • Derives domain-specific configuration through conversation and composition rules.
  • Generates domain folders, templates, and vocabulary, integrating with existing architecture.
  • Updates hub MOC and supports cross-domain linking and coherent multi-domain operation.

Quick Start

Provide the new domain name and a short description, and I will derive the domain configuration, create the domain templates, and link it into the hub.

Frequently Asked Questions about add-domain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new domain to my existing knowledge system?

To add a new domain to your knowledge system, provide the domain name and a short description to derive domain-specific configuration, generate domain templates, and link it into the hub MOC.

What is the best way to manage separate vocabularies in a multi-domain knowledge system?

Managing separate vocabularies in a multi-domain knowledge system requires deriving domain-specific configuration with independent processing rules, ensuring cross-domain linking while preserving distinct schemas for each domain.

How do I update the hub MOC when introducing a new domain?

Updating the hub MOC when introducing a new domain involves generating domain templates, creating hub links, and applying domain guidance to ensure coherent multi-domain operation and cross-domain linking.

Do I need to create separate templates for each domain in a multi-domain knowledge system?

Yes, you need separate templates for each domain in a multi-domain knowledge system to preserve distinct vocabulary, schema, and processing patterns while maintaining alignment with system constraints.

Can I use domain-specific configuration to support cross-domain linking in a knowledge system?

Yes, you can use domain-specific configuration to support cross-domain linking by deriving independent processing rules, updating the hub MOC, and generating domain templates that coexist with current domains.

When should I not use a multi-domain approach for my knowledge system?

You should not use a multi-domain approach if your knowledge system does not require cross-domain linking, separate templates, or domain-specific vocabularies with independent processing rules and system constraint alignment.