technology-stack-blueprint-generator
installsforks
How to install technology-stack-blueprint-generator?
github/awesome-copilot/technology-stack-blueprint-generator
$npx -y skills add github/awesome-copilot --skill technology-stack-blueprint-generatorComprehensive technology stack blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks, programming languages, and implementation patterns across multiple platforms (.NET, Java, JavaScript, React, Python)
SKILL.md
| 1 | # Comprehensive Technology Stack Blueprint Generator |
| 2 | |
| 3 | ## Configuration Variables |
| 4 | ${PROJECT_TYPE="Auto-detect|.NET|Java|JavaScript|React.js|React Native|Angular|Python|Other"} <!-- Primary technology --> |
| 5 | ${DEPTH_LEVEL="Basic|Standard|Comprehensive|Implementation-Ready"} <!-- Analysis depth --> |
| 6 | ${INCLUDE_VERSIONS=true|false} <!-- Include version information --> |
| 7 | ${INCLUDE_LICENSES=true|false} <!-- Include license information --> |
| 8 | ${INCLUDE_DIAGRAMS=true|false} <!-- Generate architecture diagrams --> |
| 9 | ${INCLUDE_USAGE_PATTERNS=true|false} <!-- Include code usage patterns --> |
| 10 | ${INCLUDE_CONVENTIONS=true|false} <!-- Document coding conventions --> |
| 11 | ${OUTPUT_FORMAT="Markdown|JSON|YAML|HTML"} <!-- Select output format --> |
| 12 | ${CATEGORIZATION="Technology Type|Layer|Purpose"} <!-- Organization method --> |
| 13 | |
| 14 | ## Generated Prompt |
| 15 | |
| 16 | "Analyze the codebase and generate a ${DEPTH_LEVEL} technology stack blueprint that thoroughly documents technologies and implementation patterns to facilitate consistent code generation. Use the following approach: |
| 17 | |
| 18 | ### 1. Technology Identification Phase |
| 19 | - ${PROJECT_TYPE == "Auto-detect" ? "Scan the codebase for project files, configuration files, and dependencies to determine all technology stacks in use" : "Focus on ${PROJECT_TYPE} technologies"} |
| 20 | - Identify all programming languages by examining file extensions and content |
| 21 | - Analyze configuration files (package.json, .csproj, pom.xml, etc.) to extract dependencies |
| 22 | - Examine build scripts and pipeline definitions for tooling information |
| 23 | - ${INCLUDE_VERSIONS ? "Extract precise version information from package files and configuration" : "Skip version details"} |
| 24 | - ${INCLUDE_LICENSES ? "Document license information for all dependencies" : ""} |
| 25 | |
| 26 | ### 2. Core Technologies Analysis |
| 27 | |
| 28 | ${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? "#### .NET Stack Analysis (if detected) |
| 29 | - Target frameworks and language versions (detect from project files) |
| 30 | - All NuGet package references with versions and purpose comments |
| 31 | - Project structure and organization patterns |
| 32 | - Configuration approach (appsettings.json, IOptions, etc.) |
| 33 | - Authentication mechanisms (Identity, JWT, etc.) |
| 34 | - API design patterns (REST, GraphQL, minimal APIs, etc.) |
| 35 | - Data access approaches (EF Core, Dapper, etc.) |
| 36 | - Dependency injection patterns |
| 37 | - Middleware pipeline components" : ""} |
| 38 | |
| 39 | ${PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect" ? "#### Java Stack Analysis (if detected) |
| 40 | - JDK version and core frameworks |
| 41 | - All Maven/Gradle dependencies with versions and purpose |
| 42 | - Package structure organization |
| 43 | - Spring Boot usage and configurations |
| 44 | - Annotation patterns |
| 45 | - Dependency injection approach |
| 46 | - Data access technologies (JPA, JDBC, etc.) |
| 47 | - API design (Spring MVC, JAX-RS, etc.)" : ""} |
| 48 | |
| 49 | ${PROJECT_TYPE == "JavaScript" || PROJECT_TYPE == "Auto-detect" ? "#### JavaScript Stack Analysis (if detected) |
| 50 | - ECMAScript version and transpiler settings |
| 51 | - All npm dependencies categorized by purpose |
| 52 | - Module system (ESM, CommonJS) |
| 53 | - Build tooling (webpack, Vite, etc.) with configuration |
| 54 | - TypeScript usage and configuration |
| 55 | - Testing frameworks and patterns" : ""} |
| 56 | |
| 57 | ${PROJECT_TYPE == "React.js" || PROJECT_TYPE == "Auto-detect" ? "#### React Analysis (if detected) |
| 58 | - React version and key patterns (hooks vs class components) |
| 59 | - State management approach (Context, Redux, Zustand, etc.) |
| 60 | - Component library usage (Material-UI, Chakra, etc.) |
| 61 | - Routing implementation |
| 62 | - Form handling strategies |
| 63 | - API integration patterns |
| 64 | - Testing approach for components" : ""} |
| 65 | |
| 66 | ${PROJECT_TYPE == "Python" || PROJECT_TYPE == "Auto-detect" ? "#### Python Analysis (if detected) |
| 67 | - Python version and key language features used |
| 68 | - Package dependencies and virtual environment setup |
| 69 | - Web framework details (Django, Flask, FastAPI) |
| 70 | - ORM usage patterns |
| 71 | - Project structure organization |
| 72 | - API design patterns" : ""} |
| 73 | |
| 74 | ### 3. Implementation Patterns & Conventions |
| 75 | ${INCLUDE_CONVENTIONS ? |
| 76 | "Document coding conventions and patterns for each technology area: |
| 77 | |
| 78 | #### Naming Conventions |
| 79 | - Class/type naming patterns |
| 80 | - Method/function naming patterns |
| 81 | - Variable naming conventions |
| 82 | - File naming and organization conventions |
| 83 | - Interface/abstract class patterns |
| 84 | |
| 85 | #### Code Organization |
| 86 | - File structure and organization |
| 87 | - Folder hierarchy patterns |
| 88 | - Component/module boundaries |
| 89 | - Code separation and responsibility patterns |
| 90 | |
| 91 | #### Common Patterns |
| 92 | - Error handling approaches |
| 93 | - Logging patterns |
| 94 | - Con |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
