workspace-architect 1.3.0

package/assets/prompts/technology-stack-blueprint-generator.prompt.md

@@ -0,0 +1,242 @@
+---
+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()}'
+"

package/assets/prompts/typescript-mcp-server-generator.prompt.md

@@ -0,0 +1,90 @@
+---
+mode: 'agent'
+description: 'Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration'
+---
+
+# Generate TypeScript MCP Server
+
+Create a complete Model Context Protocol (MCP) server in TypeScript with the following specifications:
+
+## Requirements
+
+1. **Project Structure**: Create a new TypeScript/Node.js project with proper directory structure
+2. **NPM Packages**: Include @modelcontextprotocol/sdk, zod@3, and either express (for HTTP) or stdio support
+3. **TypeScript Configuration**: Proper tsconfig.json with ES modules support
+4. **Server Type**: Choose between HTTP (with Streamable HTTP transport) or stdio-based server
+5. **Tools**: Create at least one useful tool with proper schema validation
+6. **Error Handling**: Include comprehensive error handling and validation
+
+## Implementation Details
+
+### Project Setup
+- Initialize with `npm init` and create package.json
+- Install dependencies: `@modelcontextprotocol/sdk`, `zod@3`, and transport-specific packages
+- Configure TypeScript with ES modules: `"type": "module"` in package.json
+- Add dev dependencies: `tsx` or `ts-node` for development
+- Create proper .gitignore file
+
+### Server Configuration
+- Use `McpServer` class for high-level implementation
+- Set server name and version
+- Choose appropriate transport (StreamableHTTPServerTransport or StdioServerTransport)
+- For HTTP: set up Express with proper middleware and error handling
+- For stdio: use StdioServerTransport directly
+
+### Tool Implementation
+- Use `registerTool()` method with descriptive names
+- Define schemas using zod for input and output validation
+- Provide clear `title` and `description` fields
+- Return both `content` and `structuredContent` in results
+- Implement proper error handling with try-catch blocks
+- Support async operations where appropriate
+
+### Resource/Prompt Setup (Optional)
+- Add resources using `registerResource()` with ResourceTemplate for dynamic URIs
+- Add prompts using `registerPrompt()` with argument schemas
+- Consider adding completion support for better UX
+
+### Code Quality
+- Use TypeScript for type safety
+- Follow async/await patterns consistently
+- Implement proper cleanup on transport close events
+- Use environment variables for configuration
+- Add inline comments for complex logic
+- Structure code with clear separation of concerns
+
+## Example Tool Types to Consider
+- Data processing and transformation
+- External API integrations
+- File system operations (read, search, analyze)
+- Database queries
+- Text analysis or summarization (with sampling)
+- System information retrieval
+
+## Configuration Options
+- **For HTTP Servers**: 
+  - Port configuration via environment variables
+  - CORS setup for browser clients
+  - Session management (stateless vs stateful)
+  - DNS rebinding protection for local servers
+  
+- **For stdio Servers**:
+  - Proper stdin/stdout handling
+  - Environment-based configuration
+  - Process lifecycle management
+
+## Testing Guidance
+- Explain how to run the server (`npm start` or `npx tsx server.ts`)
+- Provide MCP Inspector command: `npx @modelcontextprotocol/inspector`
+- For HTTP servers, include connection URL: `http://localhost:PORT/mcp`
+- Include example tool invocations
+- Add troubleshooting tips for common issues
+
+## Additional Features to Consider
+- Sampling support for LLM-powered tools
+- User input elicitation for interactive workflows
+- Dynamic tool registration with enable/disable capabilities
+- Notification debouncing for bulk updates
+- Resource links for efficient data references
+
+Generate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.

package/assets/prompts/update-avm-modules-in-bicep.prompt.md

