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
Decision gist · record as of 2026-07-25
Chous enforces frontend folder naming and file placement rules in .NET projects via CLI-based structure linting. 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.
Use it when
- Chous prevents architectural drift in growing frontend codebases via CLI checks that validate folder structure and naming conventions.
- Yes.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/chous · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 2 files
catalog/Tools/Chous/skills/chous/SKILL.md
catalog/Tools/Chous/skills/chous/manifest.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Enforce frontend folder naming and file placement rules in .NET projects”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
Biome integrates into .NET repositories to provide combined formatting, linting, and import organization across JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML. The skill handles ownership decisions between Biome and existing tools like ESLint or Prettier, generates configuration, and establishes repeatable commands for CI and local development. It guides migration strategies and validates that your build and test flows remain stable after changes.
htmlhint enforces HTML structure and attribute correctness on static files and built output in .NET repositories. Target rendered HTML in folders like wwwroot/ or dist/ rather than raw server-side templates, keeping validation separate from JavaScript and full-site audits.
Metalint aggregates multiple frontend linters into a single CLI entrypoint for .NET repositories with Node-based assets. It delegates to ESLint, Stylelint, HTMLHint, and similar tools while keeping their configs explicit and reviewable under `.metalint/`. Use it when your repo already has multiple linters and needs orchestration, not when a single tool like Biome covers your needs.
webhint runs runtime audits against .NET browser-facing sites, catching accessibility, performance, security header, SEO, and PWA issues that static linters miss. Configure a `.hintrc` baseline, point it at your local or deployed URL, and get categorized findings ready for the team to act on.
More skills cloc (MIT) · stylecop-analyzers (MIT) · complexity (MIT)