What problem does it solve? Teams struggle to keep code organization consistent as projects grow, and new contributors often cannot tell where files belong. This Skill analyzes a repository's folder structure and produces a definitive Project_Folders_Structure_Blueprint.md document that records conventions, patterns, and placement rules. ## Core Features & Use Cases - Auto-Detection of Project Type: Scans for signature files (.sln, pom.xml, package.json, pubspec.yaml, angular.json) to identify .NET, Java, React, Angular, Python, Node.js, or Flutter projects, plus monorepo and microservices indicators. - Configurable Output: Control visualization style (ASCII tree, Markdown list, or table), depth level, file counts, naming conventions, and whether to include generated folders or extension templates. - Comprehensive Blueprint Sections: Covers directory analysis, file placement patterns, naming conventions, build/output organization, technology-specific structures, and templates for adding new features, components, services, and tests. - Use Case: A lead engineer onboarding a team to a large .NET and React monorepo runs this Skill to generate a blueprint documenting where controllers, components, tests, and configuration files belong, so every new feature follows the same structure. ## Quick Start Ask the AI to analyze this repository's folder structure and generate a Project_Folders_Structure_Blueprint.md documenting the directory organization and naming conventions.
