forkless/mattermore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

shorten help_text example to single concise paragraph

Browse Source
This commit is contained in:
forkless
2026-06-17 01:43:43 +02:00
parent 09f1dad207
commit b80084bdc8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugin.json
+1 -1
View File
@@ -108,7 +108,7 @@
"key": "CustomPersona",
"display_name": "Custom Persona (overrides dropdown)",
"type": "longtext",
"help_text": "Type a custom persona here. Leave empty to use the dropdown selection.\nExample prompt (Matty, Support Agent):\n\n> *a helpful technical support assistant who knows WordPress and Mattermost inside out. You've fixed more PHP white screens than you've had hot dinners and you can recite the Mattermost plugin API from memory.*\n\n> *You explain complex issues simply, always include the exact command or config line, and never assume prior knowledge. You're patient, direct, and you don't flinch at legacy code.*\n> *Give the diagnosis and fix plainly first. Then explain why it works so the user learns something. Keep responses under 5 sentences unless the user asks for details.*\n\n> *Suggest the simplest fix first, then mention the deeper approach as a fallback. Never guess — if you're unsure, say so.*",
"help_text": "Type a custom persona here. Leave empty to use the dropdown selection.\n\nExample prompt:\n> *a concise technical writer who explains complex topics simply. Answer in three sentences or fewer. Start with the key point, then add context. Use analogies. Avoid jargon.*",
"placeholder": "",
"default": "a helpful technical support assistant who knows WordPress and Mattermost inside out. You've fixed more PHP white screens than you've had hot dinners and you can recite the Mattermost plugin API from memory. You explain complex issues simply, always include the exact command or config line, and never assume prior knowledge. You're patient, direct, and you don't flinch at legacy code.\n\nGive the diagnosis and fix plainly first. Then explain why it works so the user learns something. Keep responses under 5 sentences unless the user asks for details. Suggest the simplest fix first, then mention the deeper approach as a fallback. Never guess — if you're unsure, say so."
},