add-domain

Add a knowledge domain with configuration, templates, and vocabulary.

Updated Feb 3, 2026

Search Tags:#cross-domain #modular-architecture #knowledge-domain #domain-extension #hub-moc #vocabulary-mapping

Ready to run

npx skills add https://github.com/LopeWale/amplLABS --skill add-domain-lopewale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-domain
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/add-domain
Command: npx skills add https://github.com/LopeWale/amplLABS --skill add-domain-lopewale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add a new knowledge domain to your existing system, enabling domain-driven extension without disrupting current architecture.

Core Features & Use Cases

Derives domain-specific configuration through guided conversation and generates domain folders, templates, and vocabulary while preserving and connecting to your existing architecture.
Performs multi-domain composition validation and updates hub MOC, context, and derivation documents to reflect the new domain.
Supports optional resources (scripts, references, assets) loaded on demand during domain setup and operation.

Quick Start

Provide a domain hint to begin the multi-phase domain addition workflow.

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 knowledge domain without breaking my existing modular architecture?▼

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.

What is domain-driven extension and how does it handle cross-domain linking?▼

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.

How do I configure a new knowledge domain and generate its vocabulary step by step?▼

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.

Does adding a knowledge domain support optional resources like scripts and references?▼

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.

When should I perform collision checks during domain extension?▼

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.

Why do I need to update context and derivation documents when adding a domain?▼

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.