skills.rest
Postpartum-genushyacinthus29
Postpartum-genushyacinthus29COMMUNITY
Explore all skills by this author →
GitHub

dotnet-chous

Enforce frontend file-structure policies in .NET repositories.

8|Updated Mar 29, 2026
Search Tags:#architecture#frontend#dotnet#policy#chous#structure-lint
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-chous
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-chous
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-chous
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-chous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent frontend architecture drift in .NET projects by enforcing a structured file layout and naming conventions through a policy-driven CLI gate.

Core Features & Use Cases

  • Enforces policies on repository frontend trees to ensure ClientApp/, src/, and packages/ adhere to defined structure rules.
  • Integrates with existing linting and CI workflows to detect architectural drift before code review.
  • Use Case: In a large .NET solution with sizable frontend code, apply the Chous-based policy to automatically identify and report violations, enabling quick remediation.

Quick Start

Run chous to initialize and apply the frontend structure policy to your repository.

Frequently Asked Questions about dotnet-chous

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent frontend folder structure drift in a .NET repository?▼

To prevent frontend folder structure drift in a .NET repository, apply a policy-driven CLI gate to enforce defined file layouts, correct naming conventions, and component placement across growing frontend trees.

Can I enforce frontend file naming conventions in .NET projects automatically?▼

Yes, you can enforce frontend file naming conventions in .NET projects automatically by running a structure-lint policy workflow that identifies violations in directories like ClientApp, src, and packages.

How do I integrate frontend architecture policy checks into CI workflows?▼

You integrate frontend architecture policy checks into CI workflows by running the policy CLI gate to detect architectural drift and report file-structure violations before code review.

What is the best way to standardize a large .NET solution's frontend component placement?▼

The best way to standardize a large .NET solution's frontend component placement is to initialize a policy-driven structure-lint workflow that enforces strict folder layout rules and reports placement violations.

Does this structure-lint policy work with existing linting tools in .NET repos?▼

Yes, the structure-lint policy works with existing linting tools by integrating into current CI workflows to detect architectural drift and report structural violations before code review.

Related Skills

Explore More Software Engineering Skills→
krl76krl76

unity-project-scout

Inspect Unity version, packages, asmdefs, and folder structures for baseline assessment.

Community
Intermediate
JamesPrialJamesPrial
3

go-linting

Route Go linting tasks to vet, staticcheck, and golangci-lint.

Community
Intermediate
gcudergcuder
3

harness-generator

Generate agent harnesses with linters, style enforcement, and plan gates.

Community
Advanced
suwandresuwandre

project-structure

Organize React/Next.js/TypeScript projects into feature-based folder structures.

Community
Advanced