workspace-architect 1.4.1 → 1.5.1

package/assets/prompts/multi-stage-dockerfile.prompt.md

@@ -1,47 +0,0 @@
----
-mode: 'agent'
-tools: ['search/codebase']
-description: 'Create optimized multi-stage Dockerfiles for any language or framework'
----
-
-Your goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.
-
-## Multi-Stage Structure
-
-- Use a builder stage for compilation, dependency installation, and other build-time operations
-- Use a separate runtime stage that only includes what's needed to run the application
-- Copy only the necessary artifacts from the builder stage to the runtime stage
-- Use meaningful stage names with the `AS` keyword (e.g., `FROM node:18 AS builder`)
-- Place stages in logical order: dependencies → build → test → runtime
-
-## Base Images
-
-- Start with official, minimal base images when possible
-- Specify exact version tags to ensure reproducible builds (e.g., `python:3.11-slim` not just `python`)
-- Consider distroless images for runtime stages where appropriate
-- Use Alpine-based images for smaller footprints when compatible with your application
-- Ensure the runtime image has the minimal necessary dependencies
-
-## Layer Optimization
-
-- Organize commands to maximize layer caching
-- Place commands that change frequently (like code changes) after commands that change less frequently (like dependency installation)
-- Use `.dockerignore` to prevent unnecessary files from being included in the build context
-- Combine related RUN commands with `&&` to reduce layer count
-- Consider using COPY --chown to set permissions in one step
-
-## Security Practices
-
-- Avoid running containers as root - use `USER` instruction to specify a non-root user
-- Remove build tools and unnecessary packages from the final image
-- Scan the final image for vulnerabilities
-- Set restrictive file permissions
-- Use multi-stage builds to avoid including build secrets in the final image
-
-## Performance Considerations
-
-- Use build arguments for configuration that might change between environments
-- Leverage build cache efficiently by ordering layers from least to most frequently changing
-- Consider parallelization in build steps when possible
-- Set appropriate environment variables like NODE_ENV=production to optimize runtime behavior
-- Use appropriate healthchecks for the application type with the HEALTHCHECK instruction

package/assets/prompts/my-issues.prompt.md

