architecture-blueprint-generator

Name: architecture-blueprint-generator
Author: github

11kinstalls4.6kforks

How to install architecture-blueprint-generator?

github/awesome-copilot/architecture-blueprint-generator

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

Installs into the current project.

Summary

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible

Files · 1

View on GitHub

SKILL.md

1	# Comprehensive Project Architecture Blueprint Generator
2
3	## Configuration Variables
4	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|React\|Angular\|Python\|Node.js\|Flutter\|Other"} <!-- Primary technology -->
5	${ARCHITECTURE_PATTERN="Auto-detect\|Clean Architecture\|Microservices\|Layered\|MVVM\|MVC\|Hexagonal\|Event-Driven\|Serverless\|Monolithic\|Other"} <!-- Primary architectural pattern -->
6	${DIAGRAM_TYPE="C4\|UML\|Flow\|Component\|None"} <!-- Architecture diagram type -->
7	${DETAIL_LEVEL="High-level\|Detailed\|Comprehensive\|Implementation-Ready"} <!-- Level of detail to include -->
8	${INCLUDES_CODE_EXAMPLES=true\|false} <!-- Include sample code to illustrate patterns -->
9	${INCLUDES_IMPLEMENTATION_PATTERNS=true\|false} <!-- Include detailed implementation patterns -->
10	${INCLUDES_DECISION_RECORDS=true\|false} <!-- Include architectural decision records -->
11	${FOCUS_ON_EXTENSIBILITY=true\|false} <!-- Emphasize extension points and patterns -->
12
13	## Generated Prompt
14
15	"Create a comprehensive 'Project_Architecture_Blueprint.md' document that thoroughly analyzes the architectural patterns in the codebase to serve as a definitive reference for maintaining architectural consistency. Use the following approach:
16
17	### 1. Architecture Detection and Analysis
18	- ${PROJECT_TYPE == "Auto-detect" ? "Analyze the project structure to identify all technology stacks and frameworks in use by examining:
19	- Project and configuration files
20	- Package dependencies and import statements
21	- Framework-specific patterns and conventions
22	- Build and deployment configurations" : "Focus on ${PROJECT_TYPE} specific patterns and practices"}
23
24	- ${ARCHITECTURE_PATTERN == "Auto-detect" ? "Determine the architectural pattern(s) by analyzing:
25	- Folder organization and namespacing
26	- Dependency flow and component boundaries
27	- Interface segregation and abstraction patterns
28	- Communication mechanisms between components" : "Document how the ${ARCHITECTURE_PATTERN} architecture is implemented"}
29
30	### 2. Architectural Overview
31	- Provide a clear, concise explanation of the overall architectural approach
32	- Document the guiding principles evident in the architectural choices
33	- Identify architectural boundaries and how they're enforced
34	- Note any hybrid architectural patterns or adaptations of standard patterns
35
36	### 3. Architecture Visualization
37	${DIAGRAM_TYPE != "None" ? `Create ${DIAGRAM_TYPE} diagrams at multiple levels of abstraction:
38	- High-level architectural overview showing major subsystems
39	- Component interaction diagrams showing relationships and dependencies
40	- Data flow diagrams showing how information moves through the system
41	- Ensure diagrams accurately reflect the actual implementation, not theoretical patterns` : "Describe the component relationships based on actual code dependencies, providing clear textual explanations of:
42	- Subsystem organization and boundaries
43	- Dependency directions and component interactions
44	- Data flow and process sequences"}
45
46	### 4. Core Architectural Components
47	For each architectural component discovered in the codebase:
48
49	- Purpose and Responsibility:
50	- Primary function within the architecture
51	- Business domains or technical concerns addressed
52	- Boundaries and scope limitations
53
54	- Internal Structure:
55	- Organization of classes/modules within the component
56	- Key abstractions and their implementations
57	- Design patterns utilized
58
59	- Interaction Patterns:
60	- How the component communicates with others
61	- Interfaces exposed and consumed
62	- Dependency injection patterns
63	- Event publishing/subscription mechanisms
64
65	- Evolution Patterns:
66	- How the component can be extended
67	- Variation points and plugin mechanisms
68	- Configuration and customization approaches
69
70	### 5. Architectural Layers and Dependencies
71	- Map the layer structure as implemented in the codebase
72	- Document the dependency rules between layers
73	- Identify abstraction mechanisms that enable layer separation
74	- Note any circular dependencies or layer violations
75	- Document dependency injection patterns used to maintain separation
76
77	### 6. Data Architecture
78	- Document domain model structure and organization
79	- Map entity relationships and aggregation patterns
80	- Identify data access patterns (repositories, data mappers, etc.)
81	- Document data transformation and mapping approaches
82	- Note caching strategies and implementations
83	- Document data validation patterns
84
85	### 7. Cross-Cutting Concerns Implementation
86	Document implementation patterns for cross-cutting concerns:
87
88	- Authentication & Authorization:
89	- Security model implementation
90	- Pe

People who liked this also viewed

6 picks

Type

architecture-blueprint-generator

11kinstalls4.6kforks

View on GitHub

How to install architecture-blueprint-generator?

github/awesome-copilot/architecture-blueprint-generator

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Comprehensive Project Architecture Blueprint Generator
2
3	## Configuration Variables
4	${PROJECT_TYPE="Auto-detect\|.NET\|Java\|React\|Angular\|Python\|Node.js\|Flutter\|Other"} <!-- Primary technology -->
5	${ARCHITECTURE_PATTERN="Auto-detect\|Clean Architecture\|Microservices\|Layered\|MVVM\|MVC\|Hexagonal\|Event-Driven\|Serverless\|Monolithic\|Other"} <!-- Primary architectural pattern -->
6	${DIAGRAM_TYPE="C4\|UML\|Flow\|Component\|None"} <!-- Architecture diagram type -->
7	${DETAIL_LEVEL="High-level\|Detailed\|Comprehensive\|Implementation-Ready"} <!-- Level of detail to include -->
8	${INCLUDES_CODE_EXAMPLES=true\|false} <!-- Include sample code to illustrate patterns -->
9	${INCLUDES_IMPLEMENTATION_PATTERNS=true\|false} <!-- Include detailed implementation patterns -->
10	${INCLUDES_DECISION_RECORDS=true\|false} <!-- Include architectural decision records -->
11	${FOCUS_ON_EXTENSIBILITY=true\|false} <!-- Emphasize extension points and patterns -->
12
13	## Generated Prompt
14
15	"Create a comprehensive 'Project_Architecture_Blueprint.md' document that thoroughly analyzes the architectural patterns in the codebase to serve as a definitive reference for maintaining architectural consistency. Use the following approach:
16
17	### 1. Architecture Detection and Analysis
18	- ${PROJECT_TYPE == "Auto-detect" ? "Analyze the project structure to identify all technology stacks and frameworks in use by examining:
19	- Project and configuration files
20	- Package dependencies and import statements
21	- Framework-specific patterns and conventions
22	- Build and deployment configurations" : "Focus on ${PROJECT_TYPE} specific patterns and practices"}
23
24	- ${ARCHITECTURE_PATTERN == "Auto-detect" ? "Determine the architectural pattern(s) by analyzing:
25	- Folder organization and namespacing
26	- Dependency flow and component boundaries
27	- Interface segregation and abstraction patterns
28	- Communication mechanisms between components" : "Document how the ${ARCHITECTURE_PATTERN} architecture is implemented"}
29
30	### 2. Architectural Overview
31	- Provide a clear, concise explanation of the overall architectural approach
32	- Document the guiding principles evident in the architectural choices
33	- Identify architectural boundaries and how they're enforced
34	- Note any hybrid architectural patterns or adaptations of standard patterns
35
36	### 3. Architecture Visualization
37	${DIAGRAM_TYPE != "None" ? `Create ${DIAGRAM_TYPE} diagrams at multiple levels of abstraction:
38	- High-level architectural overview showing major subsystems
39	- Component interaction diagrams showing relationships and dependencies
40	- Data flow diagrams showing how information moves through the system
41	- Ensure diagrams accurately reflect the actual implementation, not theoretical patterns` : "Describe the component relationships based on actual code dependencies, providing clear textual explanations of:
42	- Subsystem organization and boundaries
43	- Dependency directions and component interactions
44	- Data flow and process sequences"}
45
46	### 4. Core Architectural Components
47	For each architectural component discovered in the codebase:
48
49	- Purpose and Responsibility:
50	- Primary function within the architecture
51	- Business domains or technical concerns addressed
52	- Boundaries and scope limitations
53
54	- Internal Structure:
55	- Organization of classes/modules within the component
56	- Key abstractions and their implementations
57	- Design patterns utilized
58
59	- Interaction Patterns:
60	- How the component communicates with others
61	- Interfaces exposed and consumed
62	- Dependency injection patterns
63	- Event publishing/subscription mechanisms
64
65	- Evolution Patterns:
66	- How the component can be extended
67	- Variation points and plugin mechanisms
68	- Configuration and customization approaches
69
70	### 5. Architectural Layers and Dependencies
71	- Map the layer structure as implemented in the codebase
72	- Document the dependency rules between layers
73	- Identify abstraction mechanisms that enable layer separation
74	- Note any circular dependencies or layer violations
75	- Document dependency injection patterns used to maintain separation
76
77	### 6. Data Architecture
78	- Document domain model structure and organization
79	- Map entity relationships and aggregation patterns
80	- Identify data access patterns (repositories, data mappers, etc.)
81	- Document data transformation and mapping approaches
82	- Note caching strategies and implementations
83	- Document data validation patterns
84
85	### 7. Cross-Cutting Concerns Implementation
86	Document implementation patterns for cross-cutting concerns:
87
88	- Authentication & Authorization:
89	- Security model implementation
90	- Pe

People who liked this also viewed

6 picks

Type