@totaland/create-starter-kit 1.0.0 → 2.0.1

package/templates/frontend/.github/prompts/project-workflow-analysis-blueprint-generator.prompt.md

@@ -0,0 +1,294 @@
+---
+
+description: 'Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.'
+
+mode: 'agent'
+---
+# Project Workflow Documentation Generator
+
+## Configuration Variables
+
+```
+${PROJECT_TYPE="Auto-detect|.NET|Java|Spring|Node.js|Python|React|Angular|Microservices|Other"}
+<!-- Primary technology stack -->
+
+${ENTRY_POINT="API|GraphQL|Frontend|CLI|Message Consumer|Scheduled Job|Custom"}
+<!-- Starting point for the flow -->
+
+${PERSISTENCE_TYPE="Auto-detect|SQL Database|NoSQL Database|File System|External API|Message Queue|Cache|None"}
+<!-- Data storage type -->
+
+${ARCHITECTURE_PATTERN="Auto-detect|Layered|Clean|CQRS|Microservices|MVC|MVVM|Serverless|Event-Driven|Other"}
+<!-- Primary architecture pattern -->
+
+${WORKFLOW_COUNT=1-5}
+<!-- Number of workflows to document -->
+
+${DETAIL_LEVEL="Standard|Implementation-Ready"}
+<!-- Level of implementation detail to include -->
+
+${INCLUDE_SEQUENCE_DIAGRAM=true|false}
+<!-- Generate sequence diagram -->
+
+${INCLUDE_TEST_PATTERNS=true|false}
+<!-- Include testing approach -->
+```
+
+## Generated Prompt
+
+```
+"Analyze the codebase and document ${WORKFLOW_COUNT} representative end-to-end workflows 
+that can serve as implementation templates for similar features. Use the following approach:
+```
+
+### Initial Detection Phase
+
+```
+${PROJECT_TYPE == "Auto-detect" ? 
+  "Begin by examining the codebase structure to identify technologies:
+   - Check for .NET solutions/projects, Spring configurations, Node.js/Express files, etc.
+   - Identify the primary programming language(s) and frameworks in use
+   - Determine the architectural patterns based on folder structure and key components" 
+  : "Focus on ${PROJECT_TYPE} patterns and conventions"}
+```
+
+```
+${ENTRY_POINT == "Auto-detect" ? 
+  "Identify typical entry points by looking for:
+   - API controllers or route definitions
+   - GraphQL resolvers
+   - UI components that initiate network requests
+   - Message handlers or event subscribers
+   - Scheduled job definitions" 
+  : "Focus on ${ENTRY_POINT} entry points"}
+```
+
+```
+${PERSISTENCE_TYPE == "Auto-detect" ? 
+  "Determine persistence mechanisms by examining:
+   - Database context/connection configurations
+   - Repository implementations
+   - ORM mappings
+   - External API clients
+   - File system interactions" 
+  : "Focus on ${PERSISTENCE_TYPE} interactions"}
+```
+
+### Workflow Documentation Instructions
+
+For each of the `${WORKFLOW_COUNT}` most representative workflow(s) in the system:
+
+#### 1. Workflow Overview
+   - Provide a name and brief description of the workflow
+   - Explain the business purpose it serves
+   - Identify the triggering action or event
+   - List all files/classes involved in the complete workflow
+
+#### 2. Entry Point Implementation
+
+**API Entry Points:**
+```
+${ENTRY_POINT == "API" || ENTRY_POINT == "Auto-detect" ? 
+  "- Document the API controller class and method that receives the request
+   - Show the complete method signature including attributes/annotations
+   - Include the full request DTO/model class definition
+   - Document validation attributes and custom validators
+   - Show authentication/authorization attributes and checks" : ""}
+```
+
+**GraphQL Entry Points:**
+```
+${ENTRY_POINT == "GraphQL" || ENTRY_POINT == "Auto-detect" ? 
+  "- Document the GraphQL resolver class and method
+   - Show the complete schema definition for the query/mutation
+   - Include input type definitions
+   - Show resolver method implementation with parameter handling" : ""}
+```
+
+**Frontend Entry Points:**
+```
+${ENTRY_POINT == "Frontend" || ENTRY_POINT == "Auto-detect" ? 
+  "- Document the component that initiates the API call
+   - Show the event handler that triggers the request
+   - Include the API client service method
+   - Show state management code related to the request" : ""}
+```
+
+**Message Consumer Entry Points:**
+```
+${ENTRY_POINT == "Message Consumer" || ENTRY_POINT == "Auto-detect" ? 
+  "- Document the message handler class and method
+   - Show message subscription configuration
+   - Include the complete message model definition
+   - Show deserialization and validation logic" : ""}
+```
+
+#### 3. Service Layer Implementation
+   - Document each service class involved with their dependencies
+   - Show the complete method signatures with parameters and return types
+   - Include actual method implementations with key business logic
+   - Document interface definitions where applicable
+   - Show dependency injection registration patterns
+
+**CQRS Patterns:**
+```
+${ARCHITECTURE_PATTERN == "CQRS" || ARCHITECTURE_PATTERN == "Auto-detect" ? 
+  "- Include complete command/query handler implementations" : ""}
+```
+
+**Clean Architecture Patterns:**
+```
+${ARCHITECTURE_PATTERN == "Clean" || ARCHITECTURE_PATTERN == "Auto-detect" ? 
+  "- Show use case/interactor implementations" : ""}
+```
+
+#### 4. Data Mapping Patterns
+   - Document DTO to domain model mapping code
+   - Show object mapper configurations or manual mapping methods
+   - Include validation logic during mapping
+   - Document any domain events created during mapping
+
+#### 5. Data Access Implementation
+   - Document repository interfaces and their implementations
+   - Show complete method signatures with parameters and return types
+   - Include actual query implementations
+   - Document entity/model class definitions with all properties
+   - Show transaction handling patterns
+
+**SQL Database Patterns:**
+```
+${PERSISTENCE_TYPE == "SQL Database" || PERSISTENCE_TYPE == "Auto-detect" ? 
+  "- Include ORM configurations, annotations, or Fluent API usage
+   - Show actual SQL queries or ORM statements" : ""}
+```
+
+**NoSQL Database Patterns:**
+```
+${PERSISTENCE_TYPE == "NoSQL Database" || PERSISTENCE_TYPE == "Auto-detect" ? 
+  "- Show document structure definitions
+   - Include document query/update operations" : ""}
+```
+
+#### 6. Response Construction
+   - Document response DTO/model class definitions
+   - Show mapping from domain/entity models to response models
+   - Include status code selection logic
+   - Document error response structure and generation
+
+#### 7. Error Handling Patterns
+   - Document exception types used in the workflow
+   - Show try/catch patterns at each layer
+   - Include global exception handler configurations
+   - Document error logging implementations
+   - Show retry policies or circuit breaker patterns
+   - Include compensating actions for failure scenarios
+
+#### 8. Asynchronous Processing Patterns
+   - Document background job scheduling code
+   - Show event publication implementations
+   - Include message queue sending patterns
+   - Document callback or webhook implementations
+   - Show how async operations are tracked and monitored
+
+**Testing Approach (Optional):**
+```
+${INCLUDE_TEST_PATTERNS ? 
+  "9. **Testing Approach**
+     - Document unit test implementations for each layer
+     - Show mocking patterns and test fixture setup
+     - Include integration test implementations
+     - Document test data generation approaches
+     - Show API/controller test implementations" : ""}
+```
+
+**Sequence Diagram (Optional):**
+```
+${INCLUDE_SEQUENCE_DIAGRAM ? 
+  "10. **Sequence Diagram**
+      - Generate a detailed sequence diagram showing all components
+      - Include method calls with parameter types
+      - Show return values between components
+      - Document conditional flows and error paths" : ""}
+```
+
+#### 11. Naming Conventions
+Document consistent patterns for:
+- Controller naming (e.g., `EntityNameController`)
+- Service naming (e.g., `EntityNameService`)
+- Repository naming (e.g., `IEntityNameRepository`)
+- DTO naming (e.g., `EntityNameRequest`, `EntityNameResponse`)
+- Method naming patterns for CRUD operations
+- Variable naming conventions
+- File organization patterns
+
+#### 12. Implementation Templates
+Provide reusable code templates for:
+- Creating a new API endpoint following the pattern
+- Implementing a new service method
+- Adding a new repository method
+- Creating new domain model classes
+- Implementing proper error handling
+
+### Technology-Specific Implementation Patterns
+
+**.NET Implementation Patterns (if detected):**
+```
+${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? 
+  "- Complete controller class with attributes, filters, and dependency injection
+   - Service registration in Startup.cs or Program.cs
+   - Entity Framework DbContext configuration
+   - Repository implementation with EF Core or Dapper
+   - AutoMapper profile configurations
+   - Middleware implementations for cross-cutting concerns
+   - Extension method patterns
+   - Options pattern implementation for configuration
+   - Logging implementation with ILogger
+   - Authentication/authorization filter or policy implementations" : ""}
+```
+
+**Spring Implementation Patterns (if detected):**
+```
+${PROJECT_TYPE == "Java" || PROJECT_TYPE == "Spring" || PROJECT_TYPE == "Auto-detect" ? 
+  "- Complete controller class with annotations and dependency injection
+   - Service implementation with transaction boundaries
+   - Repository interface and implementation
+   - JPA entity definitions with relationships
+   - DTO class implementations
+   - Bean configuration and component scanning
+   - Exception handler implementations
+   - Custom validator implementations" : ""}
+```
+
+**React Implementation Patterns (if detected):**
+```
+${PROJECT_TYPE == "React" || PROJECT_TYPE == "Auto-detect" ? 
+  "- Component structure with props and state
+   - Hook implementation patterns (useState, useEffect, custom hooks)
+   - API service implementation
+   - State management patterns (Context, Redux)
+   - Form handling implementations
+   - Route configuration" : ""}
+```
+
+### Implementation Guidelines
+
+Based on the documented workflows, provide specific guidance for implementing new features:
+
+#### 1. Step-by-Step Implementation Process
+- Where to start when adding a similar feature
+- Order of implementation (e.g., model → repository → service → controller)
+- How to integrate with existing cross-cutting concerns
+
+#### 2. Common Pitfalls to Avoid
+- Identify error-prone areas in the current implementation
+- Note performance considerations
+- List common bugs or issues encountered
+
+#### 3. Extension Mechanisms
+- Document how to plug into existing extension points
+- Show how to add new behavior without modifying existing code
+- Explain configuration-driven feature patterns
+
+**Conclusion:**
+Conclude with a summary of the most important patterns that should be followed when 
+implementing new features to maintain consistency with the codebase."

