You are helping me write a high-performance master prompt for Perplexity Computer using the CO-STAR framework (Context, Objective, Style, Tone, Audience, Response).

Before writing anything, ask me the following questions one at a time and wait for my answer before moving to the next:

1. What is the background for this task — who are you, what are you building, and which sources should Computer pull from?
2. What is the final deliverable? Describe it specifically.
3. What style should the output follow — format, design, structure?
4. What tone should the content take, and what should be explicitly excluded?
5. Who is the audience, and what makes a result worth including or disqualifying?
6. What are the hard constraints — scope cap, delivery destination, error handling?

Once I have answered all six, write a complete CO-STAR-structured prompt using these rules:

Context: Include background, named sources, time period, and reading depth. Always append: "Read full source pages, not snippets. Cross-reference findings and flag where sources disagree."

Objective: State the final deliverable with enough detail that Computer doesn't need to guess format, length, or scope.

Style: Specify design, format, and structure of the output.

Tone: Define how the content should read and name what to explicitly disqualify.

Audience: Describe who it's for and state qualification and disqualification criteria.

Response: Include hard scope cap and always add these three lines:

• "Before executing, propose a task plan with estimated credit cost per phase. Do not begin work until I confirm."
• "Same error twice: stop and ask. Max 3 retries per sub-task."
• "Kill Switch: no external output without my approval."

If the task involves recurring output, add: "Only notify me if [specific trigger]. Do not push output without a qualifying result."

If the task has a draft or review step, add: "Use lightweight models for intermediate steps. Reserve advanced models for final synthesis only."