domain-detection

To detect a repository's project domain, the system scans files, directory names, and config files using a prioritized signal table to classify projects as coding, marketing, legal, or unknown. This automated classification removes guesswork and guides workflow template selection during setup.

When repository signals conflict during project classification, the system aggregates confidence scores and prompts the user to resolve ties. It provides clear explanations of conflicting signals to ensure accurate domain detection and prevent inappropriate template selection.

Yes, you can classify mixed-content repositories by evaluating package managers, config files, directory names, and file extensions in prioritized order. The system produces a confidence-weighted classification to determine if the project is coding, marketing, legal, or unknown.

For repositories with no clear domain match, the system provides fallback protocols offering template choices or a minimal configuration. This enables safe continuation of setup workflows when domain detection cannot confidently classify the project.

Project domain detection works by evaluating existing repository signals including package managers, config files, directory names, and file extensions. No specific file structure is required, as the system applies fallback protocols when signals are insufficient for classification.