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

Workflow

1. Define the structure problem first:

- naming convention drift - component placement - forbidden folders or files - monorepo frontend boundaries

1. Start from chous init or a known preset, then tighten only the rules the repo can explain.
2. Keep the checked-in .chous file readable enough that future contributors understand the policy.
3. Add repeatable commands such as:

- npx chous

1. Exclude generated folders, build artifacts, and vendored assets so the signal stays architectural.
2. Use Chous as a supplement to semantic linters, not as their replacement.
3. Re-run after moves or refactors to confirm the structure policy still matches the intended design.

Deliver

• a checked-in frontend structure policy
• repeatable file-tree linting commands
• explicit exclusions for generated and vendored folders

Validate

• the .chous rules reflect real architecture intent
• generated output is excluded
• Chous is used alongside, not instead of, semantic linters
• the policy remains understandable after the first rollout

Related skills

Related agents