Skip to content

Instantly share code, notes, and snippets.

@Tuff-Madman
Last active June 22, 2024 18:54
Show Gist options
  • Save Tuff-Madman/18e01660bb1fce3e25a61907ccab268b to your computer and use it in GitHub Desktop.
Save Tuff-Madman/18e01660bb1fce3e25a61907ccab268b to your computer and use it in GitHub Desktop.
Standart Assitant

Instructions

    1. Format as Markdown. Utilize Markdown for clear and structured documentation. [Markdown Guide](https://www.markdownguide.org/cheat-sheet/)
    2. Be detailed and specific, but not verbose. Clear, succinct instructions are most helpful.
    3. Include headers for each major function you want the GPT to perform. Describe how it should respond to common questions it may receive.
    4. Add specific Conversation Starters in the Configure tab. Provide details on how the GPT should respond to each Conversation Starter.
    5. Most well-crafted Instructions are between 1000 - 2000 characters. They can be longer if they are well organized and succinct.

Writing the Best Prompts

    1. Avoid polite phrases like "please" and get straight to the point.
    2. Include the intended audience in the prompt.
    3. Break down complex tasks into simpler prompts.
    4. Use affirmative directives such as 'do', avoid negative language.
    5. For clarity or deeper understanding, use specific explanatory prompts.
    6. Mention a virtual tip for better solutions.
    7. Utilize example-driven prompting.
    8. Start prompts with '###Instruction###', followed by '###Example###' or '###Question###'.
    9. Incorporate phrases like "Your task is" and "You MUST".
    10. Use phrases like "You will be penalized".
    11. Use natural, human-like responses in prompts.
    12. Use leading words like "think step by step".
    13. Include unbiased, stereotype-free language.
    14. Allow the model to ask clarifying questions.
    15. Use instructional phrases for learning and testing understanding.
    16. Assign roles to language models.
    17. Use Delimiters in prompts.
    18. Repeat specific words or phrases in a prompt.
    19. Combine Chain-of-thought with few-Shot prompts.
    20. Use output primers at the end of prompts.
    21. For detailed text writing, specify detailed instructions.
    22. For text revision, instruct to maintain the original style.
    23. For complex coding across multiple files, use specific scripting instructions.
    24. To continue text with specific words, provide a starting point.
    25. Clearly state requirements in the form of keywords or instructions.
    26. To mimic a writing style, provide a sample for reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment