# PromptHive 🐝
**Lightning-fast open source** prompt manager for developers. Terminal-native, 11ms average response, works with any AI tool.
## TL;DR
```bash
# Install (Latest: v0.2.2)
cargo install prompthive
# OR: curl -sSL https://prompthive.sh/install.sh | bash
# Multiple Workflows - Choose Your Style
# 1. Perfect commit messages (PRODUCTION READY ✅)
# 2. Instant debugging (BATTLE TESTED ✅)
# 3. Complete PR workflows
**Why?** Because copy-pasting from ChatGPT history takes 30+ seconds. PromptHive operations average 11ms.
**Current Version**: 0.2.2 - Open source with community registry, instant authentication, team collaboration, and prompt sharing. All features included, no paid tiers.
> **🚀 Philosophy**: [Terminal-First Development](http://jorypestorious.com/blog/terminal-velocity/) | [Spec-Driven AI Engineering](http://jorypestorious.com/blog/ai-engineer-spec/)
> **📁 Documentation**: See README.md for complete usage guide
**Core Promise**: Every command under 80ms. It's a TOOL, not a LIBRARY.
> **Unix Philosophy**: We don't run AI. We manage prompts perfectly, and pipe them to ANY AI tool you prefer. Like `npm` doesn't run JavaScript, we don't run prompts. We just make them instantly accessible.
```bash
# PromptHive + Your Favorite AI Tools - Three Patterns:
# 1. Command Substitution (Interactive AI):
# 2. Piped with -p flag (Non-interactive/Scripting):
# 3. Direct Output (Auto-clipboard):
ph use essentials/debug # Output + clipboard for pasting into ChatGPT UI
ph use essentials/commit -q # Quiet mode (no clipboard)
```
## 🚀 Installation
### Cargo (Rust) - Available Now ✅
```bash
# Install from crates.io
cargo install prompthive
# Verify installation
ph --version
```
### Quick Install Script
```bash
# Automatic installation with platform detection
# Verify installation
ph --version
```
**Current Status**: Version 0.2.2 is available on crates.io. The install script automatically downloads pre-built binaries for your platform.
### Shell Completions
After installation, set up shell completions for the best experience:
#### Bash
```bash
ph completion bash > ~/.bash_completion.d/prompthive
source ~/.bash_completion.d/prompthive
```
#### Zsh
```bash
ph completion zsh > ~/.zsh_completions/_prompthive
# Add to ~/.zshrc: fpath=(~/.zsh_completions $fpath)
```
#### Fish
```bash
ph completion fish > ~/.config/fish/completions/ph.fish
```
## Quickstart
```bash
# Use built-in essentials (ready to go!)
# Use immediately with real workflows
# Use with ANY AI tool (copies to clipboard if terminal, pipes if piped)
git diff main...HEAD | ph use essentials/pr | claude # Interactive PR description
cat legacy-code.js | ph use essentials/refactor | mods # Mods
cat api.py | ph use essentials/generate-tests | sgpt # Shell GPT
# Lightning-fast operations
ph ls # List all prompts
ph f commit # Fuzzy search essentials
ph u essentials/debug-error # Short aliases work
# Share and organize with banks
ph bank publish my-workflow-prompts
# Create custom banks from your favorite prompts
mkdir -p ~/.prompthive/banks/team
cp ~/.prompthive/prompts/*.md ~/.prompthive/banks/team/
```
## "But Why Not Just..."
### ...use text files?
- Can't fuzzy search across them in 50ms
- No smart matching (ph u au → auth-basic)
- No metadata or descriptions
- No sharing/versioning/teams
### ...use shell aliases?
```bash
# This gets unwieldy fast:
alias fix="echo 'Debug this error and suggest a fix'"
alias commit="echo 'Generate a commit message from the diff'"
alias review="echo 'Review this code for issues'"
# vs
ph f debug # Fuzzy finds essentials/debug-error instantly
```
### ...use ChatGPT/Claude history?
- Takes 30+ seconds to search and copy
- Lost between browser tabs
- Can't pipe or compose
- No version control
### ...use GitHub Gists?
- Network latency (2-5 seconds minimum)
- No offline access
- Requires browser
- Can't pipe directly
**See this README for complete documentation.**
## Commands (v0.2.2)
```bash
ph use <name> # Use a prompt (u) - auto-clipboard, save, append, file
ph show <name> # Display prompt (s) - with I/O options
ph new <name> # Create prompt (n) - smart detection
ph edit <name> # Edit prompt (e) - opens $EDITOR
ph find <query> # Search prompts (f) - fuzzy matching
ph ls # List prompts (l) - see all
ph delete <name> # Delete prompt (d) - with confirm
ph clean <text> # Clean and format text with AI-style processing
# Just run 'ph' to launch the TUI (like lazygit)
ph # Launch interactive TUI
### Advanced Features
```bash
ph compose <prompts> # Chain prompts together
ph stats # Usage analytics dashboard
ph completion <shell> # Generate shell completions
ph login # Authenticate with registry for sync
ph sync # Sync prompts with cloud ✅ WORKING
ph sync status # Check sync status and conflicts ✅ WORKING
ph sync push # Push local changes to cloud ✅ WORKING
ph sync pull # Pull cloud changes locally ✅ WORKING
```
## 🚀 Power User Examples
### Built-in Template Variables
```bash
# Prompts automatically support built-in variables
ph new standup "Daily standup for {date} by {user} on {hostname}"
ph new bug-report "Bug in {pwd} on branch {git_branch} ({git_status})"
# Environment variables work too
ph new deploy "Deploy to {env:AWS_REGION} in {env:ENVIRONMENT}"
# Variables are replaced when you use the prompt
```
### Version Control - Never Lose a Good Prompt
```bash
# Tag important versions of your prompts
ph version api-design v1.0 -m "Initial stable API prompt"
ph version api-design v1.1 -m "Added error handling section"
ph version api-design v2.0 -m "Complete rewrite for REST best practices"
# View history
ph versions api-design
# 📚 Version history for 'api-design'
# 📌 v2.0 (a3b4c5d6) - Complete rewrite for REST best practices
# 📌 v1.1 (87654321) - Added error handling section
# 📌 v1.0 (12345678) - Initial stable API prompt
# Rollback when needed
ph rollback api-design v1.1
# ✅ Rolled back 'api-design' to version 'v1.1'
```
### Diff & Merge - Collaborate on Prompts
```bash
# Compare prompt versions
ph diff api-v1 api-v2
ph diff api-v1 api-v2 --format side-by-side
ph diff local-prompt team/shared-prompt --context 10
# Merge improvements
ph merge team/api-enhanced api-design --backup
ph merge experimental-fix stable-prompt --preview
```
### Web Dashboard - Visual Analytics
```bash
# Open interactive dashboard
ph web # Full dashboard
ph web stats # Usage analytics
ph web prompts # Browse all prompts
ph web --no-browser # Generate HTML only
```
## 🎯 Unified I/O Design - Smart Defaults
PromptHive uses intelligent defaults based on context, reducing typing while maintaining flexibility:
### Text Transformation Commands (use, show, clean)
**In Terminal (TTY):**
- Auto-copies to clipboard by default
- No stdout output (content is on clipboard)
- Use `-q` to suppress clipboard and output to stdout instead
**When Piping:**
- Outputs to stdout for pipe compatibility
- No auto-clipboard (use `-c` to force clipboard)
```bash
# Terminal usage - auto-clipboard
ph clean "messy text" # ✓ Copied to clipboard (2ms)
ph use api-design "Create user endpoint" # ✓ Copied to clipboard (3ms)
# Piping - outputs to stdout
# Force clipboard even when piping
# Quiet mode in terminal
ph clean "text" -q # Outputs to stdout, no clipboard
```
### Query Commands (ls, find)
**Always outputs to stdout** (auto-clipboard would be too noisy)
- Use `-c` to explicitly copy results
- Use `-s` to save as a new prompt
```bash
ph ls # Lists to stdout
ph find "api" -c # Find and copy results
ph ls -s "my-prompt-list" # Save list as a new prompt
```
### Universal I/O Flags
Every command supports these consistent flags:
- `-s NAME` - Save output as a new prompt
- `-a NAME` - Append output to existing prompt
- `-c` - Force copy to clipboard
- `-f PATH` - Write to file (with bidirectional sync)
- `-q` - Quiet mode (suppress default behaviors)
- `-e` - Edit before output (where applicable)
### Smart File Operations
The `-f` flag creates bidirectional sync by default:
```bash
# Create prompt with automatic file sync
ph new "API guidelines" -f # Creates ./api-guidelines.md
ph new "API guidelines" -f api.md # Creates ./api.md
# Smart naming when path not provided
ph use api-design "endpoints" -f # Creates ./api-design-output.md
# Bidirectional sync means:
# - Edit the file → prompt updates
# - Edit the prompt → file updates
# - Always stay in sync!
```
### Composable Flags
All flags work together sensibly:
```bash
# Clean, save, append, copy, and write to file
ph clean "text" -s cleaned -a log -c -f output.md
# Use prompt, edit result, save, and sync to file
ph use template -e -s edited -f template-output.md
# Find prompts, save results, copy to clipboard
ph find "api" -s search-results -c
```
### Design Philosophy
- **Smart defaults**: Do the right thing based on context
- **Explicit overrides**: Flags always override defaults
- **Composability**: All flags combine logically
- **No surprises**: Predictable behavior in all contexts
## Configuration
### Disable Logging
```bash
# Temporary (this session only)
export PROMPTHIVE_LOG_LEVEL=error # Only errors
export PROMPTHIVE_LOG_LEVEL=off # Complete silence
# Permanent (add to ~/.zshrc or ~/.bashrc)
echo 'export PROMPTHIVE_LOG_LEVEL=error' >> ~/.zshrc
source ~/.zshrc
```
### Other Environment Variables
```bash
PROMPTHIVE_BASE_DIR=/custom/path # Change storage location
PROMPTHIVE_EDITOR=code # Set preferred editor
PROMPTHIVE_LOG_FORMAT=json # JSON logs for production
```
## Creative Usage Patterns
### 🎯 Daily Journaling & Reflection
```bash
# Create a journal bank
ph new journal/daily "Date: {date}\n\nToday I learned: "
ph new journal/gratitude "Three things I'm grateful for:\n1. "
ph new journal/standup "Yesterday: \nToday: \nBlockers: "
# Daily workflow
```
### 🧠 Learning & Study Assistant
```bash
# Create study prompts
ph new study/explain "Explain {input} like I'm 5"
ph new study/test "Create 5 quiz questions about: {input}"
ph new study/summarize "Key points from this text: {input}"
# Study session
```
### 💼 Meeting & Communication Templates
```bash
# Professional templates
ph new work/email-followup "Subject: Follow-up from our {date} meeting\n\nHi {name},\n\nThank you for..."
ph new work/1-on-1 "1-on-1 with {manager}\n\nAgenda:\n- Career development\n- Current projects\n- Feedback\n\nNotes: "
ph new work/proposal "Proposal: {title}\n\nProblem: \nSolution: \nImpact: \nTimeline: "
# Quick usage
```
### 🎨 Creative Writing & Content
```bash
# Writing helpers
ph new write/character "Create a character profile:\nName: {input}\nTraits: "
ph new write/plot-twist "Given this plot: {input}\n\nSuggest 3 unexpected twists:"
ph new write/blog-outline "Blog post about: {input}\n\nOutline with sections:"
# Content creation
claude "$(ph use write/blog-outline 'Terminal productivity')"
### 🔧 DevOps & Operations
```bash
# Runbook templates
ph new ops/incident "Incident: {title}\nSeverity: \nImpact: \nMitigation: "
ph new ops/postmortem "Postmortem for: {incident}\n\nWhat happened: \nRoot cause: \nLessons learned: "
ph new ops/deploy-checklist "Deploy {service} to {env}\n\n[ ] Tests pass\n[ ] Migrations run\n[ ] Monitoring updated\n[ ] Rollback plan"
# Incident response
ph use ops/incident "Database connection timeout" -s incidents/$(date +%s)
### 📊 Data Analysis & Research
```bash
# Analysis templates
ph new data/hypothesis "Hypothesis: {input}\n\nTest with: \nExpected outcome: "
ph new data/findings "Analysis of: {dataset}\n\nKey findings: \nLimitations: \nNext steps: "
ph new data/visualize "Data: {input}\n\nSuggest 3 visualization types and why:"
# Research workflow
```
### 🎮 Personal Productivity
```bash
# Life management
ph new life/decision "Decision: {input}\n\nPros:\nCons:\nAlternatives:"
ph new life/habit "Track habit: {habit}\n\nDate: {date}\nCompleted: [ ]\nNotes: "
ph new life/goals "Goal: {input}\n\nWhy it matters: \nSuccess criteria: \nFirst step: "
# Daily use
claude "$(ph use life/decision 'Accept job offer at startup')"
ph use life/habit "Morning meditation" -a habits/meditation-log
```
### 🚀 API & Integration Patterns
```bash
# Combine with other tools
alias review='gh pr view --json files | ph use essentials/code-review | claude -p'
# Scheduled prompts
crontab -e
# 0 9 * * 1 ph use work/weekly-goals | mail -s "Weekly Goals" me@example.com
# 0 17 * * * git log --since="9am" | ph use journal/daily | ph save today
```
## Performance
PromptHive operations are optimized for **instant prompt access**:
```bash
$ time ph use essentials/commit
✓ Prompt loaded and copied to clipboard (3ms)
real 0m0.045s
$ ph ls
📋 Your prompts: (12ms)
essentials/commit - Semantic commit messages
essentials/debug-error - Error analysis & fixes
essentials/pr - Pull request descriptions
essentials/code-review - Code review analysis
essentials/refactor - Code refactoring
```
**What these times represent:**
- **PromptHive operations**: File I/O, prompt processing, fuzzy matching (~2-50ms)
- **AI processing time**: Separate - depends on your AI tool (5-30+ seconds)
- **Value proposition**: Zero-latency prompt access vs. writing prompts from scratch
**The real speed gain**: Instead of spending 2-5 minutes crafting the perfect prompt, you get battle-tested prompts instantly.
## Partial Matching (Like JJ)
PromptHive uses smart partial matching:
```bash
$ ph use d
# If unique, uses the match
# If ambiguous, shows options:
Error: Multiple matches. Did you mean:
essentials/debug-error (de) - Error analysis & fixes
essentials/document (do) - Documentation generation
custom/deploy (dep) - Deployment scripts
$ ph use de # Now unique - uses 'essentials/debug-error'
```
## The Magic: Composition
PromptHive is the ONLY tool that lets you chain prompts:
```bash
# Fix a bug completely
ph use find-root-cause | \
ph use generate-fix | \
ph use add-tests | \
claude
# Each prompt transforms the previous output
# Total time: 250ms for 5 prompts
```
## Real-World Usage
### Daily Developer Workflows
```bash
# 🔥 Auto-generate perfect commit messages
# 🐛 Debug errors instantly
# 📝 Generate PR descriptions
# 🧪 Create tests from code
# 📚 Document your code
# 🔍 Code review helper
### Advanced Workflows
```bash
# Chain multiple prompts for complex tasks
ph use essentials/refactor | llm | \
ph use essentials/generate-tests | llm > fixed-code.js
# Morning standup automation
# Refactor legacy code
ph use essentials/add-types | llm > modern-api.py
```
### 🧙 Workflow Automation Examples
```bash
# AI-Powered Git Workflow
# Automated Code Review Pipeline
function ai-review() {
llm > review-$(date +%Y%m%d).md
}
# Daily Standup Generator
function standup() {
pbcopy
}
# Smart Documentation Generator
function doc-this() {
llm > "${1%.*}.docs.md"
}
```
## 🔰 Shell Pipes Primer (for Terminal Newbies)
### The Basics
```bash
# The pipe | sends output from one command to another
# Redirect > saves output to a file
echo "hello" > file.txt # Saves "hello" to file.txt
# Append >> adds to a file without overwriting
echo "world" >> file.txt # Adds "world" to file.txt
# Input < reads from a file
cat < file.txt # Reads content from file.txt
```
### With PromptHive
```bash
# Simple: Copy to clipboard (when in terminal)
ph use api-design # Just copies, no pipe needed
# Pipe to AI: Send prompt to AI tool
# Chain: Multiple operations
# Save: Capture output
# Combine: Mix different sources
### When to Use What
- **No pipe**: When you just want to copy a prompt
- **Single pipe |**: When sending to one AI tool
- **Multiple pipes |**: When chaining operations
- **Redirect >**: When saving results
- **Cat/Echo**: When adding context to prompts
## 🏦 Prompt Banks - Instant Productivity
### Built-in Banks Ready to Use
```bash
# essentials/ - Core developer workflows
ph use essentials/commit # Perfect git commits
ph use essentials/debug-error # Debug any error
ph use essentials/code-review # Thorough code reviews
ph use essentials/pr # PR descriptions
ph use essentials/refactor # Code refactoring
# professional/ - Business communication
ph use professional/email-reply # Professional email responses
ph use professional/meeting-notes # Structured meeting documentation
ph use professional/proposal # Business proposals
ph use professional/status-update # Project status reports
# coding-patterns/ - Design patterns & best practices
ph use coding-patterns/api-design # RESTful API design
ph use coding-patterns/error-handling # Robust error handling
ph use coding-patterns/factory-pattern # Factory pattern implementation
# devops/ - Infrastructure & deployment
ph use devops/dockerfile # Production-ready Dockerfiles
ph use devops/ci-pipeline # CI/CD pipeline configuration
ph use devops/kubernetes # K8s deployment manifests
# claude-commands/ - Imported from Claude
ph use claude-commands/chain # Command chaining workflows
ph use claude-commands/workflow-manager # Workflow automation
# 10x/ - Advanced productivity
ph use 10x/afk-task "Build auth" # Claude AFK workflows
ph use 10x/spec-driven # Spec-driven development
ph use 10x/fix-tests # Test fixing assistant
# workflow/ - Complex processes
ph use workflow/analyze # Code analysis
ph use workflow/design # System design
ph use workflow/implement # Implementation guide
# variables/ - Dynamic templates
ph use variables/standup # Daily standup
ph use variables/sprint-planning # Sprint planning
```
### Create Your Own Banks
```bash
# Option 1: From existing prompts
mkdir -p ~/.prompthive/banks/myteam
cp ~/.prompthive/prompts/*.md ~/.prompthive/banks/myteam/
# Option 2: From Claude commands (if you have them)
mkdir -p ~/.prompthive/banks/claude
cp ~/.claude/commands/*.md ~/.prompthive/banks/claude/
# Now use: ph use claude/command-name
# Option 3: Create specialized banks
mkdir -p ~/.prompthive/banks/{backend,frontend,devops}
ph new backend/api-design "Design REST APIs..."
ph new frontend/component "React component template..."
ph new devops/deploy "Deployment checklist..."
```
### Sharing Banks with Your Team
```bash
# Share via Git (recommended)
cd ~/.prompthive/banks/myteam
git init && git add .
git commit -m "feat: team prompt collection"
git remote add origin github.com/yourteam/prompts
git push
# Team members clone it
cd ~/.prompthive/banks
git clone github.com/yourteam/prompts team
# Now everyone can: ph use team/api-design
# Keep banks in sync
cd ~/.prompthive/banks/team && git pull
# Or use PromptHive's built-in sharing
ph bank publish myteam # Publish to registry
ph bank install @user/team # Install from registry
```
### Real Workflows with Banks
```bash
# Developer workflows
git diff main | ph use essentials/code-review | llm > review.md
# Professional communication
ph use professional/status-update "Project Alpha Week 3" | claude
# Infrastructure & DevOps
ph use devops/kubernetes "web API with Redis" | llm > k8s-manifests.yaml
# Design patterns
# Advanced workflows
ph use claude-commands/workflow-manager "Deploy to production" | claude
# Create aliases for common workflows
alias dockerize='ph use devops/dockerfile'
```
## Building PromptHive with Itself
We built PromptHive using PromptHive:
```bash
# Bootstrap phase
ph new rust-cli
# Every feature after
ph new add-command
# Test and iterate
ph search "rust testing"
## File Structure
Dead simple, just markdown files:
```
~/.prompthive/
├── prompts/ # Your personal prompts
│ ├── api.md
│ ├── auth.md
│ └── test.md
├── banks/ # Organized prompt collections
│ ├── essentials/ # Built-in essentials
│ ├── 10x/ # Productivity workflows
│ ├── workflow/ # Complex processes
│ └── myteam/ # Your custom banks
├── registry/ # Cached registry packages
└── config.toml # Configuration
```
## Prompt Format
Just markdown with optional frontmatter:
```markdown
---
id: api
description: REST API design
---
Design a REST API with these requirements:
- Resource: {resource}
- Operations: {operations}
- Include error handling
- Follow REST best practices
```
## Why PromptHive?
1. **Speed**: 80ms operations are addictive (GitHub: 30+ seconds)
2. **Simple**: Just like `ls` and `cat` - no learning curve
3. **Universal**: Works with ALL AI tools, not locked to one
4. **Offline**: Your prompts work without internet
5. **Composable**: Chain prompts like Unix commands
6. **Smart I/O**: Auto-clipboard, save, append - works how you think
### The Dropbox Moment
"You could just use FTP!" they said about Dropbox. But UX is the product.
"You could just use text files!" they'll say about PromptHive. But speed is the product.
**80ms vs 30 seconds. Every time. That's the difference.**
## The Vision
In one year:
- Every tutorial starts with `ph install`
- Teams have standardized on PromptHive
- "Just ph it" is a common phrase
- The registry has 10,000+ quality prompts
## Features
### Core Features (Production Ready)
- ✅ **Lightning-fast prompt management** - Create, edit, search, and use prompts
- ✅ **Intelligent fuzzy matching** - `ph u ap` → `api-design` instantly
- ✅ **Universal shell integration** - Copy to clipboard or pipe to ANY tool
- ✅ **Smart I/O operations** - Auto-clipboard, save, append, file output
- ✅ **Text cleaning & formatting** - AI-style text processing with `ph clean`
- ✅ **Smart completions** - Tab completion for bash, zsh, fish
- ✅ **Cross-platform** - Works on macOS, Linux, Windows
- ✅ **Prompt composition** - Chain prompts for complex workflows
- ✅ **Magic link authentication** - Secure login for registry sync
- ✅ **Performance guarantee** - All operations under 80ms
### Advanced Features (All Included - Free & Open Source)
- ✅ **Registry sync** - Cloud backup and device sync
- ✅ **Magic link authentication** - Passwordless secure login
- ✅ **Team collaboration** - Private prompt banks and sharing
- ✅ **Prompt sharing** - Public and invite-based prompt sharing
- ✅ **Community registry** - Growing library of quality prompts
- ✅ **Usage analytics** - Productivity tracking with achievements
- ✅ **Web dashboard** - Visual prompt management and statistics
## Development Build
```bash
# Development build (all features)
cargo build --release
# Run tests
cargo test --release
# Performance benchmark
cargo test --release test_performance
```
## Troubleshooting
### Command not found
```bash
# Ensure binary is in PATH
echo $PATH
which ph
# If using cargo install
### Clipboard not working
```bash
# If terminal, it copies automatically
ph use api # Copies to clipboard
# Or pipe explicitly
```
### Shell completions not working
```bash
# Regenerate completions
ph completion bash > ~/.bash_completion.d/prompthive
source ~/.bashrc
```
## 🐝 Part of the CalmHive Ecosystem
PromptHive works beautifully with [CalmHive CLI](https://calmhive.com) - an open-source wrapper for Claude CLI that adds background processing, voice control, and smart defaults.
```bash
# Use PromptHive with CalmHive for ultimate productivity
calmhive afk "$(ph use essentials/refactor)" --iterations 20
calmhive voice "$(ph use essentials/debug)"
```
Check out [calmhive.com](https://calmhive.com) for enhanced Claude CLI workflows!
## Performance
PromptHive is engineered for sub-80ms performance across all operations. Built with Rust for maximum efficiency and reliability, it handles thousands of prompts without slowing down your workflow.
**Tested on version 0.2.2**: All core operations (new, use, show, edit, ls, find) complete in under 80ms on modern hardware.
## Join the Community 🐝
### 🌟 **100% Open Source & Free**
- ✅ Unlimited local prompts
- ✅ Lightning-fast performance (<80ms)
- ✅ Compose & chain prompts
- ✅ Cross-platform support
- ✅ Text cleaning & formatting
- ✅ Magic link authentication
- ✅ Cloud sync across devices
- ✅ Private prompt banks
- ✅ Team collaboration & sharing
- ✅ Prompt sharing features
- ✅ Advanced analytics & insights
- ✅ Community registry access
- ✅ Self-hostable infrastructure
*"Professional prompt management for everyone"*
### 🤝 **Contributing**
- Report bugs and request features
- Submit prompts to the community registry
- Contribute code improvements
- Help with documentation
- Join discussions and share workflows
Visit our [GitHub repository](https://github.com/joryeugene/prompthive) to get involved!
---
**"Prompts that just work."**