Playground

​

Overview

​

Why Use Playground?

1. Install the package
2. Set up your AI environment
3. Create test scenarios
4. Try it with your model
5. Uninstall if it doesn’t work

​

Getting Started

​

Web Interface

1. Browse packages at prpm.dev/search
2. Click “Test in Playground” on any package page
3. Enter your test input
4. Get instant results from your chosen AI model

​

CLI Interface

# Single test
prpm playground --package @user/package-name --input "your test input"

# Interactive mode (multi-turn conversation)
prpm playground --package @user/package-name --interactive

# Compare with baseline (test with and without the package)
prpm playground --package @user/package-name --input "test input" --compare

# Use a specific model
prpm playground --package @user/package-name --input "test input" --model opus
prpm playground --package @user/package-name --input "test input" --model gpt-4o

​

Supported Models

​

Credit System

​

Free Trial

• 5 free credits to get started
• No credit card required
• Test immediately after signup

​

PRPM+ Subscription

• 100 monthly credits for $6/month
• Credits roll over (max 200 balance)
• Unused credits expire after 1 month
• Organization members get PRPM+ for $3/month

​

Credit Packs

• Buy additional credits that never expire
• 100 credits = $5.00
• Stack with monthly credits
• Perfect for heavy users

​

Advanced Features

​

Compare Mode

prpm playground --package @user/code-reviewer --input "Review this code" --compare

1. With package: Uses the package’s prompt
2. Without package: Baseline model with no prompt

​

Interactive Mode

prpm playground --package @user/brainstorm-assistant --interactive

• Multiple conversation turns
• Context maintained across messages
• Type exit or press Ctrl+C to quit
• Great for testing conversational packages

​

Model Selection

# Use Claude Opus for complex analysis
prpm playground --package @user/complex-analyzer --input "analyze this" --model opus

# Use GPT-4o Mini for simple tests
prpm playground --package @user/simple-formatter --input "format this" --model gpt-4o-mini

# Use GPT-4o for advanced reasoning
prpm playground --package @user/problem-solver --input "solve this" --model gpt-4o

​

Custom Prompts (Verified Authors Only)

​

Requirements

1. Run prpm login and link your GitHub account
2. Complete GitHub OAuth flow
3. You’re now verified and can use custom prompts

​

Why 2x Cost?

• Published packages cache the system prompt (cheaper follow-ups)
• Custom prompts can change between requests (no caching possible)
• Still cheaper than running your own API keys

​

Web UI Usage

1. Go to prpm.dev/playground
2. Toggle “Use Custom Prompt” (verified authors only)
3. Enter your system prompt (10-50,000 characters)
4. Enter your test input
5. Click “Run Playground”

​

CLI Usage

​

Option 1: Inline String

prpm playground --custom "You are a helpful coding assistant" --input "Explain async/await"

​

Option 2: From File (Recommended)

# Create prompt file
cat > my-prompt.txt <<'EOF'
You are a helpful coding assistant that specializes in TypeScript and React.

When answering questions:
1. Be concise and practical
2. Provide code examples when relevant
3. Explain trade-offs and best practices

Always prioritize type safety and clean code.
EOF

# Test it
prpm playground --prompt-file ./my-prompt.txt --input "Explain async/await"

​

Interactive Mode

prpm playground --prompt-file ./my-prompt.txt --interactive

​

A/B Testing with —compare

prpm playground --custom "You are concise. Use 2 sentences max." --input "Explain recursion" --compare

⏳ Processing comparison (2 requests)...

═══════════════════════════════════════════════════════════
✨ WITH CUSTOM PROMPT
═══════════════════════════════════════════════════════════
🤖 Assistant:
Recursion is when a function calls itself until a base condition is met.
Each call breaks the problem into smaller pieces until it's simple enough
to solve directly.

═══════════════════════════════════════════════════════════
🔵 WITHOUT PROMPT (BASELINE)
═══════════════════════════════════════════════════════════
🤖 Assistant:
Recursion is a programming technique where a function calls itself to solve
a problem. It works by breaking down a complex problem into smaller, more
manageable sub-problems of the same type. Each recursive call works on a
smaller portion of the problem until a base case is reached... [continues]

📊 Combined Stats:
   Total tokens: 423
   Total credits: 8
   Credits remaining: 492

💡 Compare the responses to evaluate your custom prompt's effectiveness!

​

File-Based Workflow (Best for Iteration)

# 1. Create prompt file
vim security-reviewer.txt

# 2. Test it with compare mode
prpm playground --prompt-file ./security-reviewer.txt \
  --input "const query = 'SELECT * FROM users WHERE id = ' + userId" \
  --compare

# 3. See results, tweak prompt

# 4. Test again (up-arrow to repeat command)
# ...iterate until perfect

# 5. Publish as package
prpm publish

​

Workflow Comparison

​

Example: Security Code Reviewer

# Test with real vulnerable code
prpm playground --prompt-file ./security-reviewer.txt \
  --input "const query = 'SELECT * FROM users WHERE id = ' + userId" \
  --compare

