perplexity-pack

Apply Perplexity advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Perplexity support escalation. Trigger with phrases like "perplexity hard bug", "perplexity mystery error", "perplexity impossible to debug", "difficult perplexity issue", "perplexity deep debug".

Choose and implement Perplexity validated architecture blueprints for different scales. Use when designing new Perplexity integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Perplexity applications. Trigger with phrases like "perplexity architecture", "perplexity blueprint", "how to structure perplexity", "perplexity project layout", "perplexity microservice".

Configure Perplexity CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Perplexity tests into your build process. Trigger with phrases like "perplexity CI", "perplexity GitHub Actions", "perplexity automated tests", "CI perplexity".

Diagnose and fix Perplexity common errors and exceptions. Use when encountering Perplexity errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "perplexity error", "fix perplexity", "perplexity not working", "debug perplexity".

Execute Perplexity primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "perplexity main workflow", "primary task with perplexity".