Optimizer

Make the prompt do the work

An email, a review, a document, a plan, a chunk of code — anything where you want the work produced.

Your current prompt

**Situation**
{{artist_name}} just received a royalty statement from {{distributor_name}} for {{period}}, and the statement is a dense export of streaming counts, per-service rates, and deductions that reads like it was designed for an accountant rather than an artist trying to understand whether the number at the bottom makes sense.

**Task**
Translate the supplied {{distributor_name}} royalty statement for {{period}} into plain language {{artist_name}} can act on, without hiding any deduction inside a summary line.

**Objective**
1. State the final payable amount for {{period}} in the first sentence, then work backward to explain it.
2. Break the statement down by platform - Spotify, Apple Music, YouTube, and any other source present - showing streams and payout per platform separately, not combined.
3. Convert the per-stream rate on each platform into a plain-language comparison so {{artist_name}} can see which platforms actually pay.
4. Name every deduction line item exactly as {{distributor_name}} labels it, translate what it means in one sentence, and state whether it is a standard distributor fee or something specific to this period.
5. Compare this period's total to the prior period if that data is available, and state the direction and the most likely driver of the change - more streams, a rate change, or a new deduction.
6. Flag anything in the statement that looks like an error or is missing an expected platform, so {{artist_name}} knows to follow up with {{distributor_name}} rather than assuming it is correct.
7. Close with one sentence on what {{artist_name}} would need to do to increase next period's number, grounded in what this statement actually shows moved the needle.

**Knowledge**
Act as a music business manager translating a distributor statement for the artist who earned it. Never round a payout figure without saying so. Distinguish streams from payout at every step - a platform can dominate stream count and still pay the least. Treat every deduction as something to name and explain, never to fold silently into 'distributor fees' as a single line; that is exactly where trust in a royalty statement breaks down.

Template · 3 variables

3 of 3 still blank. Anything left blank is sent to the model as {{placeholder}}.

Describe your ideal output (optional)

ModeModel

4 blocks · 4 clarifying questions · Auto rotates through the models your plan unlocks, switching every two runs per mode.

⌘ + Enter

Standard frame

What you will get back

01Situation
2–3 sentences. Who is acting, for whom, and under what pressure. State the stakes concretely ("hundreds of emails daily", "risk of capital loss"). May open "You are an experienced <role>…" when the task is communicative.
02Task
1–2 sentences opening on an imperative verb. When the task is an audit or a review, enumerate the sub-areas — 4 to 6 named failure classes.
03Objective
The deliverable spec, as a numbered checklist. Length caps, required components, severity tiers if it is a review, and a "for every X provide Y" rule. Every concrete item from the ideal-output description reappears here.
04Knowledge
Tone constraints, domain conventions, the persona ("Act as a Senior …"), the standards to adhere to (PEP 8, one-stop metadata), and the fail-safes for when the model lacks information.

Plus 4 clarifying questions you can answer to re-run with more facts.