project-structure

The best way to organize a monorepo project structure is by applying framework-aware conventions, detecting anti-patterns, and suggesting feature-based or layer-based structures to colocate related components, tests, and types within a feature or module.

You can audit your codebase for common architecture anti-patterns by running a workflow-driven audit that surfaces structural pitfalls like deep nesting, barrels, and scattered utilities, then producing prioritized recommendations and actionable fixes.

Choosing between feature-based and layer-based code organization depends on your framework-aware conventions, as this Skill provides pattern-driven recommendations for grouping related files across both frontend and backend projects to maximize maintainability.

Yes, the project structure audit works with multi-language repositories, applying framework-aware conventions to guide colocated components, grouping strategies, and architectural patterns across diverse codebases.

To implement colocation guidance, the Skill audits your codebase to recommend optimal placement of files and modules, ensuring related components, tests, and types are grouped within a specific feature or module directory.