Generates project folder structure blueprints with auto-detection for .NET, Java, React, Angular, Python, Node.js, Flutter. Includes visualizations, naming conventions, patterns, and templates for consistent organization.
From awesome-copilotnpx claudepluginhub ctr26/dotfiles --plugin awesome-copilotThis skill uses the workspace's default tool permissions.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
${PROJECT_TYPE="Auto-detect|.NET|Java|React|Angular|Python|Node.js|Flutter|Other"}
<!-- Select primary technology -->${INCLUDES_MICROSERVICES="Auto-detect|true|false"}
<!-- Is this a microservices architecture? -->${INCLUDES_FRONTEND="Auto-detect|true|false"}
<!-- Does project include frontend components? -->${IS_MONOREPO="Auto-detect|true|false"}
<!-- Is this a monorepo with multiple projects? -->${VISUALIZATION_STYLE="ASCII|Markdown List|Table"}
<!-- How to visualize the structure -->${DEPTH_LEVEL=1-5}
<!-- How many levels of folders to document in detail -->${INCLUDE_FILE_COUNTS=true|false}
<!-- Include file count statistics -->${INCLUDE_GENERATED_FOLDERS=true|false}
<!-- Include auto-generated folders -->${INCLUDE_FILE_PATTERNS=true|false}
<!-- Document file naming/location patterns -->${INCLUDE_TEMPLATES=true|false}
<!-- Include file/folder templates for new features -->"Analyze the project's folder structure and create a comprehensive 'Project_Folders_Structure_Blueprint.md' document that serves as a definitive guide for maintaining consistent code organization. Use the following approach:
${PROJECT_TYPE == "Auto-detect" ? "Begin by scanning the folder structure for key files that identify the project type:
${IS_MONOREPO == "Auto-detect" ? "Determine if this is a monorepo by looking for:
${INCLUDES_MICROSERVICES == "Auto-detect" ? "Check for microservices architecture indicators:
${INCLUDES_FRONTEND == "Auto-detect" ? "Identify frontend components by looking for:
Provide a high-level overview of the ${PROJECT_TYPE == "Auto-detect" ? "detected project type(s)" : PROJECT_TYPE} project's organization principles and folder structure:
${IS_MONOREPO == "Auto-detect" ? "If detected as a monorepo, explain how the monorepo is organized and the relationship between projects." : IS_MONOREPO ? "Explain how the monorepo is organized and the relationship between projects." : ""}
${INCLUDES_MICROSERVICES == "Auto-detect" ? "If microservices are detected, describe how they are structured and organized." : INCLUDES_MICROSERVICES ? "Describe how the microservices are structured and organized." : ""}
${VISUALIZATION_STYLE == "ASCII" ? "Create an ASCII tree representation of the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
${VISUALIZATION_STYLE == "Markdown List" ? "Use nested markdown lists to represent the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
${VISUALIZATION_STYLE == "Table" ? "Create a table with columns for Path, Purpose, Content Types, and Conventions." : ""}
${INCLUDE_GENERATED_FOLDERS ? "Include all folders including generated ones." : "Exclude auto-generated folders like bin/, obj/, node_modules/, etc."}
Document each significant directory's purpose, contents, and patterns:
${PROJECT_TYPE == "Auto-detect" ? "For each detected technology, analyze directory structures based on observed usage patterns:" : ""}
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ? "#### .NET Project Structure (if detected)
Solution Organization:
Project Organization:
Domain/Feature Organization:
Layer Organization:
Configuration Management:
Test Project Organization:
${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ? "#### UI Project Structure (if detected)
Component Organization:
State Management:
Routing Organization:
API Integration:
Asset Management:
Style Organization:
${INCLUDE_FILE_PATTERNS ? "Document the patterns that determine where different types of files should be placed:
Configuration Files:
Model/Entity Definitions:
Business Logic:
Interface Definitions:
Test Files:
Documentation Files:
Document the naming and organizational conventions observed across the project:
File Naming Patterns:
Folder Naming Patterns:
Namespace/Module Patterns:
Organizational Patterns:
Provide guidance for navigating and working with the codebase structure:
Entry Points:
Common Development Tasks:
Dependency Patterns:
${INCLUDE_FILE_COUNTS ? "- Content Statistics:
Document the build process and output organization:
Build Configuration:
Output Structure:
Environment-Specific Builds:
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ? "#### .NET-Specific Structure Patterns (if detected)
Project File Organization:
Assembly Organization:
Resource Organization:
Package Management:
${(PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect") ? "#### Java-Specific Structure Patterns (if detected)
Package Hierarchy:
Build Tool Organization:
Resource Organization:
${(PROJECT_TYPE == "Node.js" || PROJECT_TYPE == "Auto-detect") ? "#### Node.js-Specific Structure Patterns (if detected)
Module Organization:
Script Organization:
Configuration Management:
Document how the project structure is designed to be extended:
Extension Points:
Scalability Patterns:
Refactoring Patterns:
${INCLUDE_TEMPLATES ? "### 10. Structure Templates
Provide templates for creating new components that follow project conventions:
New Feature Template:
New Component Template:
New Service Template:
New Test Structure:
Document how the project structure is maintained and enforced:
Structure Validation:
Documentation Practices:
Include a section at the end about maintaining this blueprint and when it was last updated. "