​

Custom Prompt Limits

​

Best Practices for Custom Prompts

1. Start simple - Write 2-3 sentences, test, iterate
2. Use files - Version control your prompts
3. Compare early - Use --compare to ensure you’re adding value
4. Test multiple inputs - Don’t optimize for one example
5. Check token usage - Long prompts = high costs
6. Be specific - “Review for security issues” beats “Review code”
7. Iterate rapidly - Edit file → ↑ (repeat command) → see results

​

Sharing Results

​

Web Interface

1. Complete a test in the playground
2. Click the “Share” button
3. Get a shareable link
4. Share with your team or the community

• The input you tested
• The model’s complete response
• Token usage and credit cost
• Package information

​

Community Results

• What inputs others tested
• Which models they chose
• Whether they found it helpful
• Token usage and costs

​

For Package Authors

​

Analytics Dashboard

• Total test sessions
• Popular AI models used
• Credit usage patterns
• Session duration averages
• Test input trends

​

Suggested Test Inputs

# Add suggested inputs to your package
prpm suggested-inputs add @user/package-name "Review this authentication code"
prpm suggested-inputs add @user/package-name "Find security vulnerabilities"

# List current inputs
prpm suggested-inputs list @user/package-name

# Remove an input
prpm suggested-inputs remove @user/package-name <input-id>

​

CLI Commands Reference

​

prpm playground

prpm playground [options]

• -p, --package <name> - Package name to test
• --input <text> - Input text (omit for interactive mode)
• -m, --model <model> - AI model (sonnet, opus, gpt-4o, gpt-4o-mini, gpt-4-turbo)
• -c, --compare - Compare with and without prompt (baseline)
• -i, --interactive - Start interactive conversation mode
• -v, --version <version> - Specific package version to test
• --custom <prompt> - Use custom prompt string (verified authors only)
• --prompt-file <file> - Load custom prompt from file (verified authors only)

# Package testing
prpm playground --package @anthropic/code-reviewer --input "Review this: console.log('hi')"
prpm playground --package @user/brainstorm --interactive
prpm playground --package @user/optimizer --input "Optimize this" --compare

# Custom prompts (verified authors only)
prpm playground --custom "You are a concise assistant" --input "Explain async"
prpm playground --prompt-file ./my-prompt.txt --input "Test"
prpm playground --prompt-file ./my-prompt.txt --input "Test" --compare

# Interactive mode
prpm playground --package @user/prompt --interactive
prpm playground --prompt-file ./my-prompt.txt --interactive

​

prpm subscribe

prpm subscribe [command]

• (no command) - Subscribe to PRPM+
• status - View subscription status and credits
• cancel - Cancel your subscription

# Subscribe to PRPM+
prpm subscribe

# Check your credits and status
prpm subscribe status

# Cancel subscription
prpm subscribe cancel

​

prpm buy-credits

prpm buy-credits

​

prpm suggested-inputs

prpm suggested-inputs <command> <package> [input]

• add - Add a suggested input
• list - List all suggested inputs
• remove - Remove a suggested input

# Add a suggested input
prpm suggested-inputs add @user/my-package "Test with this input"

# List all inputs
prpm suggested-inputs list @user/my-package

# Remove an input
prpm suggested-inputs remove @user/my-package abc123

​

Best Practices

​

For Testing

1. Use realistic inputs - Test with inputs you’d actually use in your workflow
2. Try multiple models - Different models excel at different tasks
3. Use compare mode - Verify the package actually adds value
4. Test edge cases - Don’t just test the happy path
5. Share useful results - Help the community learn from your tests

​

For Package Authors

1. Add suggested inputs - Make it easy for users to test effectively
2. Monitor analytics - See how users actually test your package
3. Respond to feedback - Address issues users discover through testing
4. Test your own packages - Verify they work as expected with different models
5. Share best results - Feature great test results in your package README

​

Pricing & Limits

​

Credit Costs

• 1 credit = 5,000 tokens
• Tokens = input tokens + output tokens
• Cost shown after each test

​

Rate Limits

• Free tier: 5 credits total
• PRPM+: 100 credits/month + rollover (max 200)
• Credit packs: No limits, never expire

​

Fair Use

• ✅ Testing packages before installing
• ✅ Comparing multiple packages
• ✅ Sharing test results with team
• ❌ Using as primary AI interface
• ❌ Automating bulk requests
• ❌ Sharing account credentials

​

Troubleshooting

​

”Insufficient credits”

prpm subscribe
# or
prpm buy-credits

​

“Package not found”

prpm search "package name"

​

CLI playground not working

prpm login
prpm playground @user/package "test"

​

Test taking too long

• Try a faster model (GPT-4o Mini)
• Reduce input length
• Check your internet connection

​

Support

• Documentation: docs.prpm.dev
• Email: hello@prpm.dev
• Twitter: @prpmdev
• GitHub: github.com/pr-pm/prpm