Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. USE FOR: growing frontend trees; naming, folder, or file-placement policy; CI checks for frontend layout drift. DO NOT USE FOR: semantic code bugs, type errors, or framework API misuse; CSS, HTML, or JS rule enforcement inside files. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, l
SkillScore80Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
Without skill40%
With skill80%
Checks it passed that the model alone missed
Specifies npx chous init.
Returns status as improved.
Returns status as configured.
and 8 more in the full report
11 fixed9 passed either way4 still failing1 broke
Pass-rate lift
+40 pp
Tokens
-9%
Agent turns
0%
Response time
-60%
Model gemini-3.6-flashMeasured 8/19/2026v120 of 25 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
If a developer prefers installing the frontend structure linter globally across their system rather than using npx, what command should be executed?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies npm install -g chous.
Missed
Passed
case-18 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md93 linessingle file
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/, or packages/
architectural drift in the frontend file tree is a larger problem than syntax errors
Do Not Use For
semantic code bugs, type errors, or framework API misuse
CSS, HTML, or JS rule enforcement inside files
very small repos where a structure linter would add more ceremony than value
Inputs
the nearest AGENTS.md
package.json
any existing .chous file
the frontend tree that needs policy enforcement
Workflow
Define the structure problem first:
naming convention drift
component placement
forbidden folders or files
monorepo frontend boundaries
Start from chous init or a known preset, then tighten only the rules the repo can explain.
Keep the checked-in .chous file readable enough that future contributors understand the policy.
Add repeatable commands such as:
npx chous
Exclude generated folders, build artifacts, and vendored assets so the signal stays architectural.
Use Chous as a supplement to semantic linters, not as their replacement.
Re-run after moves or refactors to confirm the structure policy still matches the intended design.