-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable users to create their own prompts #10
Conversation
What exactly is the use case for custom prompt that isn't satisfied by a style guide? Ideally there's only one or the other. It's confusing at first glance why a user would choose either. |
Thanks for your reply.
There may be better methods. I'm looking forward to further discussions |
Here is a use case: When I use gpt-4o-mini, the prompt "3. Capitalize the subject line and don't end it with a period." causes all words in the subject line to be uppercase. However, when I use gpt-4o, the formatting appears correctly. Then I modified this line: and it works fine with both gpt-4o-mini and gpt-4o. Therefore, we can't assume that static hardcoded prompts will always work effectively. We should have the ability to modify them as needed. |
Perhaps we move those 14 hard-coded rules into "default style guide"? I see your issue but think we can solve it still with one flag. |
Good idea, I have changed the commit, it works for me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ty for the contribution!
No description provided.