Why are barrel files (index.ts) discouraged by this skill?

Barrel files often break tree-shaking in modern bundlers like Vite, leading to larger bundle sizes, and frequently cause circular dependency issues and slower build times.

What is the maximum nesting depth allowed?

The skill enforces a maximum of 4 levels from the src/ or app/ directory to ensure the codebase remains navigable and prevents overly complex directory hierarchies.

Can this skill handle both frontend and backend projects?

Yes, it contains specialized validation patterns for both React/Next.js (frontend) and FastAPI (backend) ecosystems, including rules for hooks, components, routers, and services.

What is a blocking validation rule?

A blocking rule means the skill will explicitly flag and prevent actions that violate the project structure standards, ensuring zero-tolerance for architectural drift during development.

How does the unidirectional import rule work?

It enforces a strict hierarchy where code can only import from lower-level layers (e.g., features can import from shared, but shared cannot import from features), preventing spaghetti code.

Project Structure Enforcer

Name: Project Structure Enforcer
Author: yonatangross

byyonatangross

•

開発者ツール

Enforces modern folder structure standards and architectural integrity through strict blocking validation rules.

概要

The Project Structure Enforcer skill automates the maintenance of high-quality codebase architecture by enforcing 2026 standards for React and FastAPI projects. It proactively prevents architectural debt by blocking deep directory nesting, eliminating problematic barrel files, and validating strict unidirectional import patterns. Whether you are scaling a feature-based frontend or a layered backend, this skill ensures that every file resides in its correct domain-specific location, maintaining a clean, navigable, and performant project structure that scales without rot.

主な機能

Automated architectural reviews to prevent cross-feature dependency leakage
27 GitHub stars
Elimination of barrel files to optimize tree-shaking and build times
Blocking validation for maximum nesting depth (4 levels from root)
Domain-specific file placement rules for React components and FastAPI routers
Enforcement of unidirectional import flows (shared → features → app)

ユースケース

Maintaining architectural consistency in large-scale React/Next.js monorepos
Preventing circular dependencies and tree-shaking issues in modern frontend builds
Enforcing layered separation of concerns in FastAPI backend microservices

概要

主な機能

Automated architectural reviews to prevent cross-feature dependency leakage
27 GitHub stars
Elimination of barrel files to optimize tree-shaking and build times
Blocking validation for maximum nesting depth (4 levels from root)
Domain-specific file placement rules for React components and FastAPI routers
Enforcement of unidirectional import flows (shared → features → app)

ユースケース

Maintaining architectural consistency in large-scale React/Next.js monorepos
Preventing circular dependencies and tree-shaking issues in modern frontend builds
Enforcing layered separation of concerns in FastAPI backend microservices