@totaland/create-starter-kit 2.0.1 → 2.0.2

package/templates/frontend/.github/prompts/suggest-awesome-github-copilot-chatmodes.prompt.md

@@ -1,71 +0,0 @@
----
-agent: 'agent'
-description: 'Suggest relevant GitHub Copilot Custom Chat Modes files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom chat modes in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
----
-
-# Suggest Awesome GitHub Copilot Custom Chat Modes
-
-Analyze current repository context and suggest relevant Custom Chat Modes files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.chatmodes.md) that are not already available in this repository. Custom Chat Mode files are located in the [chatmodes](https://github.com/github/awesome-copilot/tree/main/chatmodes) folder of the awesome-copilot repository.
-
-## Process
-
-1. **Fetch Available Custom Chat Modes**: Extract Custom Chat Modes list and descriptions from [awesome-copilot README.chatmodes.md](https://github.com/github/awesome-copilot/blob/main/docs/README.chatmodes.md). Must use `#fetch` tool.
-2. **Scan Local Custom Chat Modes**: Discover existing custom chat mode files in `.github/chatmodes/` folder
-3. **Extract Descriptions**: Read front matter from local custom chat mode files to get descriptions
-4. **Analyze Context**: Review chat history, repository files, and current project needs
-5. **Compare Existing**: Check against custom chat modes already available in this repository
-6. **Match Relevance**: Compare available custom chat modes against identified patterns and requirements
-7. **Present Options**: Display relevant custom chat modes with descriptions, rationale, and availability status
-8. **Validate**: Ensure suggested chatmodes would add value not already covered by existing chatmodes
-9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot custom chat modes and similar local custom chat modes
-   **AWAIT** user request to proceed with installation of specific custom chat modes. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
-10. **Download Assets**: For requested chat modes, automatically download and install individual chat modes to `.github/chatmodes/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
-
-## Context Analysis Criteria
-
-🔍 **Repository Patterns**:
-- Programming languages used (.cs, .js, .py, etc.)
-- Framework indicators (ASP.NET, React, Azure, etc.)
-- Project types (web apps, APIs, libraries, tools)
-- Documentation needs (README, specs, ADRs)
-
-🗨️ **Chat History Context**:
-- Recent discussions and pain points
-- Feature requests or implementation needs
-- Code review patterns
-- Development workflow requirements
-
-## Output Format
-
-Display analysis results in structured table comparing awesome-copilot custom chat modes with existing repository custom chat modes:
-
-| Awesome-Copilot Custom Chat Mode | Description | Already Installed | Similar Local Custom Chat Mode | Suggestion Rationale |
-|---------------------------|-------------|-------------------|-------------------------|---------------------|
-| [code-reviewer.chatmode.md](https://github.com/github/awesome-copilot/blob/main/chatmodes/code-reviewer.chatmode.md) | Specialized code review custom chat mode | ❌ No | None | Would enhance development workflow with dedicated code review assistance |
-| [architect.chatmode.md](https://github.com/github/awesome-copilot/blob/main/chatmodes/architect.chatmode.md) | Software architecture guidance | ✅ Yes | azure_principal_architect.chatmode.md | Already covered by existing architecture custom chat modes |
-| [debugging-expert.chatmode.md](https://github.com/github/awesome-copilot/blob/main/chatmodes/debugging-expert.chatmode.md) | Debug assistance custom chat mode | ❌ No | None | Could improve troubleshooting efficiency for development team |
-
-## Local Chatmodes Discovery Process
-
-1. List all `*.chatmode.md` files in `.github/chatmodes/` directory
-2. For each discovered file, read front matter to extract `description`
-3. Build comprehensive inventory of existing chatmodes
-4. Use this inventory to avoid suggesting duplicates
-
-## Requirements
-
-- Use `githubRepo` tool to get content from awesome-copilot repository chatmodes folder
-- Scan local file system for existing chatmodes in `.github/chatmodes/` directory
-- Read YAML front matter from local chatmode files to extract descriptions
-- Compare against existing chatmodes in this repository to avoid duplicates
-- Focus on gaps in current chatmode library coverage
-- Validate that suggested chatmodes align with repository's purpose and standards
-- Provide clear rationale for each suggestion
-- Include links to both awesome-copilot chatmodes and similar local chatmodes
-- Don't provide any additional information or context beyond the table and the analysis
-
-## Icons Reference
-
-- ✅ Already installed in repo
-- ❌ Not installed in repo

package/templates/frontend/.github/prompts/suggest-awesome-github-copilot-collections.prompt.md

@@ -1,149 +0,0 @@
----
-mode: 'agent'
-description: 'Suggest relevant GitHub Copilot collections from the awesome-copilot repository based on current repository context and chat history, providing automatic download and installation of collection assets.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
----
-# Suggest Awesome GitHub Copilot Collections
-
-Analyze current repository context and suggest relevant collections from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md) that would enhance the development workflow for this repository.
-
-## Process
-
-1. **Fetch Available Collections**: Extract collection list and descriptions from [awesome-copilot README.collections.md](https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md). Must use `#fetch` tool.
-2. **Scan Local Assets**: Discover existing prompt files in `prompts/`, instruction files in `instructions/`, and chat modes in `chatmodes/` folders
-3. **Extract Local Descriptions**: Read front matter from local asset files to understand existing capabilities
-4. **Analyze Repository Context**: Review chat history, repository files, programming languages, frameworks, and current project needs
-5. **Match Collection Relevance**: Compare available collections against identified patterns and requirements
-6. **Check Asset Overlap**: For relevant collections, analyze individual items to avoid duplicates with existing repository assets
-7. **Present Collection Options**: Display relevant collections with descriptions, item counts, and rationale for suggestion
-8. **Provide Usage Guidance**: Explain how the installed collection enhances the development workflow
-   **AWAIT** user request to proceed with installation of specific collections. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
-9. **Download Assets**: For requested collections, automatically download and install each individual asset (prompts, instructions, chat modes) to appropriate directories. Do NOT adjust content of the files. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
-
-## Context Analysis Criteria
-
-🔍 **Repository Patterns**:
-- Programming languages used (.cs, .js, .py, .ts, .bicep, .tf, etc.)
-- Framework indicators (ASP.NET, React, Azure, Next.js, Angular, etc.)
-- Project types (web apps, APIs, libraries, tools, infrastructure)
-- Documentation needs (README, specs, ADRs, architectural decisions)
-- Development workflow indicators (CI/CD, testing, deployment)
-
-🗨️ **Chat History Context**:
-- Recent discussions and pain points
-- Feature requests or implementation needs
-- Code review patterns and quality concerns
-- Development workflow requirements and challenges
-- Technology stack and architecture decisions
-
-## Output Format
-
-Display analysis results in structured table showing relevant collections and their potential value:
-
-### Collection Recommendations
-
-| Collection Name | Description | Items | Asset Overlap | Suggestion Rationale |
-|-----------------|-------------|-------|---------------|---------------------|
-| [Azure & Cloud Development](https://github.com/github/awesome-copilot/blob/main/collections/azure-cloud-development.md) | Comprehensive Azure cloud development tools including Infrastructure as Code, serverless functions, architecture patterns, and cost optimization | 15 items | 3 similar | Would enhance Azure development workflow with Bicep, Terraform, and cost optimization tools |
-| [C# .NET Development](https://github.com/github/awesome-copilot/blob/main/collections/csharp-dotnet-development.md) | Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices | 7 items | 2 similar | Already covered by existing .NET-related assets but includes advanced testing patterns |
-| [Testing & Test Automation](https://github.com/github/awesome-copilot/blob/main/collections/testing-automation.md) | Comprehensive collection for writing tests, test automation, and test-driven development | 11 items | 1 similar | Could significantly improve testing practices with TDD guidance and automation tools |
-
-### Asset Analysis for Recommended Collections
-
-For each suggested collection, break down individual assets:
-
-**Azure & Cloud Development Collection Analysis:**
-- ✅ **New Assets (12)**: Azure cost optimization prompts, Bicep planning mode, AVM modules, Logic Apps expert mode
-- ⚠️ **Similar Assets (3)**: Azure DevOps pipelines (similar to existing CI/CD), Terraform (basic overlap), Containerization (Docker basics covered)
-- 🎯 **High Value**: Cost optimization tools, Infrastructure as Code expertise, Azure-specific architectural guidance
-
-**Installation Preview:**
-- Will install to `prompts/`: 4 Azure-specific prompts
-- Will install to `instructions/`: 6 infrastructure and DevOps best practices
-- Will install to `chatmodes/`: 5 specialized Azure expert modes
-
-## Local Asset Discovery Process
-
-1. **Scan Asset Directories**:
-   - List all `*.prompt.md` files in `prompts/` directory
-   - List all `*.instructions.md` files in `instructions/` directory
-   - List all `*.chatmode.md` files in `chatmodes/` directory
-
-2. **Extract Asset Metadata**: For each discovered file, read YAML front matter to extract:
-   - `description` - Primary purpose and functionality
-   - `tools` - Required tools and capabilities
-   - `mode` - Operating mode (for prompts)
-   - `model` - Specific model requirements (for chat modes)
-
-3. **Build Asset Inventory**: Create comprehensive map of existing capabilities organized by:
-   - **Technology Focus**: Programming languages, frameworks, platforms
-   - **Workflow Type**: Development, testing, deployment, documentation, planning
-   - **Specialization Level**: General purpose vs. specialized expert modes
-
-4. **Identify Coverage Gaps**: Compare existing assets against:
-   - Repository technology stack requirements
-   - Development workflow needs indicated by chat history
-   - Industry best practices for identified project types
-   - Missing expertise areas (security, performance, architecture, etc.)
-
-## Collection Asset Download Process
-
-When user confirms a collection installation:
-
-1. **Fetch Collection Manifest**: Get collection YAML from awesome-copilot repository
-2. **Download Individual Assets**: For each item in collection:
-   - Download raw file content from GitHub
-   - Validate file format and front matter structure
-   - Check naming convention compliance
-3. **Install to Appropriate Directories**:
-   - `*.prompt.md` files → `prompts/` directory
-   - `*.instructions.md` files → `instructions/` directory
-   - `*.chatmode.md` files → `chatmodes/` directory
-4. **Avoid Duplicates**: Skip files that are substantially similar to existing assets
-5. **Report Installation**: Provide summary of installed assets and usage instructions
-
-## Requirements
-
-- Use `fetch` tool to get collections data from awesome-copilot repository
-- Use `githubRepo` tool to get individual asset content for download
-- Scan local file system for existing assets in `prompts/`, `instructions/`, and `chatmodes/` directories
-- Read YAML front matter from local asset files to extract descriptions and capabilities
-- Compare collections against repository context to identify relevant matches
-- Focus on collections that fill capability gaps rather than duplicate existing assets
-- Validate that suggested collections align with repository's technology stack and development needs
-- Provide clear rationale for each collection suggestion with specific benefits
-- Enable automatic download and installation of collection assets to appropriate directories
-- Ensure downloaded assets follow repository naming conventions and formatting standards
-- Provide usage guidance explaining how collections enhance the development workflow
-- Include links to both awesome-copilot collections and individual assets within collections
-
-## Collection Installation Workflow
-
-1. **User Confirms Collection**: User selects specific collection(s) for installation
-2. **Fetch Collection Manifest**: Download YAML manifest from awesome-copilot repository
-3. **Asset Download Loop**: For each asset in collection:
-   - Download raw content from GitHub repository
-   - Validate file format and structure
-   - Check for substantial overlap with existing local assets
-   - Install to appropriate directory (`prompts/`, `instructions/`, or `chatmodes/`)
-4. **Installation Summary**: Report installed assets with usage instructions
-5. **Workflow Enhancement Guide**: Explain how the collection improves development capabilities
-
-## Post-Installation Guidance
-
-After installing a collection, provide:
-- **Asset Overview**: List of installed prompts, instructions, and chat modes
-- **Usage Examples**: How to activate and use each type of asset
-- **Workflow Integration**: Best practices for incorporating assets into development process
-- **Customization Tips**: How to modify assets for specific project needs
-- **Related Collections**: Suggestions for complementary collections that work well together
-
-
-## Icons Reference
-
-- ✅ Collection recommended for installation
-- ⚠️ Collection has some asset overlap but still valuable
-- ❌ Collection not recommended (significant overlap or not relevant)
-- 🎯 High-value collection that fills major capability gaps
-- 📁 Collection partially installed (some assets skipped due to duplicates)
-- 🔄 Collection needs customization for repository-specific needs

package/templates/frontend/.github/prompts/suggest-awesome-github-copilot-instructions.prompt.md

@@ -1,88 +0,0 @@
----
-agent: 'agent'
-description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
----
-# Suggest Awesome GitHub Copilot Instructions
-
-Analyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository.
-
-## Process
-
-1. **Fetch Available Instructions**: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool.
-2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder
-3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns
-4. **Analyze Context**: Review chat history, repository files, and current project needs
-5. **Compare Existing**: Check against instructions already available in this repository
-6. **Match Relevance**: Compare available instructions against identified patterns and requirements
-7. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status
-8. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions
-9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
-   **AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
-10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/instructions/` folder. Do NOT adjust content of the files.  Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
-
-## Context Analysis Criteria
-
-🔍 **Repository Patterns**:
-- Programming languages used (.cs, .js, .py, .ts, etc.)
-- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
-- Project types (web apps, APIs, libraries, tools)
-- Development workflow requirements (testing, CI/CD, deployment)
-
-🗨️ **Chat History Context**:
-- Recent discussions and pain points
-- Technology-specific questions
-- Coding standards discussions
-- Development workflow requirements
-
-## Output Format
-
-Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:
-
-| Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale |
-|------------------------------|-------------|-------------------|---------------------------|---------------------|
-| [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) | Blazor development guidelines | ❌ No | blazor.instructions.md | Already covered by existing Blazor instructions |
-| [reactjs.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/reactjs.instructions.md) | ReactJS development standards | ❌ No | None | Would enhance React development with established patterns |
-| [java.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md) | Java development best practices | ❌ No | None | Could improve Java code quality and consistency |
-
-## Local Instructions Discovery Process
-
-1. List all `*.instructions.md` files in the `instructions/` directory
-2. For each discovered file, read front matter to extract `description` and `applyTo` patterns
-3. Build comprehensive inventory of existing instructions with their applicable file patterns
-4. Use this inventory to avoid suggesting duplicates
-
-## File Structure Requirements
-
-Based on GitHub documentation, copilot-instructions files should be:
-- **Repository-wide instructions**: `.github/copilot-instructions.md` (applies to entire repository)
-- **Path-specific instructions**: `.github/instructions/NAME.instructions.md` (applies to specific file patterns via `applyTo` frontmatter)
-- **Community instructions**: `instructions/NAME.instructions.md` (for sharing and distribution)
-
-## Front Matter Structure
-
-Instructions files in awesome-copilot use this front matter format:
-```markdown
----
-description: 'Brief description of what this instruction provides'
-applyTo: '**/*.js,**/*.ts' # Optional: glob patterns for file matching
----
-```
-
-## Requirements
-
-- Use `githubRepo` tool to get content from awesome-copilot repository
-- Scan local file system for existing instructions in `instructions/` directory
-- Read YAML front matter from local instruction files to extract descriptions and `applyTo` patterns
-- Compare against existing instructions in this repository to avoid duplicates
-- Focus on gaps in current instruction library coverage
-- Validate that suggested instructions align with repository's purpose and standards
-- Provide clear rationale for each suggestion
-- Include links to both awesome-copilot instructions and similar local instructions
-- Consider technology stack compatibility and project-specific needs
-- Don't provide any additional information or context beyond the table and the analysis
-
-## Icons Reference
-
-- ✅ Already installed in repo
-- ❌ Not installed in repo

package/templates/frontend/.github/prompts/suggest-awesome-github-copilot-prompts.prompt.md

@@ -1,71 +0,0 @@
----
-mode: 'agent'
-description: 'Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository.'
-tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
----
-# Suggest Awesome GitHub Copilot Prompts
-
-Analyze current repository context and suggest relevant prompt files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.prompts.md) that are not already available in this repository.
-
-## Process
-
-1. **Fetch Available Prompts**: Extract prompt list and descriptions from [awesome-copilot README.prompts.md](https://github.com/github/awesome-copilot/blob/main/docs/README.prompts.md). Must use `#fetch` tool.
-2. **Scan Local Prompts**: Discover existing prompt files in `.github/prompts/` folder
-3. **Extract Descriptions**: Read front matter from local prompt files to get descriptions
-4. **Analyze Context**: Review chat history, repository files, and current project needs
-5. **Compare Existing**: Check against prompts already available in this repository
-6. **Match Relevance**: Compare available prompts against identified patterns and requirements
-7. **Present Options**: Display relevant prompts with descriptions, rationale, and availability status
-8. **Validate**: Ensure suggested prompts would add value not already covered by existing prompts
-9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot prompts and similar local prompts
-   **AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
-10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/prompts/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
-
-## Context Analysis Criteria
-
-🔍 **Repository Patterns**:
-- Programming languages used (.cs, .js, .py, etc.)
-- Framework indicators (ASP.NET, React, Azure, etc.)
-- Project types (web apps, APIs, libraries, tools)
-- Documentation needs (README, specs, ADRs)
-
-🗨️ **Chat History Context**:
-- Recent discussions and pain points
-- Feature requests or implementation needs
-- Code review patterns
-- Development workflow requirements
-
-## Output Format
-
-Display analysis results in structured table comparing awesome-copilot prompts with existing repository prompts:
-
-| Awesome-Copilot Prompt | Description | Already Installed | Similar Local Prompt | Suggestion Rationale |
-|-------------------------|-------------|-------------------|---------------------|---------------------|
-| [code-review.md](https://github.com/github/awesome-copilot/blob/main/prompts/code-review.md) | Automated code review prompts | ❌ No | None | Would enhance development workflow with standardized code review processes |
-| [documentation.md](https://github.com/github/awesome-copilot/blob/main/prompts/documentation.md) | Generate project documentation | ✅ Yes | create_oo_component_documentation.prompt.md | Already covered by existing documentation prompts |
-| [debugging.md](https://github.com/github/awesome-copilot/blob/main/prompts/debugging.md) | Debug assistance prompts | ❌ No | None | Could improve troubleshooting efficiency for development team |
-
-## Local Prompts Discovery Process
-
-1. List all `*.prompt.md` files directory `.github/prompts/`.
-2. For each discovered file, read front matter to extract `description`
-3. Build comprehensive inventory of existing prompts
-4. Use this inventory to avoid suggesting duplicates
-
-## Requirements
-
-- Use `githubRepo` tool to get content from awesome-copilot repository
-- Scan local file system for existing prompts in `.github/prompts/` directory
-- Read YAML front matter from local prompt files to extract descriptions
-- Compare against existing prompts in this repository to avoid duplicates
-- Focus on gaps in current prompt library coverage
-- Validate that suggested prompts align with repository's purpose and standards
-- Provide clear rationale for each suggestion
-- Include links to both awesome-copilot prompts and similar local prompts
-- Don't provide any additional information or context beyond the table and the analysis
-
-
-## Icons Reference
-
-- ✅ Already installed in repo
-- ❌ Not installed in repo

package/templates/frontend/.github/prompts/technology-stack-blueprint-generator.prompt.md

@@ -1,242 +0,0 @@
----
-description: 'Comprehensive 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). Generates configurable blueprints with version information, licensing details, usage patterns, coding conventions, and visual diagrams. Provides implementation-ready templates and maintains architectural consistency for guided development.'
-mode: 'agent'
----
-
-# Comprehensive Technology Stack Blueprint Generator
-
-## Configuration Variables
-${PROJECT_TYPE="Auto-detect|.NET|Java|JavaScript|React.js|React Native|Angular|Python|Other"} <!-- Primary technology -->
-${DEPTH_LEVEL="Basic|Standard|Comprehensive|Implementation-Ready"} <!-- Analysis depth -->
-${INCLUDE_VERSIONS=true|false} <!-- Include version information -->
-${INCLUDE_LICENSES=true|false} <!-- Include license information -->
-${INCLUDE_DIAGRAMS=true|false} <!-- Generate architecture diagrams -->
-${INCLUDE_USAGE_PATTERNS=true|false} <!-- Include code usage patterns -->
-${INCLUDE_CONVENTIONS=true|false} <!-- Document coding conventions -->
-${OUTPUT_FORMAT="Markdown|JSON|YAML|HTML"} <!-- Select output format -->
-${CATEGORIZATION="Technology Type|Layer|Purpose"} <!-- Organization method -->
-
-## Generated Prompt
-
-"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:
-
-### 1. Technology Identification Phase
-- ${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"}
-- Identify all programming languages by examining file extensions and content
-- Analyze configuration files (package.json, .csproj, pom.xml, etc.) to extract dependencies
-- Examine build scripts and pipeline definitions for tooling information
-- ${INCLUDE_VERSIONS ? "Extract precise version information from package files and configuration" : "Skip version details"}
-- ${INCLUDE_LICENSES ? "Document license information for all dependencies" : ""}
-
-### 2. Core Technologies Analysis
-
-${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? "#### .NET Stack Analysis (if detected)
-- Target frameworks and language versions (detect from project files)
-- All NuGet package references with versions and purpose comments
-- Project structure and organization patterns
-- Configuration approach (appsettings.json, IOptions, etc.)
-- Authentication mechanisms (Identity, JWT, etc.)
-- API design patterns (REST, GraphQL, minimal APIs, etc.)
-- Data access approaches (EF Core, Dapper, etc.)
-- Dependency injection patterns
-- Middleware pipeline components" : ""}
-
-${PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect" ? "#### Java Stack Analysis (if detected)
-- JDK version and core frameworks
-- All Maven/Gradle dependencies with versions and purpose
-- Package structure organization
-- Spring Boot usage and configurations
-- Annotation patterns
-- Dependency injection approach
-- Data access technologies (JPA, JDBC, etc.)
-- API design (Spring MVC, JAX-RS, etc.)" : ""}
-
-${PROJECT_TYPE == "JavaScript" || PROJECT_TYPE == "Auto-detect" ? "#### JavaScript Stack Analysis (if detected)
-- ECMAScript version and transpiler settings
-- All npm dependencies categorized by purpose
-- Module system (ESM, CommonJS)
-- Build tooling (webpack, Vite, etc.) with configuration
-- TypeScript usage and configuration
-- Testing frameworks and patterns" : ""}
-
-${PROJECT_TYPE == "React.js" || PROJECT_TYPE == "Auto-detect" ? "#### React Analysis (if detected)
-- React version and key patterns (hooks vs class components)
-- State management approach (Context, Redux, Zustand, etc.)
-- Component library usage (Material-UI, Chakra, etc.)
-- Routing implementation
-- Form handling strategies
-- API integration patterns
-- Testing approach for components" : ""}
-
-${PROJECT_TYPE == "Python" || PROJECT_TYPE == "Auto-detect" ? "#### Python Analysis (if detected)
-- Python version and key language features used
-- Package dependencies and virtual environment setup
-- Web framework details (Django, Flask, FastAPI)
-- ORM usage patterns
-- Project structure organization
-- API design patterns" : ""}
-
-### 3. Implementation Patterns & Conventions
-${INCLUDE_CONVENTIONS ? 
-"Document coding conventions and patterns for each technology area:
-
-#### Naming Conventions
-- Class/type naming patterns
-- Method/function naming patterns
-- Variable naming conventions
-- File naming and organization conventions
-- Interface/abstract class patterns
-
-#### Code Organization
-- File structure and organization
-- Folder hierarchy patterns
-- Component/module boundaries
-- Code separation and responsibility patterns
-
-#### Common Patterns
-- Error handling approaches
-- Logging patterns
-- Configuration access
-- Authentication/authorization implementation
-- Validation strategies
-- Testing patterns" : ""}
-
-### 4. Usage Examples
-${INCLUDE_USAGE_PATTERNS ? 
-"Extract representative code examples showing standard implementation patterns:
-
-#### API Implementation Examples
-- Standard controller/endpoint implementation
-- Request DTO pattern
-- Response formatting
-- Validation approach
-- Error handling
-
-#### Data Access Examples
-- Repository pattern implementation
-- Entity/model definitions
-- Query patterns
-- Transaction handling
-
-#### Service Layer Examples
-- Service class implementation
-- Business logic organization
-- Cross-cutting concerns integration
-- Dependency injection usage
-
-#### UI Component Examples (if applicable)
-- Component structure
-- State management pattern
-- Event handling
-- API integration pattern" : ""}
-
-### 5. Technology Stack Map
-${DEPTH_LEVEL == "Comprehensive" || DEPTH_LEVEL == "Implementation-Ready" ? 
-"Create a comprehensive technology map including:
-
-#### Core Framework Usage
-- Primary frameworks and their specific usage in the project
-- Framework-specific configurations and customizations
-- Extension points and customizations
-
-#### Integration Points
-- How different technology components integrate
-- Authentication flow between components
-- Data flow between frontend and backend
-- Third-party service integration patterns
-
-#### Development Tooling
-- IDE settings and conventions
-- Code analysis tools
-- Linters and formatters with configuration
-- Build and deployment pipeline
-- Testing frameworks and approaches
-
-#### Infrastructure
-- Deployment environment details
-- Container technologies
-- Cloud services utilized
-- Monitoring and logging infrastructure" : ""}
-
-### 6. Technology-Specific Implementation Details
-
-${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? 
-"#### .NET Implementation Details (if detected)
-- **Dependency Injection Pattern**:
-  - Service registration approach (Scoped/Singleton/Transient patterns)
-  - Configuration binding patterns
-  
-- **Controller Patterns**:
-  - Base controller usage
-  - Action result types and patterns
-  - Route attribute conventions
-  - Filter usage (authorization, validation, etc.)
-  
-- **Data Access Patterns**:
-  - ORM configuration and usage
-  - Entity configuration approach
-  - Relationship definitions
-  - Query patterns and optimization approaches
-  
-- **API Design Patterns** (if used):
-  - Endpoint organization
-  - Parameter binding approaches
-  - Response type handling
-  
-- **Language Features Used**:
-  - Detect specific language features from code
-  - Identify common patterns and idioms
-  - Note any specific version-dependent features" : ""}
-
-${PROJECT_TYPE == "React.js" || PROJECT_TYPE == "Auto-detect" ? 
-"#### React Implementation Details (if detected)
-- **Component Structure**:
-  - Function vs class components
-  - Props interface definitions
-  - Component composition patterns
-  
-- **Hook Usage Patterns**:
-  - Custom hook implementation style
-  - useState patterns
-  - useEffect cleanup approaches
-  - Context usage patterns
-  
-- **State Management**:
-  - Local vs global state decisions
-  - State management library patterns
-  - Store configuration
-  - Selector patterns
-  
-- **Styling Approach**:
-  - CSS methodology (CSS modules, styled-components, etc.)
-  - Theme implementation
-  - Responsive design patterns" : ""}
-
-### 7. Blueprint for New Code Implementation
-${DEPTH_LEVEL == "Implementation-Ready" ? 
-"Based on the analysis, provide a detailed blueprint for implementing new features:
-
-- **File/Class Templates**: Standard structure for common component types
-- **Code Snippets**: Ready-to-use code patterns for common operations
-- **Implementation Checklist**: Standard steps for implementing features end-to-end
-- **Integration Points**: How to connect new code with existing systems
-- **Testing Requirements**: Standard test patterns for different component types
-- **Documentation Requirements**: Standard doc patterns for new features" : ""}
-
-${INCLUDE_DIAGRAMS ? 
-"### 8. Technology Relationship Diagrams
-- **Stack Diagram**: Visual representation of the complete technology stack
-- **Dependency Flow**: How different technologies interact
-- **Component Relationships**: How major components depend on each other
-- **Data Flow**: How data flows through the technology stack" : ""}
-
-### ${INCLUDE_DIAGRAMS ? "9" : "8"}. Technology Decision Context
-- Document apparent reasons for technology choices
-- Note any legacy or deprecated technologies marked for replacement
-- Identify technology constraints and boundaries
-- Document technology upgrade paths and compatibility considerations
-
-Format the output as ${OUTPUT_FORMAT} and categorize technologies by ${CATEGORIZATION}.
-
-Save the output as 'Technology_Stack_Blueprint.${OUTPUT_FORMAT == "Markdown" ? "md" : OUTPUT_FORMAT.toLowerCase()}'
-"