PHPackages                             wachterjohannes/debug-mcp-prompts - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. wachterjohannes/debug-mcp-prompts

ActiveLibrary

wachterjohannes/debug-mcp-prompts
=================================

Code generation prompts for Symfony development

11PHP

Since Nov 29Pushed 5mo agoCompare

[ Source](https://github.com/wachterjohannes/debug-mcp-prompts)[ Packagist](https://packagist.org/packages/wachterjohannes/debug-mcp-prompts)[ RSS](/packages/wachterjohannes-debug-mcp-prompts/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

debug-mcp-prompts
=================

[](#debug-mcp-prompts)

**⚠️ PROTOTYPE - FOR TESTING AND DISCUSSION PURPOSES ONLY**

---

Code generation prompts for Symfony development, providing structured templates for creating console commands and other components.

Purpose
-------

[](#purpose)

Provides MCP prompts that guide LLMs in generating high-quality Symfony code:

- **Symfony Command Prompts**: Templates for creating console commands with best practices
- **Structured Generation**: Consistent code structure following Symfony conventions

Features
--------

[](#features)

- Template-based prompt generation
- Parameter substitution for customization
- Best practices guidance embedded in prompts
- Automatic discovery by debug-mcp server

Installation
------------

[](#installation)

```
composer require wachterjohannes/debug-mcp-prompts
```

The prompts will be automatically discovered when debug-mcp server starts.

Available Prompts
-----------------

[](#available-prompts)

### symfony\_command

[](#symfony_command)

Generate a Symfony Console Command with proper structure and best practices.

**Name**: `symfony_command`

**Parameters**:

- `command_name` (required): The command name (e.g., 'app:process-data')
- `description` (required): What the command does
- `interactive` (optional, default: false): Whether the command needs user interaction

**Example Usage**:

Via MCP protocol:

```
{
  "jsonrpc": "2.0",
  "method": "prompts/get",
  "params": {
    "name": "symfony_command",
    "arguments": {
      "command_name": "app:import-users",
      "description": "Import users from CSV file",
      "interactive": true
    }
  },
  "id": 1
}
```

**Generated Prompt**:

The prompt will guide the LLM to create a command following this structure:

- Uses `#[AsCommand]` attribute
- Extends `Command` class
- Includes configure() method for arguments/options
- Implements execute() method with SymfonyStyle
- Adds dependency injection via constructor
- Includes error handling
- Interactive input handling (if requested)

Template Structure
------------------

[](#template-structure)

Prompts use template files in `templates/`:

```
templates/
├── command-basic.txt       # Non-interactive command template
└── command-interactive.txt # Interactive command template

```

Templates contain:

- Role markers (user/assistant)
- Parameter placeholders ({command\_name}, {description})
- Step-by-step generation instructions
- Code structure guidance
- Best practices reminders

Usage in Claude
---------------

[](#usage-in-claude)

When using with Claude Desktop configured with debug-mcp:

1. **List Available Prompts**: Ask Claude: "What prompts are available?"
2. **Use a Prompt**: "Use the symfony\_command prompt to create a command named app:export-orders that exports orders to CSV"
3. **Customize Parameters**: Claude will use the prompt template with your provided parameters to generate the code.

Registration
------------

[](#registration)

Prompts are registered via composer.json extra configuration:

```
{
  "extra": {
    "wachterjohannes/debug-mcp": {
      "classes": [
        "Wachterjohannes\\DebugMcp\\Prompts\\SymfonyCommandPrompt"
      ]
    }
  }
}
```

Adding New Prompts
------------------

[](#adding-new-prompts)

To add a new prompt:

1. **Create Template File** in `templates/`:

    ```
    templates/entity-crud.txt

    ```
2. **Create Prompt Class**:

    ```