What problem does it solve? Sokrates' default folder-depth-1 component view is wrong for most repositories: one folder holding 95% of the code, hundreds of fragments, or a src/ split that matches nothing anyone thinks in. This Skill produces logicalDecompositions that match how teams actually divide the codebase, so component size, dependency, duplication, and ownership views become meaningful. ## Core Features & Use Cases - Measured proposals: A script evaluates folder-depth, mixed-depth, build-modules (Cargo, Maven, Gradle, npm workspaces, Bazel, Go, Python, .NET), grouped-modules, CODEOWNERS ownership, architectural layers, and technology candidates against the real tree, scoring each for balance and emitting ready-to-paste config. - Guided composition: Rules of thumb for choosing the primary decomposition vocabulary (modules, domains, teams, layers), targeting 5-25 components with no dominant share, plus secondary decompositions like by-layer or by-team. - Verification workflow: Mandatory preview with the repo-config checker to eliminate Multiple Classifications, Unclassified files, and regex errors before writing config. - Use Case: A monorepo with 80 Cargo crates shows one giant component in Sokrates. Run the proposal script, group modules using an architecture-scan component map into 12 named components, verify with the preview, and get dependency and duplication views that reflect the real structure. ## Quick Start Ask the AI to propose better Sokrates component decompositions for this repository and write them into _sokrates/config.json.