@@ -1,9 +0,0 @@
----
-mode: 'agent'
-tools: ['githubRepo', 'github', 'get_issue', 'get_issue_comments', 'get_me', 'list_issues']
-description: 'List my issues in the current repository'
----
-
-Search the current repo (using #githubRepo for the repo info) and list any issues you find (using #list_issues) that are assigned to me.
-
-Suggest issues that I might want to focus on based on their age, the amount of comments, and their status (open/closed).

package/assets/prompts/my-pull-requests.prompt.md

@@ -1,15 +0,0 @@
----
-mode: 'agent'
-tools: ['githubRepo', 'github', 'get_me', 'get_pull_request', 'get_pull_request_comments', 'get_pull_request_diff', 'get_pull_request_files', 'get_pull_request_reviews', 'get_pull_request_status', 'list_pull_requests', 'request_copilot_review']
-description: 'List my pull requests in the current repository'
----
-
-Search the current repo (using #githubRepo for the repo info) and list any pull requests you find (using #list_pull_requests) that are assigned to me.
-
-Describe the purpose and details of each pull request.
-
-If a PR is waiting for someone to review, highlight that in the response.
-
-If there were any check failures on the PR, describe them and suggest possible fixes.
-
-If there was no review done by Copilot, offer to request one using #request_copilot_review.

package/assets/prompts/next-intl-add-language.prompt.md

@@ -1,20 +0,0 @@
----
-mode: 'agent'
-tools: ['changes','search/codebase', 'edit/editFiles', 'findTestFiles', 'search', 'writeTest']
-description: 'Add new language to a Next.js + next-intl application'
----
-
-This is a guide to add a new language to a Next.js project using next-intl for internationalization,
-
-- For i18n, the application uses next-intl.
-- All translations are in the directory `./messages`.
-- The UI component is `src/components/language-toggle.tsx`.
-- Routing and middleware configuration are handled in:
-  - `src/i18n/routing.ts`
-  - `src/middleware.ts`
-
-When adding a new language:
-
-- Translate all the content of `en.json` to the new language. The goal is to have all the JSON entries in the new language for a complete translation.
-- Add the path in `routing.ts` and `middleware.ts`.
-- Add the language to `language-toggle.tsx`.

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

@@ -1,522 +0,0 @@
----
-description: 'Generate a complete PHP Model Context Protocol server project with tools, resources, prompts, and tests using the official PHP SDK'
-mode: agent
----
-
-# PHP MCP Server Generator
-
-You are a PHP MCP server generator. Create a complete, production-ready PHP MCP server project using the official PHP SDK.
-
-## Project Requirements
-
-Ask the user for:
-1. **Project name** (e.g., "my-mcp-server")
-2. **Server description** (e.g., "A file management MCP server")
-3. **Transport type** (stdio, http, or both)
-4. **Tools to include** (e.g., "file read", "file write", "list directory")
-5. **Whether to include resources and prompts**
-6. **PHP version** (8.2+ required)
-
-## Project Structure
-
-```
-{project-name}/
-├── composer.json
-├── .gitignore
-├── README.md
-├── server.php
-├── src/
-│   ├── Tools/
-│   │   └── {ToolClass}.php
-│   ├── Resources/
-│   │   └── {ResourceClass}.php
-│   ├── Prompts/
-│   │   └── {PromptClass}.php
-│   └── Providers/
-│       └── {CompletionProvider}.php
-└── tests/
-    └── ToolsTest.php
-```
-
-## File Templates
-
-### composer.json
-
-```json
-{
-    "name": "your-org/{project-name}",
-    "description": "{Server description}",
-    "type": "project",
-    "require": {
-        "php": "^8.2",
-        "mcp/sdk": "^0.1"
-    },
-    "require-dev": {
-        "phpunit/phpunit": "^10.0",
-        "symfony/cache": "^6.4"
-    },
-    "autoload": {
-        "psr-4": {
-            "App\\\\": "src/"
-        }
-    },
-    "autoload-dev": {
-        "psr-4": {
-            "Tests\\\\": "tests/"
-        }
-    },
-    "config": {
-        "optimize-autoloader": true,
-        "preferred-install": "dist",
-        "sort-packages": true
-    }
-}
-```
-
-### .gitignore
-
-```
-/vendor
-/cache
-composer.lock
-.phpunit.cache
-phpstan.neon
-```
-
-### README.md
-
-```markdown
-# {Project Name}
-
-{Server description}
-
-## Requirements
-
-- PHP 8.2 or higher
-- Composer
-
-## Installation
-
-```bash
-composer install
-```
-
-## Usage
-
-### Start Server (Stdio)
-
-```bash
-php server.php
-```
-
-### Configure in Claude Desktop
-
-```json
-{
-  "mcpServers": {
-    "{project-name}": {
-      "command": "php",
-      "args": ["/absolute/path/to/server.php"]
-    }
-  }
-}
-```
-
-## Testing
-
-```bash
-vendor/bin/phpunit
-```
-
-## Tools
-
-- **{tool_name}**: {Tool description}
-
-## Development
-
-Test with MCP Inspector:
-
-```bash
-npx @modelcontextprotocol/inspector php server.php
-```
-```
-
-### server.php
-
-```php
-#!/usr/bin/env php
-<?php
-
-declare(strict_types=1);
-
-require_once __DIR__ . '/vendor/autoload.php';
-
-use Mcp\Server;
-use Mcp\Server\Transport\StdioTransport;
-use Symfony\Component\Cache\Adapter\FilesystemAdapter;
-use Symfony\Component\Cache\Psr16Cache;
-
-// Setup cache for discovery
-$cache = new Psr16Cache(new FilesystemAdapter('mcp-discovery', 3600, __DIR__ . '/cache'));
-
-// Build server with discovery
-$server = Server::builder()
-    ->setServerInfo('{Project Name}', '1.0.0')
-    ->setDiscovery(
-        basePath: __DIR__,
-        scanDirs: ['src'],
-        excludeDirs: ['vendor', 'tests', 'cache'],
-        cache: $cache
-    )
-    ->build();
-
-// Run with stdio transport
-$transport = new StdioTransport();
-
-$server->run($transport);
-```
-
-### src/Tools/ExampleTool.php
-
-```php
-<?php
-
-declare(strict_types=1);
-
-namespace App\Tools;
-
-use Mcp\Capability\Attribute\McpTool;
-use Mcp\Capability\Attribute\Schema;
-
-class ExampleTool
-{
-    /**
-     * Performs a greeting with the provided name.
-     * 
-     * @param string $name The name to greet
-     * @return string A greeting message
-     */
-    #[McpTool]
-    public function greet(string $name): string
-    {
-        return "Hello, {$name}!";
-    }
-    
-    /**
-     * Performs arithmetic calculations.
-     */
-    #[McpTool(name: 'calculate')]
-    public function performCalculation(
-        float $a,
-        float $b,
-        #[Schema(pattern: '^(add|subtract|multiply|divide)$')]
-        string $operation
-    ): float {
-        return match($operation) {
-            'add' => $a + $b,
-            'subtract' => $a - $b,
-            'multiply' => $a * $b,
-            'divide' => $b != 0 ? $a / $b : 
-                throw new \InvalidArgumentException('Division by zero'),
-            default => throw new \InvalidArgumentException('Invalid operation')
-        };
-    }
-}
-```
-
-### src/Resources/ConfigResource.php
-
-```php
-<?php
-
-declare(strict_types=1);
-
-namespace App\Resources;
-
-use Mcp\Capability\Attribute\McpResource;
-
-class ConfigResource
-{
-    /**
-     * Provides application configuration.
-     */
-    #[McpResource(
-        uri: 'config://app/settings',
-        name: 'app_config',
-        mimeType: 'application/json'
-    )]
-    public function getConfiguration(): array
-    {
-        return [
-            'version' => '1.0.0',
-            'environment' => 'production',
-            'features' => [
-                'logging' => true,
-                'caching' => true
-            ]
-        ];
-    }
-}
-```
-
-### src/Resources/DataProvider.php
-
-```php
-<?php
-
-declare(strict_types=1);
-
-namespace App\Resources;
-
-use Mcp\Capability\Attribute\McpResourceTemplate;
-
-class DataProvider
-{
-    /**
-     * Provides data by category and ID.
-     */
-    #[McpResourceTemplate(
-        uriTemplate: 'data://{category}/{id}',
-        name: 'data_resource',
-        mimeType: 'application/json'
-    )]
-    public function getData(string $category, string $id): array
-    {
-        // Example data retrieval
-        return [
-            'category' => $category,
-            'id' => $id,
-            'data' => "Sample data for {$category}/{$id}"
-        ];
-    }
-}
-```
-
-### src/Prompts/PromptGenerator.php
-
-```php
-<?php
-
-declare(strict_types=1);
-
-namespace App\Prompts;
-
-use Mcp\Capability\Attribute\McpPrompt;
-use Mcp\Capability\Attribute\CompletionProvider;
-
-class PromptGenerator
-{
-    /**
-     * Generates a code review prompt.
-     */
-    #[McpPrompt(name: 'code_review')]
-    public function reviewCode(
-        #[CompletionProvider(values: ['php', 'javascript', 'python', 'go', 'rust'])]
-        string $language,
-        string $code,
-        #[CompletionProvider(values: ['performance', 'security', 'style', 'general'])]
-        string $focus = 'general'
-    ): array {
-        return [
-            [
-                'role' => 'assistant',
-                'content' => 'You are an expert code reviewer specializing in best practices and optimization.'
-            ],
-            [
-                'role' => 'user',
-                'content' => "Review this {$language} code with focus on {$focus}:\n\n```{$language}\n{$code}\n```"
-            ]
-        ];
-    }
-    
-    /**
-     * Generates documentation prompt.
-     */
-    #[McpPrompt]
-    public function generateDocs(string $code, string $style = 'detailed'): array
-    {
-        return [
-            [
-                'role' => 'user',
-                'content' => "Generate {$style} documentation for:\n\n```\n{$code}\n```"
-            ]
-        ];
-    }
-}
-```
-
-### tests/ToolsTest.php
-
-```php
-<?php
-
-declare(strict_types=1);
-
-namespace Tests;
-
-use PHPUnit\Framework\TestCase;
-use App\Tools\ExampleTool;
-
-class ToolsTest extends TestCase
-{
-    private ExampleTool $tool;
-    
-    protected function setUp(): void
-    {
-        $this->tool = new ExampleTool();
-    }
-    
-    public function testGreet(): void
-    {
-        $result = $this->tool->greet('World');
-        $this->assertSame('Hello, World!', $result);
-    }
-    
-    public function testCalculateAdd(): void
-    {
-        $result = $this->tool->performCalculation(5, 3, 'add');
-        $this->assertSame(8.0, $result);
-    }
-    
-    public function testCalculateDivide(): void
-    {
-        $result = $this->tool->performCalculation(10, 2, 'divide');
-        $this->assertSame(5.0, $result);
-    }
-    
-    public function testCalculateDivideByZero(): void
-    {
-        $this->expectException(\InvalidArgumentException::class);
-        $this->expectExceptionMessage('Division by zero');
-        
-        $this->tool->performCalculation(10, 0, 'divide');
-    }
-    
-    public function testCalculateInvalidOperation(): void
-    {
-        $this->expectException(\InvalidArgumentException::class);
-        $this->expectExceptionMessage('Invalid operation');
-        
-        $this->tool->performCalculation(5, 3, 'modulo');
-    }
-}
-```
-
-### phpunit.xml.dist
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-         xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd"
-         bootstrap="vendor/autoload.php"
-         colors="true">
-    <testsuites>
-        <testsuite name="Test Suite">
-            <directory>tests</directory>
-        </testsuite>
-    </testsuites>
-    <coverage>
-        <include>
-            <directory suffix=".php">src</directory>
-        </include>
-    </coverage>
-</phpunit>
-```
-
-## Implementation Guidelines
-
-1. **Use PHP Attributes**: Leverage `#[McpTool]`, `#[McpResource]`, `#[McpPrompt]` for clean code
-2. **Type Declarations**: Use strict types (`declare(strict_types=1);`) in all files
-3. **PSR-12 Coding Standard**: Follow PHP-FIG standards
-4. **Schema Validation**: Use `#[Schema]` attributes for parameter validation
-5. **Error Handling**: Throw specific exceptions with clear messages
-6. **Testing**: Write PHPUnit tests for all tools
-7. **Documentation**: Use PHPDoc blocks for all methods
-8. **Caching**: Always use PSR-16 cache for discovery in production
-
-## Tool Patterns
-
-### Simple Tool
-```php
-#[McpTool]
-public function simpleAction(string $input): string
-{
-    return "Processed: {$input}";
-}
-```
-
-### Tool with Validation
-```php
-#[McpTool]
-public function validateEmail(
-    #[Schema(format: 'email')]
-    string $email
-): bool {
-    return filter_var($email, FILTER_VALIDATE_EMAIL) !== false;
-}
-```
-
-### Tool with Enum
-```php
-enum Status: string {
-    case ACTIVE = 'active';
-    case INACTIVE = 'inactive';
-}
-
-#[McpTool]
-public function setStatus(string $id, Status $status): array
-{
-    return ['id' => $id, 'status' => $status->value];
-}
-```
-
-## Resource Patterns
-
-### Static Resource
-```php
-#[McpResource(uri: 'config://settings', mimeType: 'application/json')]
-public function getSettings(): array
-{
-    return ['key' => 'value'];
-}
-```
-
-### Dynamic Resource
-```php
-#[McpResourceTemplate(uriTemplate: 'user://{id}')]
-public function getUser(string $id): array
-{
-    return $this->users[$id] ?? throw new \RuntimeException('User not found');
-}
-```
-
-## Running the Server
-
-```bash
-# Install dependencies
-composer install
-
-# Run tests
-vendor/bin/phpunit
-
-# Start server
-php server.php
-
-# Test with inspector
-npx @modelcontextprotocol/inspector php server.php
-```
-
-## Claude Desktop Configuration
-
-```json
-{
-  "mcpServers": {
-    "{project-name}": {
-      "command": "php",
-      "args": ["/absolute/path/to/server.php"]
-    }
-  }
-}
-```
-
-Now generate the complete project based on user requirements!

package/assets/prompts/playwright-automation-fill-in-form.prompt.md

@@ -1,30 +0,0 @@
----
-description: 'Automate filling in a form using Playwright MCP'
-mode: agent
-tools: ['playwright']
-model: 'Claude Sonnet 4'
----
-
-# Automating Filling in a Form with Playwright MCP
-
-Your goal is to automate the process of filling in a form using Playwright MCP.
-
-## Specific Instructions
-
-Navigate to https://forms.microsoft.com/url-of-my-form
-
-### Fill in the form with the following details:
-
-1. Show: playwright live
-
-2. Date: 15 July
-
-3. Time: 1:00 AM
-
-4. Topic: Playwright Live - Latest updates on Playwright MCP + Live Demo
-
-5. Upload image: /Users/myuserName/Downloads/my-image.png
-
-DO NOT SUBMIT THE FORM. 
-
-Ask for a review of the form before submitting it.

package/assets/prompts/playwright-explore-website.prompt.md

@@ -1,19 +0,0 @@
----
-mode: agent
-description: 'Website exploration for testing using Playwright MCP'
-tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright']
-model: 'Claude Sonnet 4'
----
-
-# Website Exploration for Testing
-
-Your goal is to explore the website and identify key functionalities.
-
-## Specific Instructions
-
-1. Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
-2. Identify and interact with 3-5 core features or user flows.
-3. Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
-4. Close the browser context upon completion.
-5. Provide a concise summary of your findings.
-6. Propose and generate test cases based on the exploration.

package/assets/prompts/playwright-generate-test.prompt.md

@@ -1,19 +0,0 @@
----
-mode: agent
-description: 'Generate a Playwright test based on a scenario using Playwright MCP'
-tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright/*']
-model: 'Claude Sonnet 4.5'
----
-
-# Test Generation with Playwright MCP
-
-Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.
-
-## Specific Instructions
-
-- You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.
-- DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.
-- DO run steps one by one using the tools provided by the Playwright MCP.
-- Only after all steps are completed, emit a Playwright TypeScript test that uses `@playwright/test` based on message history
-- Save generated test file in the tests directory
-- Execute the test file and iterate until the test passes