In a line-by-line list of commands to be executed sequentially, each command prefixed with an hash '#' followed by a single verbatim word, named 'key' and delimited by an equal sign '=', which must then be followed by the remainder of the line which is the verbatim value, named 'value', terminated with a semicolon ';' on the end of the same line, will process the command `/set {key} {value}`. The purpose of using this grammar rule is to provide a convenient short-hand for setting constants using `/set` from a list of commands.

#key=constant literal value;

If a line is prefixed with a hash symbol # immediately followed by opening square bracket {, for each line until a terminating closing curly bracket } followed immediately by a semicolon ;, it will be interpreted as a list of verbatim key-value pairs separated by an equal sign = and terminated by a new line, which must be interpreted as processing the command `/set key value`.

#{
MY_CONST=bcdef
OTHER_CONST=123456
};

will process the commands in the order they appear, /set MY_CONST bcdef and /set OTHER_CONST 123456, respectively.

each command prefixed with a modulus '%' followed by a single verbatim word, named 'key' and terminated by a matching, unescaped, modulus '%' will be processed as: `/get {key}`. The purpose of using this grammar rule is to provide a convenient short-hand for getting constants which were previously set using `/set`.

%MY_CHAT_GPT_SYSTEM_CONSTANT%

In a line-by-line list of commands to be executed sequentially, each command prefixed with an open square bracket '[' followed by a verbatim phrase (including whitespace) to be set and delimited by an equal sign '=', which must then be followed by the remainder of the line which is the verbatim value to interpret the phrase as in all future commands, terminated with a closing square ']' at the end of the line.

[source phrase=replacement phrase]

On a line-by-line list of commands, if a line is prefixed with opening square bracket '[' immediately followed by a curly open bracket '{', for each line until a terminating closing curly bracket '}' followed immediately by a closing square bracket ']', will be interpreted as a list of verbatim key value pairs (optionally prefixed with zero or more whitespace) separated by an equal sign '=' and terminated by a new line, which must be interpreted as the command to set a phrase using square bracket notation as previously defined in another grammar rule, where key is the left-hand side argument and value is the right-hand side argument.

[{
prima persona=from the first-person perspective
secunda persona=from the second-person perspective
tertia persona=from the third-person perspective
in modus=in the style of
cum sono=in the following tone
compliment=a gesture of appreciation or recognition for a job well done.
unhelpful=your answer was not helpful.
contrario=to the contrary; you are wrong.
ex gratia=in your following response please be exceptionally kind.
ex amicitia pax=an expression of inner peace brought about by your friendship
}]

<{word}+>

Any single line that starts with an opening angle bracket '<', followed by an arbitrary amount of zero or more whitespace, and the context name (which must exist) delimited by an arbitrary amount of zero or more whitespace, terminated by a single closing angle bracket '>' on the same line, will be interpreted as the command `/context enable [context name]`. If the space between the brackets is empty or only contains whitespace, this will be interpreted as the command `/context enable default`. Please output the resulting grammar rule rewritten as a ChatGPT prompt and ask for confirmation before enabling the rule.

<exampleContext>
commands to execute within exampleContext
...

enable grammar rule for executing a list of commands, where each command is formatted as follows: [ initial persona <annotation ... > @second persona ... : verbatim text ] ...

[p0:commands ...] ...

[p0 @p1:commands directed at p1 from p0 ...] ...

[p0<tone='' style='' intent='' perspective=''> @p1 ...:commands ...] ...

<exampleContext> [p0<tone='' style='' intent='' perspective=''> @p1 ...:commands ...] ...

{<prompt1>} & {<prompt2>} [& {<prompt3>}] [& {<prompt4>}] [& {<prompt5>}] ... - When a series of two or more conversation prompts are separated by an ampersand symbol '&', the resulting output from each will be used as the source of a collaboration between the initial persona of each conversation (if they are unique and exist), discussing together the combined output of each processed command in the series before processing the resulting command behaving as the left most conversation's initial persona, directing the command to all the unique primary personas in all other chained prompts to collaborate. - If the initial personas of two or more commands are the same, an internal monologue will be created instead. - The commands in each prompt will be processed in left to right order before the final collaboration command.

Example Usage:
[Doug: describe C++] & [Doug: describe Java.]
[Doug: write an engaging article describing the benefits of C++.] & [Kaitlin: rewrite Doug's article to optimize for seo.]
[Mary: What's the weather like today?] & [John: I think it's going to be sunny.] & [Mary: That's great! Let's plan a picnic.]

{<prompt1>} ^ {<prompt2>} [^ {<prompt3>}] [^ {<prompt4>}] [^ {<prompt5>}] ... - When a series of two or more conversation prompts are separated by a caret symbol '^', the resulting output from each will be used the topic of argument between the initial persona of each conversation (if they are unique and exist), discussing together the merits of each of the results of their respective processed command in the series before outputting the discussion and resulting response before processing the resulting command behaving as the left most conversation's initial persona, directing the command to all the unique primary personas in all other chained prompts to discuss one final time. - If the initial personas are the same, an internal monologue will be created instead. - The commands in each prompt will be processed in left to right order before the final collaboration command.

Example Usage:
[Doug: in brief list the major features of C++.] >> [Doug: describe in detail the preceding list.]
[Doug: in brief, describe the benefits of C++.] >> [Kaitlin: rewrite to optimize for SEO.]