What problem does it solve? Frontend file trees in .NET repositories drift over time: naming conventions diverge, components land in the wrong folders, and folder layout loses its intended architecture even while ESLint and other semantic linters pass. This Skill sets up Chous as a file-structure linting gate so layout policy is enforced as a repeatable CLI check. ## Core Features & Use Cases - Structure Policy Definition: Initialize a checked-in .chous config from npx chous init or a preset, then tighten only the rules the team can explain. - Repeatable Lint Commands: Add npx chous to package.json and AGENTS.md so file-tree linting runs consistently in local and CI workflows. - Scoped Signal: Exclude generated folders, build artifacts, and vendored assets so the lint output reflects architecture rather than noise. - Use Case: A .NET repo with a growing ClientApp/ tree keeps accumulating inconsistently named components. Use this Skill to define naming and placement rules, wire npx chous into the build, and catch layout drift in pull requests. ## Quick Start Ask the AI to add Chous file-structure linting to the repository's frontend tree and verify it with a repeatable npx chous command.
