# Amicus MCP Server - Prompts
This directory contains specialized prompts for auditing and testing the Amicus MCP Server.
## Quick Start
**One-Line Launch Prompt:**
```
Perform a comprehensive audit of the Amicus MCP Server project following the framework in prompts/comprehensive-audit.md: analyze code quality, security vulnerabilities, architectural design, testing strategy, multi-agent coordination patterns, performance, and provide a scorecard with prioritized recommendations. CRITICAL: Identify yourself as a Node (e.g., 'Node-AUDIT') at start, finish, and intervals.
```
Copy and paste this into Claude (Opus or Sonnet with extended thinking) to launch a comprehensive audit.
See [`LAUNCH.md`](LAUNCH.md) for more launch options.
---
## Available Prompts
### comprehensive-audit.md
**Type:** Audit Framework
A complete audit framework designed for use with strongly-thinking models (like Claude Opus or Sonnet with extended thinking enabled).
**Purpose:** Perform a thorough, multi-dimensional evaluation of the entire project covering:
- Code quality and architecture
- Security vulnerabilities
- Testing strategy and implementation
- Multi-agent testing patterns
- Reliability and fault tolerance
- Performance analysis
- API design and developer experience
- Standards compliance
- Documentation quality
- Operational readiness
**How to Use:**
#### Option 1: Copy and Paste
1. Open `comprehensive-audit.md`
2. Copy the entire content
3. Paste into a conversation with Claude (preferably Opus or Sonnet with extended thinking)
4. Wait for the comprehensive analysis
#### Option 2: Using Claude Code
```bash
# From the project root
claude --file prompts/comprehensive-audit.md
```
#### Option 3: Using the Claude API
```bash
# Read the prompt file and send to Claude API
cat prompts/comprehensive-audit.md | claude-api --model claude-opus-4-5
```
**Expected Output:**
- Detailed scorecard with ratings (1-10) for each dimension
- Security analysis with prioritized vulnerabilities
- Complete test suite design with implementation examples
- Multi-agent testing framework and coordination scripts
- Prioritized action plan with how-to guides
- Research references and implementation resources
**Time to Complete:**
The audit requires deep analysis and may take several minutes with extended thinking enabled. The thoroughness of the analysis is worth the wait.
**Best Practices:**
- Run this audit after major changes
- Use the output to guide sprint planning
- Track improvements over time by re-running periodically
- Share results with team members
- Implement critical fixes immediately
---
### testing-guide.md
**Type:** Implementation Guide
**Purpose:** Practical test implementation patterns and examples for the Amicus MCP Server, including:
- Test structure and organization
- Unit test examples (state operations, locking, path resolution)
- Integration test patterns (workflows, MCP protocol)
- Concurrency test scenarios (race conditions, lock contention)
- Multi-agent coordination tests
- Performance benchmarking
**How to Use:**
This is a reference guide for implementing tests based on audit recommendations:
```bash
# View the testing guide
cat prompts/testing-guide.md
# Copy specific test examples
cat prompts/testing-guide.md | grep -A 20 "def test_"
```
**What's Included:**
- Complete test directory structure
- pytest configuration examples
- Unit test patterns with code samples
- Concurrency test implementations
- MCP protocol testing examples
- CI/CD integration templates
- Performance benchmarking utilities
**Workflow:**
1. Run comprehensive audit to identify testing gaps
2. Use this guide to implement recommended tests
3. Copy and adapt the example test code
4. Set up CI/CD using the provided templates
5. Track coverage and iterate
## Contributing
To add new prompts to this directory:
1. Create a descriptive markdown file
2. Include clear purpose and usage instructions
3. Update this README with the new prompt
4. Test the prompt to ensure it produces valuable output
