domain-expert

Domain knowledge extraction builds a glossary by analyzing project files like CLAUDE.md and README.md. It infers entities, relationships, and rules from documentation and code, generating a structured domain knowledge configuration with deterministic results.

Domain-driven design mapping links business concepts to code locations by analyzing software projects. It maps real-world requests to specific code references, identifying inferred entities and relationships to bridge the gap between domain terminology and implementation.

Yes, generating a domain model from a software project is possible without manual entity writing. The system learns domain models by analyzing code and documentation, automatically extracting and inferring entities, relationships, and rules into a structured configuration.

The best way to discover domain rules and terminology across projects is through systematic code and documentation analysis. Running a configure mode extracts the glossary and entities from key files, establishing consistent domain-driven design practices.

Code analysis for domain discovery works across software projects by operating in configure, learn, explain, and map modes. It requires no specific dependencies, reading directly from existing documentation and code to produce structured domain knowledge outputs.

Inferred domain entities become inconsistent when mapping domain concepts if documentation lacks clear terminology. The tool extracts glossary and entities directly from docs and code, so incomplete or ambiguous source material yields fragmented domain knowledge configurations.