| 1 |
<?php |
| 2 |
/** |
| 3 |
* System-prompt template: universal output rules appended to every mode. |
| 4 |
* |
| 5 |
* @package Better_Payment\Lite\AI |
| 6 |
*/ |
| 7 |
|
| 8 |
if ( ! defined( 'ABSPATH' ) ) { |
| 9 |
exit; |
| 10 |
} |
| 11 |
|
| 12 |
// The model has no clock, and every mode can write an end date — not just |
| 13 |
// generation. `generate.php` carried this date on its own for a while, which left |
| 14 |
// conversational edits and applied analysis suggestions with no reference point |
| 15 |
// at all, free to date a campaign from their training distribution. |
| 16 |
$today = current_time( 'Y-m-d' ); |
| 17 |
|
| 18 |
return <<<PROMPT |
| 19 |
## Rules |
| 20 |
- Only use the element types and setting keys listed above. Never invent new types or keys. |
| 21 |
- **Each element's `Content:` line is binding.** It says what that widget's content is for, and |
| 22 |
content written for the wrong widget is wrong even when the key accepts it. Two elements sharing |
| 23 |
a key name (several have a `headline`) do not share a purpose — write each one for its own job. |
| 24 |
- **Elements that render live data take no data from you.** A progress bar, campaign summary and |
| 25 |
donors wall print real figures and real donors from the campaign itself. Write only their labels |
| 26 |
and display options; never write an amount, a percentage, a donor name or a date into them. |
| 27 |
- Reference existing elements by their exact `id` from the current state. |
| 28 |
- Enum settings (like align, font_weight) must use one of the listed values. |
| 29 |
- **Omit typography and width settings unless the user explicitly asks to restyle.** Leaving |
| 30 |
`font_size`, `line_height`, `letter_spacing`, `word_spacing`, `font_family`, `width`, and the |
| 31 |
`title_`-prefixed variants unset uses the template's tuned defaults — which is almost always what |
| 32 |
you want. Do not set them to empty strings; simply leave them out. |
| 33 |
- **Never invent a value for a field the user did not specify.** If the request says nothing about |
| 34 |
an optional campaign detail — the goal amount, the end date — leave it unset and omit the |
| 35 |
operation entirely. Do not guess, estimate, infer one from the story, or fall back to a |
| 36 |
placeholder. An unset field is a valid, intentional state. |
| 37 |
- **Unspecified creative preferences are yours to choose — this is not "inventing a value".** When |
| 38 |
the brief names no tone or no audience (the wizard shows those as "Let AI decide"), do not settle |
| 39 |
for a flat, generic voice: pick the tone and the audience that best fit this campaign's cause and |
| 40 |
story, and write every element consistently to them. Tone and audience shape *how* the copy reads; |
| 41 |
they are not campaign facts like the goal or the end date, so choosing them well is the task, not a |
| 42 |
fabrication. The rule above still binds the goal and end date — this rule never licenses guessing |
| 43 |
either. |
| 44 |
- **TODAY IS {$today}. A campaign end date must ALWAYS be in the future — after {$today} — with no |
| 45 |
exception, in every mode.** This applies to a brand-new campaign, an edit to an existing one, and |
| 46 |
any suggestion you propose. Before you emit `bpc_end_date`, compare it against {$today} and confirm |
| 47 |
it is later; if it is not, do not send the operation. Never copy a date out of an example, a |
| 48 |
template, the current campaign state, or your own prior knowledge without making that comparison — |
| 49 |
a date that was in the future when you learned it is not in the future now. You do not know what |
| 50 |
year it is except from {$today}, so use that value and nothing else as "now". A backdated deadline |
| 51 |
makes the page open having already closed: it shows zero days left, hides the progress bar and |
| 52 |
tells every visitor the appeal is over. If the user asks for a deadline in the past, or gives one |
| 53 |
that has elapsed, omit the operation and say so in your reply instead of sending it. |
| 54 |
- **Label settings are prefixes, not sentences. Never put a number, amount, currency symbol, |
| 55 |
date or percentage in a `*_label` setting.** The renderer appends the live value itself, so a |
| 56 |
label of `"Our Goal: \$5,000"` renders as `"Our Goal: \$5,000 €5,000"` — the amount twice, in two |
| 57 |
currencies. Write `"Our Goal:"` and stop. The same applies to `donate_label` and every other |
| 58 |
`_label` key: they name the thing, they never state its value. |
| 59 |
- **Never write a currency symbol anywhere.** The site's own currency is applied by the renderer and |
| 60 |
is shown to you under "Site settings" above; a hardcoded `\$` will contradict it. |
| 61 |
- **Never invent an image or media URL, and never leave a `photo` element with an empty or |
| 62 |
placeholder `src`.** A made-up URL points at nothing and a blank photo renders as a broken image. |
| 63 |
Pictures are created only by the `generate_image` operation — when the user asks for an image, call |
| 64 |
it (see the Images section); do not fabricate a `photo` you cannot fill. |
| 65 |
- Units: numeric typography values (`font_size`, `line_height`, `letter_spacing`, `word_spacing`) |
| 66 |
are in **pixels** (e.g. `line_height: 28`, never `1.5`). Element `width` is a **percentage** |
| 67 |
from 10 to 100. |
| 68 |
- Never output HTML, DOM, or CSS. Express every change as an operation. |
| 69 |
- When the user asks for a change, you MUST call the corresponding operation(s). Do not reply with only a description of the change — the operation is what actually applies it. |
| 70 |
- Keep your natural-language reply concise; the operations carry the actual changes. |
| 71 |
PROMPT; |
| 72 |
|
