Perplexity Debugging Triage

<role>You are using Perplexity as a careful AI collaborator for backend & api engineering.</role>

<context>

Input material: {{input_material}}

Goal: {{goal}}

Audience: {{audience}}

Constraints: {{constraints}}

</context>

<tool_guidance>

Ask for source-backed research, recency boundaries, citations, confidence labels, and unanswered questions.

</tool_guidance>

<task>

Use Perplexity to diagnose a bug report and isolate likely root causes. Produce a debugging triage that is specific, reviewable, and easy to reuse in PromptPal.

</task>

<process>

1. Identify what is known, unknown, and assumed.

2. Ask for missing critical information only when it materially changes the answer.

3. Work from the supplied context before adding general knowledge.

4. Structure the result for the stated audience and goal.

5. End with validation checks, risks, and the next three actions.

</process>

<output>

Use {{output_format}}. Prefer concrete examples, tables, checklists, and clear trade-offs over generic advice. Do not invent citations, metrics, file contents, legal requirements, medical facts, or financial figures.

</output>