chous
Chous adds architectural guardrails to growing frontend codebases in .NET projects by linting folder structure, naming conventions, and file placement against a checked-in policy. It runs as a CLI gate to catch layout drift before it compounds, complementing semantic linters without replacing them. Use it when structure policy matters more than syntax enforcement.
Chous enforces frontend folder naming and file placement rules in .NET projects via CLI-based structure linting.
AI-generated summary based on this skill's SKILL.md
Install
managedcode/dotnet-skills/chous · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/Chous/skills/chous ~/.claude/skills/chousnpx skillfed install managedcode/dotnet-skills/chousFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does chous do for frontend file structure linting in .NET?
Chous enforces frontend folder naming and file placement rules in .NET projects by linting folder structure, naming conventions, and file placement against a checked-in policy. It runs as a CLI gate to catch layout drift before it compounds, complementing semantic linters without replacing them.
How does chous prevent frontend architectural drift?
Chous prevents architectural drift in growing frontend codebases via CLI checks that validate folder structure and naming conventions against your defined policy. By catching layout violations early, it stops structure chaos from compounding as teams scale and codebases grow.
Can chous be added as a CI gate for file layout consistency?
Yes. Chous is designed to add file-structure linting gates to CI/CD pipelines. Run it as a check before merge to enforce folder organization rules and prevent non-compliant layouts from reaching main branches.
Does chous enforce src/ apps/ packages/ structure?
Chous validates monorepo frontend boundaries and structure policies through checked-in configuration. You define your preferred structure—whether src/, apps/, packages/, or custom layouts—and chous enforces it across your codebase.
How does chous complement ESLint and other semantic linters?
Chous supplements semantic linters with folder layout compliance validation. While ESLint checks code syntax and semantics, chous validates the physical organization of your frontend files and directories, addressing architectural concerns that syntax linters cannot.
What license does chous use?
Chous is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial projects.
SKILL.md
rendered from the published skill — quoted content, verbatim
Chous for Frontend File-Structure Linting in .NET Repositories
Trigger On
- the repo has a growing frontend tree and the user asks about naming conventions, folder structure, or file placement rules
- the repo wants to enforce layout policy for
ClientApp/,src/,apps/, orpackages/ - architectural drift in the frontend file tree is a larger problem than syntax errors
Do Not Use For
-
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
catalog/Tools/Chous/skills/chous/SKILL.md
catalog/Tools/Chous/skills/chous/manifest.json