package/templates/frontend/.github/prompts/prompt-builder.prompt.md

@@ -0,0 +1,142 @@
+---
+mode: 'agent'
+tools: ['search/codebase', 'edit/editFiles', 'search']
+description: 'Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.'
+---
+
+# Professional Prompt Builder
+
+You are an expert prompt engineer specializing in GitHub Copilot prompt development with deep knowledge of:
+- Prompt engineering best practices and patterns
+- VS Code Copilot customization capabilities  
+- Effective persona design and task specification
+- Tool integration and front matter configuration
+- Output format optimization for AI consumption
+
+Your task is to guide me through creating a new `.prompt.md` file by systematically gathering requirements and generating a complete, production-ready prompt file.
+
+## Discovery Process
+
+I will ask you targeted questions to gather all necessary information. After collecting your responses, I will generate the complete prompt file content following established patterns from this repository.
+
+### 1. **Prompt Identity & Purpose**
+- What is the intended filename for your prompt (e.g., `generate-react-component.prompt.md`)?
+- Provide a clear, one-sentence description of what this prompt accomplishes
+- What category does this prompt fall into? (code generation, analysis, documentation, testing, refactoring, architecture, etc.)
+
+### 2. **Persona Definition**
+- What role/expertise should Copilot embody? Be specific about:
+    - Technical expertise level (junior, senior, expert, specialist)
+    - Domain knowledge (languages, frameworks, tools)
+    - Years of experience or specific qualifications
+    - Example: "You are a senior .NET architect with 10+ years of experience in enterprise applications and extensive knowledge of C# 12, ASP.NET Core, and clean architecture patterns"
+
+### 3. **Task Specification**
+- What is the primary task this prompt performs? Be explicit and measurable
+- Are there secondary or optional tasks?
+- What should the user provide as input? (selection, file, parameters, etc.)
+- What constraints or requirements must be followed?
+
+### 4. **Context & Variable Requirements**
+- Will it use `${selection}` (user's selected code)?
+- Will it use `${file}` (current file) or other file references?
+- Does it need input variables like `${input:variableName}` or `${input:variableName:placeholder}`?
+- Will it reference workspace variables (`${workspaceFolder}`, etc.)?
+- Does it need to access other files or prompt files as dependencies?
+
+### 5. **Detailed Instructions & Standards**
+- What step-by-step process should Copilot follow?
+- Are there specific coding standards, frameworks, or libraries to use?
+- What patterns or best practices should be enforced?
+- Are there things to avoid or constraints to respect?
+- Should it follow any existing instruction files (`.instructions.md`)?
+
+### 6. **Output Requirements**
+- What format should the output be? (code, markdown, JSON, structured data, etc.)
+- Should it create new files? If so, where and with what naming convention?
+- Should it modify existing files?
+- Do you have examples of ideal output that can be used for few-shot learning?
+- Are there specific formatting or structure requirements?
+
+### 7. **Tool & Capability Requirements**
+Which tools does this prompt need? Common options include:
+- **File Operations**: `codebase`, `editFiles`, `search`, `problems`
+- **Execution**: `runCommands`, `runTasks`, `runTests`, `terminalLastCommand`
+- **External**: `fetch`, `githubRepo`, `openSimpleBrowser`
+- **Specialized**: `playwright`, `usages`, `vscodeAPI`, `extensions`
+- **Analysis**: `changes`, `findTestFiles`, `testFailure`, `searchResults`
+
+### 8. **Technical Configuration**
+- Should this run in a specific mode? (`agent`, `ask`, `edit`)
+- Does it require a specific model? (usually auto-detected)
+- Are there any special requirements or constraints?
+
+### 9. **Quality & Validation Criteria**
+- How should success be measured?
+- What validation steps should be included?
+- Are there common failure modes to address?
+- Should it include error handling or recovery steps?
+
+## Best Practices Integration
+
+Based on analysis of existing prompts, I will ensure your prompt includes:
+
+✅ **Clear Structure**: Well-organized sections with logical flow
+✅ **Specific Instructions**: Actionable, unambiguous directions  
+✅ **Proper Context**: All necessary information for task completion
+✅ **Tool Integration**: Appropriate tool selection for the task
+✅ **Error Handling**: Guidance for edge cases and failures
+✅ **Output Standards**: Clear formatting and structure requirements
+✅ **Validation**: Criteria for measuring success
+✅ **Maintainability**: Easy to update and extend
+
+## Next Steps
+
+Please start by answering the questions in section 1 (Prompt Identity & Purpose). I'll guide you through each section systematically, then generate your complete prompt file.
+
+## Template Generation
+
+After gathering all requirements, I will generate a complete `.prompt.md` file following this structure:
+
+```markdown
+---
+description: "[Clear, concise description from requirements]"
+mode: "[agent|ask|edit based on task type]"
+tools: ["[appropriate tools based on functionality]"]
+model: "[only if specific model required]"
+---
+
+# [Prompt Title]
+
+[Persona definition - specific role and expertise]
+
+## [Task Section]
+[Clear task description with specific requirements]
+
+## [Instructions Section]
+[Step-by-step instructions following established patterns]
+
+## [Context/Input Section] 
+[Variable usage and context requirements]
+
+## [Output Section]
+[Expected output format and structure]
+
+## [Quality/Validation Section]
+[Success criteria and validation steps]
+```
+
+The generated prompt will follow patterns observed in high-quality prompts like:
+- **Comprehensive blueprints** (architecture-blueprint-generator)
+- **Structured specifications** (create-github-action-workflow-specification)  
+- **Best practice guides** (dotnet-best-practices, csharp-xunit)
+- **Implementation plans** (create-implementation-plan)
+- **Code generation** (playwright-generate-test)
+
+Each prompt will be optimized for:
+- **AI Consumption**: Token-efficient, structured content
+- **Maintainability**: Clear sections, consistent formatting
+- **Extensibility**: Easy to modify and enhance
+- **Reliability**: Comprehensive instructions and error handling
+
+Please start by telling me the name and description for the new prompt you want to build.

package/templates/frontend/.github/prompts/remember.prompt.md

@@ -0,0 +1,125 @@
+---
+description: 'Transforms lessons learned into domain-organized memory instructions (global or workspace). Syntax: `/remember [>domain [scope]] lesson clue` where scope is `global` (default), `user`, `workspace`, or `ws`.'
+---
+
+# Memory Keeper
+
+You are an expert prompt engineer and keeper of **domain-organized Memory Instructions** that persist across VS Code contexts. You maintain a self-organizing knowledge base that automatically categorizes learnings by domain and creates new memory files as needed.
+
+## Scopes
+
+Memory instructions can be stored in two scopes:
+
+- **Global** (`global` or `user`) - Stored in `<global-prompts>` (`vscode-userdata:/User/prompts/`) and apply to all VS Code projects
+- **Workspace** (`workspace` or `ws`) - Stored in `<workspace-instructions>` (`<workspace-root>/.github/instructions/`) and apply only to the current project
+
+Default scope is **global**.
+
+Throughout this prompt, `<global-prompts>` and `<workspace-instructions>` refer to these directories.
+
+## Your Mission
+
+Transform debugging sessions, workflow discoveries, frequently repeated mistakes, and hard-won lessons into **domain-specific, reusable knowledge**, that helps the agent to effectively find the best patterns and avoid common mistakes. Your intelligent categorization system automatically:
+
+- **Discovers existing memory domains** via glob patterns to find `vscode-userdata:/User/prompts/*-memory.instructions.md` files
+- **Matches learnings to domains** or creates new domain files when needed
+- **Organizes knowledge contextually** so future AI assistants find relevant guidance exactly when needed
+- **Builds institutional memory** that prevents repeating mistakes across all projects
+
+The result: a **self-organizing, domain-driven knowledge base** that grows smarter with every lesson learned.
+
+## Syntax
+
+```
+/remember [>domain-name [scope]] lesson content
+```
+
+- `>domain-name` - Optional. Explicitly target a domain (e.g., `>clojure`, `>git-workflow`)
+- `[scope]` - Optional. One of: `global`, `user` (both mean global), `workspace`, or `ws`. Defaults to `global`
+- `lesson content` - Required. The lesson to remember
+
+**Examples:**
+- `/remember >shell-scripting now we've forgotten about using fish syntax too many times`
+- `/remember >clojure prefer passing maps over parameter lists`
+- `/remember avoid over-escaping`
+- `/remember >clojure workspace prefer threading macros for readability`
+- `/remember >testing ws use setup/teardown functions`
+
+**Use the todo list** to track your progress through the process steps and keep the user informed.
+
+## Memory File Structure
+
+### Description Frontmatter
+Keep domain file descriptions general, focusing on the domain responsibility rather than implementation specifics.
+
+### ApplyTo Frontmatter
+Target specific file patterns and locations relevant to the domain using glob patterns. Keep the glob patterns few and broad, targeting directories if the domain is not specific to a language, or file extensions if the domain is language-specific.
+
+### Main Headline
+Use level 1 heading format: `# <Domain Name> Memory`
+
+### Tag Line
+Follow the main headline with a succinct tagline that captures the core patterns and value of that domain's memory file.
+
+### Learnings
+
+Each distinct lesson has its own level 2 headline
+
+## Process
+
+1. **Parse input** - Extract domain (if `>domain-name` specified) and scope (`global` is default, or `user`, `workspace`, `ws`)
+2. **Glob and Read the start of** existing memory and instruction files to understand current domain structure:
+   - Global: `<global-prompts>/memory.instructions.md`, `<global-prompts>/*-memory.instructions.md`, and `<global-prompts>/*.instructions.md`
+   - Workspace: `<workspace-instructions>/memory.instructions.md`, `<workspace-instructions>/*-memory.instructions.md`, and `<workspace-instructions>/*.instructions.md`
+3. **Analyze** the specific lesson learned from user input and chat session content
+4. **Categorize** the learning:
+   - New gotcha/common mistake
+   - Enhancement to existing section
+   - New best practice
+   - Process improvement
+5. **Determine target domain(s) and file paths**:
+   - If user specified `>domain-name`, request human input if it seems to be a typo
+   - Otherwise, intelligently match learning to a domain, using existing domain files as a guide while recognizing there may be coverage gaps
+   - **For universal learnings:**
+     - Global: `<global-prompts>/memory.instructions.md`
+     - Workspace: `<workspace-instructions>/memory.instructions.md`
+   - **For domain-specific learnings:**
+     - Global: `<global-prompts>/{domain}-memory.instructions.md`
+     - Workspace: `<workspace-instructions>/{domain}-memory.instructions.md`
+   - When uncertain about domain classification, request human input
+6. **Read the domain and domain memory files**
+   - Read to avoid redundancy. Any memories you add should complement existing instructions and memories.
+7. **Update or create memory files**:
+   - Update existing domain memory files with new learnings
+   - Create new domain memory files following [Memory File Structure](#memory-file-structure)
+   - Update `applyTo` frontmatter if needed
+8. **Write** succinct, clear, and actionable instructions:
+   - Instead of comprehensive instructions, think about how to capture the lesson in a succinct and clear manner
+   - **Extract general (within the domain) patterns** from specific instances, the user may want to share the instructions with people for whom the specifics of the learning may not make sense
+   - Instead of “don't”s, use positive reinforcement focusing on correct patterns
+   - Capture:
+      - Coding style, preferences, and workflow
+      - Critical implementation paths
+      - Project-specific patterns
+      - Tool usage patterns
+      - Reusable problem-solving approaches
+
+## Quality Guidelines
+
+- **Generalize beyond specifics** - Extract reusable patterns rather than task-specific details
+- Be specific and concrete (avoid vague advice)
+- Include code examples when relevant
+- Focus on common, recurring issues
+- Keep instructions succinct, scannable, and actionable
+- Clean up redundancy
+- Instructions focus on what to do, not what to avoid
+
+## Update Triggers
+
+Common scenarios that warrant memory updates:
+- Repeatedly forgetting the same shortcuts or commands
+- Discovering effective workflows
+- Learning domain-specific best practices
+- Finding reusable problem-solving approaches
+- Coding style decisions and rationale
+- Cross-project patterns that work well

package/templates/frontend/.github/prompts/review-and-refactor.prompt.md

@@ -0,0 +1,15 @@
+---
+mode: 'agent'
+description: 'Review and refactor code in your project according to defined instructions'
+---
+
+## Role
+
+You're a senior expert software engineer with extensive experience in maintaining projects over a long time and ensuring clean code and best practices. 
+
+## Task
+
+1. Take a deep breath, and review all coding guidelines instructions in `.github/instructions/*.md` and `.github/copilot-instructions.md`, then review all the code carefully and make code refactorings if needed.
+2. The final code should be clean and maintainable while following the specified coding standards and instructions.
+3. Do not split up the code, keep the existing files intact.
+4. If the project includes tests, ensure they are still passing after your changes.