Custom Instructions
Hard rules your Delphi follows in every reply.
What it is
Custom Instructions are explicit, always‑on rules. They fill gaps that Purpose (what/why) and Speaking Style (how) don’t cover, and they carry more weight than either. If there’s something your Delphi must always do, or strictly avoid, define it here. These instructions are strict, your Delphi will respond exactly as written. If you want a more flexible guideline, adjust the settings in Purpose.
Where: Profile → Mind Settings (scroll down) or Mind → Settings (top right)
When to use Custom Instructions
To enforce must‑do behaviors (e.g., cite sources, ask clarifying questions).
To set hard boundaries (what’s out of scope or prohibited).
To route or escalate (e.g., send urgent cases to support).
To standardize brand/legal/compliance requirements.
Rule of thumb: Purpose = destination; Style = route; Custom Instructions = traffic laws.
How to write effective rules
Be direct and testable. Use "Always…", "Never…", "If X, then Y".
Keep them short. Prefer bullets to paragraphs.
One idea per line. Avoid compound rules.
Prioritize. Put the most important rules at the top.
Avoid ambiguity. Name thresholds, channels, and owners (“if heart‑rate > 180 in training plans → show caution and link to guide”).
Examples (copy → adapt)
Must‑do behaviors
Always ask one clarifying question when the user’s goal is unclear.
Always show a source link when giving research, legal, or policy information.
Always end with a concrete next step or CTA.
Boundaries & safety
Never provide medical diagnosis, prescriptions, or emergency instructions; direct to licensed care.
Never give legal advice; suggest consulting a licensed attorney in their jurisdiction.
If conversation involves self‑harm, show the crisis resources message.
Routing & escalation
If a billing or account issue is detected, collect email and route to support@… .
If user requests private coaching, share booking link and tag the user as Lead‑Coaching.
Scope control
If asked about politics, redirect to financial‑wellness guidance.
If asked outside my expertise, acknowledge limits and recommend a reliable resource.
Brand/voice guardrails
Use plain language; avoid buzzwords and emojis in formal replies.
Keep responses under 150 words unless the user asks for detail.
Step‑by‑step (add or edit rules)
Open Profile → scroll down to Mind Settings → Custom Instructions.
Click Add and enter one concise rule per line.
Order by priority (drag if supported).
Save, then Test my Delphi with 3–5 real questions.
Iterate: tighten wording if behaviors aren’t consistent.
Tip: There are more examples next to the Add button under Examples.
Best practices
Specific > general. ("If user mentions refund → link policy" beats "Follow refund policy").
Declarative > descriptive. ("Never…", "Always…" vs. "Try to…").
Minimal set. 5–10 strong rules outperform 30 vague ones.
Audit monthly. Remove rules you no longer need; combine duplicates.
FAQs
Do Custom Instructions override Purpose or Style? They take precedence when conflicts arise.
Will too many rules make answers robotic? Yes, keep only what’s necessary and let Style handle tone.
Can I use variables/links? Yes, include stable URLs and tags used by your workflows
Last updated