@@ -0,0 +1,60 @@
+---
+mode: 'agent'
+description: 'Update Azure Verified Modules (AVM) to latest versions in Bicep files.'
+tools: ['search/codebase', 'think', 'changes', 'fetch', 'search/searchResults', 'todos', 'edit/editFiles', 'search', 'runCommands', 'bicepschema', 'azure_get_schema_for_Bicep']
+---
+# Update Azure Verified Modules in Bicep Files
+
+Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final outout table and summary.
+
+## Process
+
+1. **Scan**: Extract AVM modules and current versions from `${file}`
+1. **Identify**: List all unique AVM modules used by matching `avm/res/{service}/{resource}` using `#search` tool
+1. **Check**: Use `#fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
+1. **Compare**: Parse semantic versions to identify AVM modules needing update
+1. **Review**: For breaking changes, use `#fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
+1. **Update**: Apply version updates and parameter changes using `#editFiles` tool
+1. **Validate**: Run `bicep lint` and `bicep build` using `#runCommands` tool to ensure compliance.
+1. **Output**: Summarize changes in a table format with summary of updates below.
+
+## Tool Usage
+
+Always use tools `#search`, `#searchResults`,`#fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks.
+
+## Breaking Change Policy
+
+⚠️ **PAUSE for approval** if updates involve:
+
+- Incompatible parameter changes
+- Security/compliance modifications
+- Behavioral changes
+
+## Output Format
+
+Only display results in table with icons:
+
+```markdown
+| Module | Current | Latest | Status | Action | Docs |
+|--------|---------|--------|--------|--------|------|
+| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) |
+| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |
+
+### Summary of Updates
+
+Describe updates made, any manual reviews needed or issues encountered.
+```
+
+## Icons
+
+- 🔄 Updated
+- ✅ Current
+- ⚠️ Manual review required
+- ❌ Failed
+- 📖 Documentation
+
+## Requirements
+
+- Use MCR tags API only for version discovery
+- Parse JSON tags array and sort by semantic versioning
+- Maintain Bicep file validity and linting compliance

package/assets/prompts/update-implementation-plan.prompt.md

@@ -0,0 +1,157 @@
+---
+mode: 'agent'
+description: 'Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.'
+tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
+---
+# Update Implementation Plan
+
+## Primary Directive
+
+You are an AI agent tasked with updating the implementation plan file `${file}` based on new or updated requirements. Your output must be machine-readable, deterministic, and structured for autonomous execution by other AI systems or humans.
+
+## Execution Context
+
+This prompt is designed for AI-to-AI communication and automated processing. All instructions must be interpreted literally and executed systematically without human interpretation or clarification.
+
+## Core Requirements
+
+- Generate implementation plans that are fully executable by AI agents or humans
+- Use deterministic language with zero ambiguity
+- Structure all content for automated parsing and execution
+- Ensure complete self-containment with no external dependencies for understanding
+
+## Plan Structure Requirements
+
+Plans must consist of discrete, atomic phases containing executable tasks. Each phase must be independently processable by AI agents or humans without cross-phase dependencies unless explicitly declared.
+
+## Phase Architecture
+
+- Each phase must have measurable completion criteria
+- Tasks within phases must be executable in parallel unless dependencies are specified
+- All task descriptions must include specific file paths, function names, and exact implementation details
+- No task should require human interpretation or decision-making
+
+## AI-Optimized Implementation Standards
+
+- Use explicit, unambiguous language with zero interpretation required
+- Structure all content as machine-parseable formats (tables, lists, structured data)
+- Include specific file paths, line numbers, and exact code references where applicable
+- Define all variables, constants, and configuration values explicitly
+- Provide complete context within each task description
+- Use standardized prefixes for all identifiers (REQ-, TASK-, etc.)
+- Include validation criteria that can be automatically verified
+
+## Output File Specifications
+
+- Save implementation plan files in `/plan/` directory
+- Use naming convention: `[purpose]-[component]-[version].md`
+- Purpose prefixes: `upgrade|refactor|feature|data|infrastructure|process|architecture|design`
+- Example: `upgrade-system-command-4.md`, `feature-auth-module-1.md`
+- File must be valid Markdown with proper front matter structure
+
+## Mandatory Template Structure
+
+All implementation plans must strictly adhere to the following template. Each section is required and must be populated with specific, actionable content. AI agents must validate template compliance before execution.
+
+## Template Validation Rules
+
+- All front matter fields must be present and properly formatted
+- All section headers must match exactly (case-sensitive)
+- All identifier prefixes must follow the specified format
+- Tables must include all required columns
+- No placeholder text may remain in the final output
+
+## Status
+
+The status of the implementation plan must be clearly defined in the front matter and must reflect the current state of the plan. The status can be one of the following (status_color in brackets): `Completed` (bright green badge), `In progress` (yellow badge), `Planned` (blue badge), `Deprecated` (red badge), or `On Hold` (orange badge). It should also be displayed as a badge in the introduction section.
+
+```md
+---
+goal: [Concise Title Describing the Package Implementation Plan's Goal]
+version: [Optional: e.g., 1.0, Date]
+date_created: [YYYY-MM-DD]
+last_updated: [Optional: YYYY-MM-DD]
+owner: [Optional: Team/Individual responsible for this spec]
+status: 'Completed'|'In progress'|'Planned'|'Deprecated'|'On Hold'
+tags: [Optional: List of relevant tags or categories, e.g., `feature`, `upgrade`, `chore`, `architecture`, `migration`, `bug` etc]
+---
+
+# Introduction
+
+![Status: <status>](https://img.shields.io/badge/status-<status>-<status_color>)
+
+[A short concise introduction to the plan and the goal it is intended to achieve.]
+
+## 1. Requirements & Constraints
+
+[Explicitly list all requirements & constraints that affect the plan and constrain how it is implemented. Use bullet points or tables for clarity.]
+
+- **REQ-001**: Requirement 1
+- **SEC-001**: Security Requirement 1
+- **[3 LETTERS]-001**: Other Requirement 1
+- **CON-001**: Constraint 1
+- **GUD-001**: Guideline 1
+- **PAT-001**: Pattern to follow 1
+
+## 2. Implementation Steps
+
+### Implementation Phase 1
+
+- GOAL-001: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.]
+
+| Task | Description | Completed | Date |
+|------|-------------|-----------|------|
+| TASK-001 | Description of task 1 | ✅ | 2025-04-25 |
+| TASK-002 | Description of task 2 | |  |
+| TASK-003 | Description of task 3 | |  |
+
+### Implementation Phase 2
+
+- GOAL-002: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.]
+
+| Task | Description | Completed | Date |
+|------|-------------|-----------|------|
+| TASK-004 | Description of task 4 | |  |
+| TASK-005 | Description of task 5 | |  |
+| TASK-006 | Description of task 6 | |  |
+
+## 3. Alternatives
+
+[A bullet point list of any alternative approaches that were considered and why they were not chosen. This helps to provide context and rationale for the chosen approach.]
+
+- **ALT-001**: Alternative approach 1
+- **ALT-002**: Alternative approach 2
+
+## 4. Dependencies
+
+[List any dependencies that need to be addressed, such as libraries, frameworks, or other components that the plan relies on.]
+
+- **DEP-001**: Dependency 1
+- **DEP-002**: Dependency 2
+
+## 5. Files
+
+[List the files that will be affected by the feature or refactoring task.]
+
+- **FILE-001**: Description of file 1
+- **FILE-002**: Description of file 2
+
+## 6. Testing
+
+[List the tests that need to be implemented to verify the feature or refactoring task.]
+
+- **TEST-001**: Description of test 1
+- **TEST-002**: Description of test 2
+
+## 7. Risks & Assumptions
+
+[List any risks or assumptions related to the implementation of the plan.]
+
+- **RISK-001**: Risk 1
+- **ASSUMPTION-001**: Assumption 1
+
+## 8. Related Specifications / Further Reading
+
+[Link to related spec 1]
+[Link to relevant external documentation]
+```