Distill an AI Chat Into Instructions — the Standing Macro
A support-reply iteration becomes a standing instruction: status-and-date first, ticket number in sentence one, never overpromise — paste once per session, use all day.
Overview
Some conversations converge on something bigger than a prompt: a standing way of handling a task type. The support-macro case is the archetype — one good refund reply, iterated into rules (status and date first, ticket number in the first sentence, conservative timelines only), then declared the pattern for every refund reply. System Instruction mode frames the distillation for exactly that: a paste-once-per-session instruction, task-scoped on purpose — the usage notes draw the line to the System Prompt Generator for full operational personas.
Workflow
-
Iterate once, properly
One reply, corrected until right — the conversation does the design work.
-
Frame as instruction
System Instruction mode converts the convergence into a standing, session-level rule set.
-
Stay task-scoped
It governs refund replies, not the assistant's whole identity — the boundary keeps it composable.
Why This Works
- Standing framing matches how repeated tasks are actually run
- Task scoping keeps the instruction composable with other prompts
- The from-now-on declaration travels as the rule it was meant to be
Best for
- Support, ops, and any reply-pattern work
- Tasks done many times per session
- Sharing one person's convergence with a team
Not for
- Full operational system prompts with roles and escalation — the System Prompt Generator
- One-off tasks — Standard mode fits those better
Use cases
- Building support macros from one good reply
- Standing instructions for repeated task types
- Team-shareable converged patterns