add-domain

To add a new knowledge domain safely, this Skill derives domain-specific configuration through guided conversation, generating folders, templates, and vocabulary while preserving your existing modular architecture. It performs collision checks and updates your hub MOC to ensure multi-domain coherence without disrupting current structures.

Domain-driven extension allows you to scale your system by adding new knowledge areas without breaking current structures. Cross-domain linking is handled by updating the hub MOC, context, and derivation documents to validate multi-domain composition and ensure the new domain connects seamlessly to the existing architecture.

You can configure a new knowledge domain by providing a domain hint to start the multi-phase workflow. The system guides you through domain discovery, schema design, and collision checks, ultimately generating domain-specific folders, templates, and vocabulary while enforcing kernel checks to maintain coherence.

Yes, adding a knowledge domain supports optional resources including scripts, references, and assets. These resources are loaded on demand during the domain setup and operation phases, ensuring you can extend the system with necessary auxiliary components without overloading the base architecture.

Collision checks should be performed during the schema design phase of domain extension. This prevents naming or structural conflicts between the new knowledge domain and the existing architecture, ensuring multi-domain composition validation succeeds before you finalize hub updates and cross-domain linking.

Updating context and derivation documents is necessary to reflect the newly added knowledge domain accurately. This ensures the system tracks how the new domain-specific configuration was generated and maintains multi-domain coherence by keeping the hub MOC and architectural records synchronized.