folder-structure-blueprint-generator

Name: folder-structure-blueprint-generator
Author: github

9.1kinstalls4.6kforks

How to install folder-structure-blueprint-generator?

github/awesome-copilot/folder-structure-blueprint-generator

$npx -y skills add github/awesome-copilot --skill folder-structure-blueprint-generator

Installs into the current project.

Summary

Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patter

Files · 1

View on GitHub

SKILL.md

1	# Project Folder Structure Blueprint Generator
2
3	## Configuration Variables
4
5	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|React\|Angular\|Python\|Node.js\|Flutter\|Other"}
6	<!-- Select primary technology -->
7
8	${INCLUDES_MICROSERVICES="Auto-detect\|true\|false"}
9	<!-- Is this a microservices architecture? -->
10
11	${INCLUDES_FRONTEND="Auto-detect\|true\|false"}
12	<!-- Does project include frontend components? -->
13
14	${IS_MONOREPO="Auto-detect\|true\|false"}
15	<!-- Is this a monorepo with multiple projects? -->
16
17	${VISUALIZATION_STYLE="ASCII\|Markdown List\|Table"}
18	<!-- How to visualize the structure -->
19
20	${DEPTH_LEVEL=1-5}
21	<!-- How many levels of folders to document in detail -->
22
23	${INCLUDE_FILE_COUNTS=true\|false}
24	<!-- Include file count statistics -->
25
26	${INCLUDE_GENERATED_FOLDERS=true\|false}
27	<!-- Include auto-generated folders -->
28
29	${INCLUDE_FILE_PATTERNS=true\|false}
30	<!-- Document file naming/location patterns -->
31
32	${INCLUDE_TEMPLATES=true\|false}
33	<!-- Include file/folder templates for new features -->
34
35	## Generated Prompt
36
37	"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:
38
39	### Initial Auto-detection Phase
40
41	${PROJECT_TYPE == "Auto-detect" ?
42	"Begin by scanning the folder structure for key files that identify the project type:
43	- Look for solution/project files (.sln, .csproj, .fsproj, .vbproj) to identify .NET projects
44	- Check for build files (pom.xml, build.gradle, settings.gradle) for Java projects
45	- Identify package.json with dependencies for JavaScript/TypeScript projects
46	- Look for specific framework files (angular.json, react-scripts entries, next.config.js)
47	- Check for Python project identifiers (requirements.txt, setup.py, pyproject.toml)
48	- Examine mobile app identifiers (pubspec.yaml, android/ios folders)
49	- Note all technology signatures found and their versions" :
50	"Focus analysis on ${PROJECT_TYPE} project structure"}
51
52	${IS_MONOREPO == "Auto-detect" ?
53	"Determine if this is a monorepo by looking for:
54	- Multiple distinct projects with their own configuration files
55	- Workspace configuration files (lerna.json, nx.json, turborepo.json, etc.)
56	- Cross-project references and shared dependency patterns
57	- Root-level orchestration scripts and configuration" : ""}
58
59	${INCLUDES_MICROSERVICES == "Auto-detect" ?
60	"Check for microservices architecture indicators:
61	- Multiple service directories with similar/repeated structures
62	- Service-specific Dockerfiles or deployment configurations
63	- Inter-service communication patterns (APIs, message brokers)
64	- Service registry or discovery configuration
65	- API gateway configuration files
66	- Shared libraries or utilities across services" : ""}
67
68	${INCLUDES_FRONTEND == "Auto-detect" ?
69	"Identify frontend components by looking for:
70	- Web asset directories (wwwroot, public, dist, static)
71	- UI framework files (components, modules, pages)
72	- Frontend build configuration (webpack, vite, rollup, etc.)
73	- Style sheet organization (CSS, SCSS, styled-components)
74	- Static asset organization (images, fonts, icons)" : ""}
75
76	### 1. Structural Overview
77
78	Provide a high-level overview of the ${PROJECT_TYPE == "Auto-detect" ? "detected project type(s)" : PROJECT_TYPE} project's organization principles and folder structure:
79
80	- Document the overall architectural approach reflected in the folder structure
81	- Identify the main organizational principles (by feature, by layer, by domain, etc.)
82	- Note any structural patterns that repeat throughout the codebase
83	- Document the rationale behind the structure where it can be inferred
84
85	${IS_MONOREPO == "Auto-detect" ?
86	"If detected as a monorepo, explain how the monorepo is organized and the relationship between projects." :
87	IS_MONOREPO ? "Explain how the monorepo is organized and the relationship between projects." : ""}
88
89	${INCLUDES_MICROSERVICES == "Auto-detect" ?
90	"If microservices are detected, describe how they are structured and organized." :
91	INCLUDES_MICROSERVICES ? "Describe how the microservices are structured and organized." : ""}
92
93	### 2. Directory Visualization
94
95	${VISUALIZATION_STYLE == "ASCII" ?
96	"Create an ASCII tree representation of the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
97
98	${VISUALIZATION_STYLE == "Markdown List" ?
99	"Use nested markdown lists to represent the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
100
101	${VISUALIZATION_STYLE == "Table" ?
102	"Create a table with columns for Path, Purpose, Content Types, and Conventions." : ""}

People who liked this also viewed

6 picks

Type

folder-structure-blueprint-generator

9.1kinstalls4.6kforks

View on GitHub

How to install folder-structure-blueprint-generator?

github/awesome-copilot/folder-structure-blueprint-generator

$npx -y skills add github/awesome-copilot --skill folder-structure-blueprint-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Folder Structure Blueprint Generator
2
3	## Configuration Variables
4
5	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|React\|Angular\|Python\|Node.js\|Flutter\|Other"}
6	<!-- Select primary technology -->
7
8	${INCLUDES_MICROSERVICES="Auto-detect\|true\|false"}
9	<!-- Is this a microservices architecture? -->
10
11	${INCLUDES_FRONTEND="Auto-detect\|true\|false"}
12	<!-- Does project include frontend components? -->
13
14	${IS_MONOREPO="Auto-detect\|true\|false"}
15	<!-- Is this a monorepo with multiple projects? -->
16
17	${VISUALIZATION_STYLE="ASCII\|Markdown List\|Table"}
18	<!-- How to visualize the structure -->
19
20	${DEPTH_LEVEL=1-5}
21	<!-- How many levels of folders to document in detail -->
22
23	${INCLUDE_FILE_COUNTS=true\|false}
24	<!-- Include file count statistics -->
25
26	${INCLUDE_GENERATED_FOLDERS=true\|false}
27	<!-- Include auto-generated folders -->
28
29	${INCLUDE_FILE_PATTERNS=true\|false}
30	<!-- Document file naming/location patterns -->
31
32	${INCLUDE_TEMPLATES=true\|false}
33	<!-- Include file/folder templates for new features -->
34
35	## Generated Prompt
36
37	"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:
38
39	### Initial Auto-detection Phase
40
41	${PROJECT_TYPE == "Auto-detect" ?
42	"Begin by scanning the folder structure for key files that identify the project type:
43	- Look for solution/project files (.sln, .csproj, .fsproj, .vbproj) to identify .NET projects
44	- Check for build files (pom.xml, build.gradle, settings.gradle) for Java projects
45	- Identify package.json with dependencies for JavaScript/TypeScript projects
46	- Look for specific framework files (angular.json, react-scripts entries, next.config.js)
47	- Check for Python project identifiers (requirements.txt, setup.py, pyproject.toml)
48	- Examine mobile app identifiers (pubspec.yaml, android/ios folders)
49	- Note all technology signatures found and their versions" :
50	"Focus analysis on ${PROJECT_TYPE} project structure"}
51
52	${IS_MONOREPO == "Auto-detect" ?
53	"Determine if this is a monorepo by looking for:
54	- Multiple distinct projects with their own configuration files
55	- Workspace configuration files (lerna.json, nx.json, turborepo.json, etc.)
56	- Cross-project references and shared dependency patterns
57	- Root-level orchestration scripts and configuration" : ""}
58
59	${INCLUDES_MICROSERVICES == "Auto-detect" ?
60	"Check for microservices architecture indicators:
61	- Multiple service directories with similar/repeated structures
62	- Service-specific Dockerfiles or deployment configurations
63	- Inter-service communication patterns (APIs, message brokers)
64	- Service registry or discovery configuration
65	- API gateway configuration files
66	- Shared libraries or utilities across services" : ""}
67
68	${INCLUDES_FRONTEND == "Auto-detect" ?
69	"Identify frontend components by looking for:
70	- Web asset directories (wwwroot, public, dist, static)
71	- UI framework files (components, modules, pages)
72	- Frontend build configuration (webpack, vite, rollup, etc.)
73	- Style sheet organization (CSS, SCSS, styled-components)
74	- Static asset organization (images, fonts, icons)" : ""}
75
76	### 1. Structural Overview
77
78	Provide a high-level overview of the ${PROJECT_TYPE == "Auto-detect" ? "detected project type(s)" : PROJECT_TYPE} project's organization principles and folder structure:
79
80	- Document the overall architectural approach reflected in the folder structure
81	- Identify the main organizational principles (by feature, by layer, by domain, etc.)
82	- Note any structural patterns that repeat throughout the codebase
83	- Document the rationale behind the structure where it can be inferred
84
85	${IS_MONOREPO == "Auto-detect" ?
86	"If detected as a monorepo, explain how the monorepo is organized and the relationship between projects." :
87	IS_MONOREPO ? "Explain how the monorepo is organized and the relationship between projects." : ""}
88
89	${INCLUDES_MICROSERVICES == "Auto-detect" ?
90	"If microservices are detected, describe how they are structured and organized." :
91	INCLUDES_MICROSERVICES ? "Describe how the microservices are structured and organized." : ""}
92
93	### 2. Directory Visualization
94
95	${VISUALIZATION_STYLE == "ASCII" ?
96	"Create an ASCII tree representation of the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
97
98	${VISUALIZATION_STYLE == "Markdown List" ?
99	"Use nested markdown lists to represent the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
100
101	${VISUALIZATION_STYLE == "Table" ?
102	"Create a table with columns for Path, Purpose, Content Types, and Conventions." : ""}

People who liked this also viewed

6 picks

Type