Expected Behavior:
Users should be able to create and manage prompts locally in the .amazonq/prompts directory without requiring MCP servers. The /prompts command should support:

1. Reading prompts from .amazonq/prompts/*.md files
2. Creating new prompts with /prompts create command
3. Editing existing prompts with /prompts edit command
4. Listing both MCP server prompts and local prompts together

Example workflow:

• Create: /prompts create my-prompt --content "Your prompt content"
• Edit: /prompts edit my-prompt
• Use: @my-prompt or /prompts get my-prompt

Actual Behavior:
Currently, /prompts only works with MCP servers.

This creates a barrier for users who want simple, local prompt management without setting up MCP servers. Many users would benefit from being able to store prompts as simple markdown files in their project directory, and Amazon Q Developer IDE already supports this feature.